The Zoning Gap

Where does Indianapolis zoning disagree with its own plans — and in which direction? The Zoning Gap map answers that question for every acre of Marion County, and lets you ask it about any address.

Open the Zoning Gap map →

The idea

Indianapolis has two rulebooks. The zoning code says what you may build today. The land use plan says what the city intends for each place — the Pattern Book typologies across most of the county, and older township-adopted plans still governing the rest. Everyone assumes the two rulebooks roughly agree. This map measures where they don’t:

What zoning prohibits

The map also shows the flip side of the question — not what the plan wants, but what the code forbids outright, district by district:

As of the current build: homes are prohibited by right on 29.9% of analyzed land, apartments on 69.6%, and neighborhood retail on 60.7%. These are conservative counts — districts where limited residential or retail is arguably possible are not flagged, and the denominator includes parks and special districts.

Ask about your address

Type an address — or click anywhere on the map — and the card tells you: the zoning district in plain English, what housing it permits by right, the plan designation over it, whether the plan and the code agree, which prohibitions apply, any overlays (TOD, Regional Center, Specific Area Plans), and the parcel’s owner and acreage. Summary only, not a zoning determination — every card links to the source records.

The method

Rather than hand-judging thousands of district-and-designation combinations, the matrix is derived from small calibration tables. Every zoning district gets an intensity rank (1–10, from D-A at 1 to the CBD core at 10). Every plan category gets an intended intensity range — the Pattern Book typologies by their described character, and the legacy plans’ density buckets natively (a “3.5–5 units per acre” designation is an intensity range). A district below its designation’s range is underzoned; above it, overzoned; a use-family mismatch is flagged on its own terms. Parks, floodway, special uses, planned developments, and the excluded towns are set aside for individual evaluation rather than force-classified.

Every classification traces to a stated rule, and the current build accounts for every polygon in the county’s land use plan — zero unmatched values. Disagree with a cell and you’re really disagreeing with one of a few dozen published calibration numbers, which is a productive argument to have in public. Several calibrations have already come from exactly that kind of challenge, and this page will keep hosting them.

Why it matters

Petitioners and neighbors argue about rezonings one at a time, as if each were a referendum. The Gap map reframes the question: on nearly two thousand acres of the urban core, a petition isn’t asking for a favor — it’s asking for consistency with a plan the city already adopted. And where the code bans the apartment and the corner store across most of the county, that’s not an anecdote; it’s a policy choice you can measure in acres.

The method is fully exportable. Every city with a comprehensive plan has a zoning gap. Indianapolis is simply the first to see its own.

Data: City of Indianapolis MapIndy and DMD GIS services (zoning districts, Land Use Plan, overlays, parcels). Figures reflect the current map build and update as the analysis is recalibrated. Questions and calibration arguments welcome — that’s what the digest is for.