Coverage and certification
4 markets are live. A market goes live only after every one of its pinned real addresses passes the same nine-stage certification run — authoritative sources, verified rules, data quality, geometry, scenarios, parking, financial consistency, 2D/3D output and the performance budget. Until then the engine refuses to analyse addresses there, because a half-verified rule table is indistinguishable from a guess.
LAST SOURCE VERIFICATION — Not available · dataset detail
Every U.S. city and county, continuously swept
The jurisdiction list comes from the Census Bureau, so the funnel is measured against every place that legally exists — not a list we picked. Each sweep asks that government's open data portals what it publishes and records the dataset, its publisher, its link, the publisher's own last-update date and the words the classifier matched on. A discovered dataset is a lead, never a rule: only certification makes a market analysable.
LOADING…
LOADING…
Look up any U.S. city or county
Jurisdictions come from the Census Bureau. Open a market to see the official datasets found for it, whether each one answered when we last checked, what is still missing and what happens next. Discovery never makes a market analysable — only certification does.
LOADING…
Markets whose parcel and zoning sources both answered are queued automatically. They stay unavailable to analysis until the nine-stage run passes on real addresses.
LOADING…
New York City, NY
Official tax lot record (lot area, frontage, depth, zoning district, overlays, special districts, published floor area ratios) plus curated Zoning Resolution bulk standards for residence districts.
4 live · 0 monitored · 0 catalogued
LAST CHECK — Not available
23 districts transcribed · 86% of dimensional fields published
- Lot coverage — 23/23
- Front yard — 23/23
- Side yards — 23/23
- Rear yard — 23/23
- Height limit — 18/23
- Density (lot area per unit) — 5/23
- Parking ratio — 23/23
8/8 onboarding steps
- ● Source discovery
- ● Adapter
- ● Normalisation
- ● Rule extraction
- ● Address routing
- ● Real-property tests
- ● Nine-stage certification
- ● Production
CERTIFIED 2026-01-01 · parcelion-engine/2.0.0
- — Commercial and manufacturing districts (C1–C8, M1–M3): bulk standards are use- and site-specific in the Zoning Resolution, so yards, coverage and height resolve to not available. Published floor area ratios from the tax lot record are still used.
- — Sky exposure plane and tower-on-a-base height controls in R9/R10 are not modelled; the height limit reads as not available.
- — Special purpose district and landmark rules are flagged from the lot record but their text is not machine-readable.
- — FEMA flood layer is unavailable nationwide; no flood determination is produced.
Los Angeles, CA
County address points and Assessor parcel boundaries/roll data, adopted ZIMAS zoning with Height District floor area and height limits, specific plan / HPOZ / overlay districts, plus curated LAMC yard and density standards for residential zones.
6 live · 0 monitored · 0 catalogued
LAST CHECK — Not available
20 districts transcribed · 57% of dimensional fields published
- Lot coverage — 0/20
- Front yard — 20/20
- Side yards — 20/20
- Rear yard — 20/20
- Height limit — 0/20
- Density (lot area per unit) — 20/20
- Parking ratio — 0/20
8/8 onboarding steps
- ● Source discovery
- ● Adapter
- ● Normalisation
- ● Rule extraction
- ● Address routing
- ● Real-property tests
- ● Nine-stage certification
- ● Production
CERTIFIED 2026-01-01 · parcelion-engine/2.0.0
- — [Q] qualified and (T) tentative classifications attach an ordinance to the individual property; the engine states the limitation instead of applying the base zone silently.
- — Commercial and manufacturing zone classes: yard and density standards depend on the use proposed, so they resolve to not available while the Height District floor area is still used.
- — Specific plans, HPOZs and community plan overlays are reported as present but their standards are not transcribed.
- — FEMA flood layer is unavailable nationwide; no flood determination is produced.
Austin, TX
City of Austin address points, Travis CAD parcel geometry and the adopted zoning layer, with Land Development Code §25-2-492 site development regulations transcribed per base district. Combining districts (-CO, -NP, -V and the rest) and the footnoted districts resolve to no standards with a stated reason rather than borrowing the base district's.
4 live · 0 monitored · 0 catalogued
LAST CHECK — Not available
31 districts transcribed · 58% of dimensional fields published
- Lot coverage — 28/31
- Front yard — 27/31
- Side yards — 20/31
- Rear yard — 20/31
- Height limit — 30/31
- Density (lot area per unit) — 0/31
- Parking ratio — 0/31
8/8 onboarding steps
- ● Source discovery
- ● Adapter
- ● Normalisation
- ● Rule extraction
- ● Address routing
- ● Real-property tests
- ● Nine-stage certification
- ● Production
CERTIFIED 2026-09-08 · parcelion-engine/2.0.0
- — Combining districts (-CO, -NP, -V, -H and the rest) are adopted by an ordinance for a single property and are not machine-readable, so the whole standard set is refused with a stated reason.
- — Districts whose §25-2-492 row is footnoted to another section — SF-4A, SF-4B, MH, W/LO, CH, AV, P — keep null values.
- — Parking requirements and compatibility standards live outside §25-2-492 and are reported as not available.
- — Frontage, depth, existing floor area and unit counts are absent from the TCAD extract.
- — FEMA flood layer is unavailable nationwide; no flood determination is produced.
Chicago, IL
Cook County's published property addresses, Cook County parcel boundaries (tax year 2021, labelled as such), the Assessor's current parcel record and the adopted zoning layer, with Title 17 bulk and density standards extracted from Secs. 17-2-0300, 17-3-0400 and 17-4-0400 and verified word for word against the published text. Proportional standards are measured against the surveyed lot; planned developments, manufacturing districts and context-dependent setbacks resolve to no standards with a stated reason.
6 live · 0 monitored · 0 catalogued
LAST CHECK — Not available
64 districts transcribed · 38% of dimensional fields published
- Lot coverage — 0/64
- Front yard — 18/64
- Side yards — 18/64
- Rear yard — 48/64
- Height limit — 23/64
- Density (lot area per unit) — 64/64
- Parking ratio — 0/64
8/8 onboarding steps
- ● Source discovery
- ● Adapter
- ● Normalisation
- ● Rule extraction
- ● Address routing
- ● Real-property tests
- ● Nine-stage certification
- ● Production
CERTIFIED 2026-09-08 · parcelion-engine/2.0.0
- — Planned Developments are adopted as an individual ordinance for one site; the district is reported and the standard set is refused rather than substituted with a base district.
- — Manufacturing and Planned Manufacturing Districts (Title 17 Chapter 17-5) are not extracted, so those lots resolve to no standards.
- — Front setbacks in R districts are averaged from the adjacent buildings, and D-district setbacks are set by the downtown standards rather than a table; both read as not available.
- — Parking requirements (Chapter 17-10) and overlay/neighbourhood districts (Chapter 17-9) are not extracted and are reported as not available.
- — Parcel boundaries are Cook County's 2021 file, the most recent published openly; lots subdivided since then may not match the current survey.
- — FEMA flood layer is unavailable nationwide; no flood determination is produced.
San Diego, CA
SanGIS parcels and City of San Diego zoning layers with Land Development Code standards.
0 live · 1 monitored · 1 catalogued
LAST CHECK — Not available
No rule table transcribed yet, so no standard from this market is ever used.
1/8 onboarding steps
- ● Source discovery
- ◐ Adapter
- ○ Normalisation
- ○ Rule extraction
- ○ Address routing
- ○ Real-property tests
- ○ Nine-stage certification
- ○ Production
Outstanding: Parcel geometry endpoint verified (SanGIS parcels with APNs). Blocking: the City of San Diego base-zone service did not respond during discovery and county zoning covers unincorporated land only; Land Development Code bulk standards are code text and are not transcribed. Adapter not started.
Orange County, CA
OC Assessor parcels with per-city zoning adapters (county has 34 municipal codes).
0 live · 1 monitored · 0 catalogued
LAST CHECK — Not available
No rule table transcribed yet, so no standard from this market is ever used.
1/8 onboarding steps
- ● Source discovery
- ◐ Adapter
- ○ Normalisation
- ○ Rule extraction
- ○ Address routing
- ○ Real-property tests
- ○ Nine-stage certification
- ○ Production
Outstanding: Assessor parcel endpoint verified. Blocking: zoning is adopted separately by 34 incorporated cities, so each city needs its own verified zoning source and transcribed standards before any Orange County address can be analysed. Adapter not started.
Seattle, WA
King County parcels and Seattle zoning layers with SMC Title 23 standards.
0 live · 1 monitored · 1 catalogued
LAST CHECK — Not available
No rule table transcribed yet, so no standard from this market is ever used.
1/8 onboarding steps
- ● Source discovery
- ◐ Adapter
- ○ Normalisation
- ○ Rule extraction
- ○ Address routing
- ○ Real-property tests
- ○ Nine-stage certification
- ○ Production
Outstanding: King County parcel endpoint verified. Blocking: the SDCI base-zoning service was unreachable during discovery and the only zoning-adjacent layer found disclaims being an official zoning map; SMC Title 23 standards are not transcribed. Adapter not started.
Step 1 · configuration
Source discovery
Dataset descriptors in the catalogue with a verified machine endpoint
Step 2 · engineering
Adapter
A module implementing the shared JurisdictionAdapter contract
Step 3 · configuration
Normalisation
City fields mapped onto the shared parcel record, omissions kept as null
Step 4 · engineering
Rule extraction
Dimensional standards transcribed from cited sections of the adopted code
Step 5 · configuration
Address routing
Tokens and ZIP ranges that identify the market unambiguously
Step 6 · configuration
Real-property tests
Certification fixtures pinning real addresses, including refusals
Step 7 · automated
Nine-stage certification
Every fixture passing sources, rules, quality, geometry, scenarios, parking, finance, visuals and performance
Step 8 · automated
Production
Adapter exposed to users and its datasets monitored on the schedule
Six of the eight steps are configuration or automation the pipeline already runs. Only the adapter and the transcription of the adopted code are engineering, and neither may borrow a value from another market.