200 feet The 27 parcels Further Analysis

The city's 27 parcels, identified

The city published only totals: parcel counts and acreage per separation distance, without naming the parcels. But the totals are a fingerprint. Working backwards, this page shows the unique parcel assignment that reproduces the city's cumulative counts and acres at every published tier, within the table's own rounding. Then it checks each parcel against the ordinance's own rules.

The parcels, by verdict

    Validation against the city's table

    TierParcelsCityAcresCity acres

    Method

    Three deterministic steps: (1) the count-and-acre arithmetic alone identifies several parcels with certainty; (2) those anchors prove the city's measure: plain parcel-boundary distance, no padding, to residential zoning districts where districts exist and to county residential land beyond the city limits, ignoring residential uses inside the city; (3) under that measure, each distance band's small candidate ring is solved exactly for the city's (count, acre) signature. One parcel set satisfies everything. Scripts: scripts/city_exact.py for the identification, scripts/city_issues.py for the per-parcel diagnosis.

    Caveats: two 0.581-ac parcels are interchangeable between the 250 and 300 bands by arithmetic alone (distance order assigns them); the three [350,400) members miss their distance ring by 14–27 ft under the public GIS snapshot (layer-vintage tolerance); and 24 other candidates ≥200 ft under this universe are absent from the city's counts. Those far from a band edge imply exclusion features or manual pruning the city has not disclosed. Full detail: out/city_exact.json.