A guard on the restore path's geocode. Google always returns something — for an address it cannot find it silently falls back to a similar road, the postcode, or the town centroid, flagged partial_match or APPROXIMATE. Those are rejected and no marker is drawn; the borders and rule still stand on the FIPS already held.
Also called: wrong pin · map pin accuracy · approximate address
- 1The restore path geocodes only to establish WHERE the property is — never to re-decide which rule governs
- 2r0.partial_match, or a location_type other than ROOFTOP / RANGE_INTERPOLATED, resolves to null
- 3With no pin, the drawn borders and the frozen rule are still shown
- 4If a confident pin lands outside the drawn city border, that disagreement is deliberately left visible
Straight from the comment: 'A pin dropped on that is not "roughly right" — it is a specific wrong parcel, and on a permit screen the parcel IS the question, since the answer changes across a city line. No pin is the honest output when we cannot place the property.' And on the disagreement case: 'If the pin lands outside the drawn city border, that disagreement is worth seeing, not worth hiding.'
- A confident-looking pin on the wrong parcel misleads on the one question that matters
- A silent geocode fallback looks like an answer
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →