US Census TIGER polygons fetched on demand and drawn as Google Maps Data layers. The map draws the surrounding context borders without re-fitting, then fits to the most specific level only (city, then county, then state), and caps the zoom so a tiny village outline does not fill the screen.
Also called: city limits map · county line map · am I in city limits · jurisdiction boundary
- 1TIGER layer ids are discovered dynamically from the TIGERweb MapServer, with hard-coded fallbacks
- 2County and state outlines are generalized server-side (maxAllowableOffset) so a whole-state outline is not a huge payload
- 3A place is looked up by exact place FIPS when known, falling back to a name match
- 4City features sit above county features by zIndex so a click inside a city opens the city
- 5A ResizeObserver re-fits the map on any size change so an expanding panel never leaves a half-painted grey box
The rule changes across a line you cannot see from an address string. The code says it plainly: 'city rules govern inside city limits; outside every city, the county rule applies.' The ResizeObserver exists because 'Google Maps caches its container size at construction and paints nothing until told the size changed… Watching the element is the version that cannot be raced.' The map height is capped because a long rule (Columbia's runs to thousands of words) once stretched the map to 2313px and 'read as "the map is broken".'
- An address alone cannot decide which side of a boundary a rural parcel sits on
- A jurisdiction name means nothing to a rep who does not know the area
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 →