Skip to main content
This page lists the permit data issues we know about.
  • Each row says what you see and what to do.
  • We fix them in data updates. When an issue is fixed, we remove its row.
  • Counts on this page are approximate. They change with each data update.
If you find an issue that is not on this page, see Report a problem.

Dates

Status

Categories

Work tags

Work tags are assigned by Mireye from each permit’s own text. Each tag carries a measured confidence (work_tag_confidence). The issues below are part of that measured error.

Permit offices

Requests and field lists

Behaviour that is not a defect

These are how the data works. They are not errors. Re-issued permits
  • An old permit issued again after July 1, 2024 has date_flags: ["reissued"].
  • “New since” searches leave it out: issued_since, or date_field: "issued" with a date_from.
  • Set include_reissued: true in the Permits API to keep it.
  • The Search permits filter always leaves it out of an issued-since count.
A source that never records a milestone
  • Some sources never record an issued date, a final date or a final status.
  • Their permits cannot match a search on that milestone. The note or the remark says so.
  • For those offices a 0 does not mean none happened.
Permits not tied to a parcel
  • A permit that could not be tied to a parcel does not count per parcel.
  • In Enrich, partial can mean many permits are not tied to parcels. Read the coverage note.