Data dictionary

Tables

• Permit fields

  247 fields

  One row per permit, served by /v1/permits and /v1/regions/{region}/permits/{permit_number}. A field a place does not publish is blank there.

• Contractor licence fields

  40 fields

  One row per licence, served by /v1/contractors and /v1/contractors/{id}. Nevada licences come from the Nevada State Contractors Board, Austin's from the Texas Department of Licensing and Regulation (TDLR).

• Permit fee fields

  15 fields

  One row per fee line, served as fees on /v1/regions/{region}/permits/{permit_number}, an empty array where the place publishes no fee lines.

• Permit inspection fields

  18 fields

  One row per inspection, served as inspections on /v1/regions/{region}/permits/{permit_number}, an empty array where the place publishes none.

• Plan review step fields

  17 fields

  One row per step of a permit's plan review, served as review_steps on /v1/regions/{region}/permits/{permit_number}.

• Permit event fields

  11 fields

  One row per change to a permit's status or one of its dates, served by /v1/events. How to page through them is on the change events page.

• Parcel sale fields

  8 fields

  Recorded sales of a parcel from the County Assessor, served as sales on /v1/regions/{region}/properties/{parcel_id}.

• Planning case fields

  13 fields

  Planning cases on a parcel in the City of Las Vegas, served as planning_cases on a permit and on a property.

• Code enforcement case fields

  8 fields

  Open code enforcement cases on a parcel in the City of Las Vegas. The API serves their counts and dates on each permit (parcel_open_code_cases, parcel_last_code_case_date and the other code case fields); the cases themselves come in data extracts.

• Contractor discipline fields

  6 fields

  Disciplinary actions the Nevada State Contractors Board took against a licence, served as discipline on /v1/contractors/{id}, newest first.

• Property summary fields

  8 fields

  One row per parcel with permits: the summary of /v1/regions/{region}/properties/{parcel_id} and each match of /v1/properties.

• Property trade fields

  7 fields

  One row per work tag on a parcel: the trades of /v1/regions/{region}/properties/{parcel_id}.

The same dictionary is served as JSON at /v1/meta/dictionary. How often each field is filled, place by place, is on the coverage page.