MapIndy carries present zoning, rezoning history, context, and land-use plans in different operational layers. Reconstruct LABEL, CODE1, and CODE2 on one parcel before a Compact Context Area or planning overlay is allowed to influence the code search. It is not an approval.
Last checked: August 7, 2026.
Begin the parcel-code-to-rezoning-history chain at MapIndy, which supplies parcel and map lookup. Cross-check the selected geometry through Indianapolis planning and zoning map service, the route used for exact layer and zoning schema. Before copying Zoning (layer 9), verify gis.indy.gov official host and OpenData_PlanningZoning service; those markers keep the MapIndy layer route tied to the intended jurisdiction and record period.
MapIndy layer 9 is not the same record as plan layers 13 and 14
MapIndy separates Indianapolis zoning into operational layers that should stay separate in the evidence record. Zoning layer 9 returns the mapped polygon; within it, LABEL is the displayed code and CODE1 is the primary code. CODE2 can supply a secondary value, but a blank sampled row is only a data state. Rezoning layer 8 adds history that must be traced to a final decision and effective date. Compact Context Area layer 10 identifies the context used when ordinance standards vary by compact or metro geography. DMD Land Use Plan Base and Overlay layers 13 and 14 publish policy designations, not the legal district. A code such as SU2 must be preserved exactly because its special-purpose ordinance provision cannot be replaced with a broad residential or commercial description. The complete chain is parcel, layer 9 code, context, any history, and then the ordinance.
| Returned local record | Record to compare | When to stop | Next decision |
|---|---|---|---|
| Zoning (layer 9) returns layer ID 9 | Compare with LABEL, which stores the displayed zoning code | Stop the parcel-code-to-rezoning-history chain if LABEL is missing, dated differently, or points to another record. | Continue through the MapIndy layer route: Read the exact LABEL in the Indianapolis zoning ordinance. Then test whether LABEL changes that route. |
| LABEL returns D1; SU2; D7 | Compare with CODE1, which stores the primary zoning code | Stop the parcel-code-to-rezoning-history chain if CODE1 is missing, dated differently, or points to another record. | Continue through the MapIndy layer route: Preserve SU and other special-purpose codes exactly. Then test whether CODE1 changes that route. |
| CODE1 returns D1; SU2; D7 | Compare with CODE2, which stores a secondary zoning code when supplied | Stop the parcel-code-to-rezoning-history chain if CODE2 is missing, dated differently, or points to another record. | Continue through the MapIndy layer route: Compare with LABEL and investigate any difference. Then test whether CODE2 changes that route. |
| CODE2 returns blank in sampled rows | Compare with Rezoning (layer 8), which locates rezoning history records | Stop the parcel-code-to-rezoning-history chain if Rezoning (layer 8) is missing, dated differently, or points to another record. | Continue through the MapIndy layer route: A blank is a returned data state, not proof that no secondary control exists. Then test whether Rezoning (layer 8) changes that route. |
| Rezoning (layer 8) returns layer ID 8 | Compare with Compact Context Area (layer 10), which identifies the compact/metro zoning context | Stop the parcel-code-to-rezoning-history chain if Compact Context Area (layer 10) is missing, dated differently, or points to another record. | Continue through the MapIndy layer route: A rezoning layer record must be traced to its final decision and effective date. Then test whether Compact Context Area (layer 10) changes that route. |
| Compact Context Area (layer 10) returns layer ID 10 | Compare with DMD Land Use Plan Base / Overlay (layers 13 and 14), which shows plan designations and plan overlays | Stop the parcel-code-to-rezoning-history chain if DMD Land Use Plan Base / Overlay (layers 13 and 14) is missing, dated differently, or points to another record. | Continue through the MapIndy layer route: Use the context when the ordinance makes standards context-dependent. Then test whether DMD Land Use Plan Base / Overlay (layers 13 and 14) changes that route. |
| DMD Land Use Plan Base / Overlay (layers 13 and 14) returns layer IDs 13 and 14 | Compare with Zoning (layer 9), which returns the mapped zoning polygon | Stop the parcel-code-to-rezoning-history chain if Zoning (layer 9) is missing, dated differently, or points to another record. | Continue through the MapIndy layer route: Plan layers guide policy but do not replace the zoning code. Then test whether Zoning (layer 9) changes that route. |
LABEL, CODE1, and CODE2 build the operative district string
The MapIndy layer route table keeps each returned label beside its displayed scope and the separate legal record still waiting to be opened. Its first checkpoint is Zoning (layer 9), which may appear as layer ID 9; from there, Read the exact LABEL in the Indianapolis zoning ordinance. A blank in the parcel-code-to-rezoning-history chain stays visible so another reader can distinguish an empty official return from an unexamined field.
| Local field, layer, or record | What it does | Displayed value or scope | Next code or record check | Official page |
|---|---|---|---|---|
| Zoning (layer 9) layer | returns the mapped zoning polygon | layer ID 9 | Read the exact LABEL in the Indianapolis zoning ordinance. | Open exact record |
| LABEL field | stores the displayed zoning code | D1; SU2; D7 | Preserve SU and other special-purpose codes exactly. | Open exact record |
| CODE1 field | stores the primary zoning code | D1; SU2; D7 | Compare with LABEL and investigate any difference. | Open exact record |
| CODE2 field | stores a secondary zoning code when supplied | blank in sampled rows | A blank is a returned data state, not proof that no secondary control exists. | Open exact record |
| Rezoning (layer 8) layer | locates rezoning history records | layer ID 8 | A rezoning layer record must be traced to its final decision and effective date. | Open exact record |
| Compact Context Area (layer 10) layer | identifies the compact/metro zoning context | layer ID 10 | Use the context when the ordinance makes standards context-dependent. | Open exact record |
| DMD Land Use Plan Base / Overlay (layers 13 and 14) layers | shows plan designations and plan overlays | layer IDs 13 and 14 | Plan layers guide policy but do not replace the zoning code. | Open exact record |
Keep Compact Context Area beside the result without calling it zoning
In a hypothetical Indianapolis lookup, Zoning layer 9 returns LABEL SU2 and CODE1 SU2, while CODE2 is blank. The researcher records the blank without treating it as proof that no secondary control exists. SU2 is searched exactly in the Indianapolis zoning ordinance rather than generalized to a familiar use family. Rezoning layer 8 is then checked; if it returns a record, the final decision and effective date are retrieved before it is used to explain the current code. Compact Context Area layer 10 is opened to determine whether context-dependent standards apply. If DMD Land Use Plan Base or Overlay layers 13 and 14 show a plan designation, that result is placed in a policy column and not substituted for SU2. The hypothetical remains a code-and-record inquiry, not a claim that the special use or plan designation approves a proposal.
Move from the parcel to rezoning layer 8 before reading plan overlays
- Open the MapIndy layer route; fix the parcel, boundary, jurisdiction, and official key before reading thematic records.
- Start the parcel-code-to-rezoning-history chain by copying Zoning (layer 9) exactly as returned, including layer ID 9.
- Keep LABEL in a second MapIndy layer route worksheet field because it stores the displayed zoning code.
- Test CODE1 independently, then mark its value, service layer, or documented blank in the parcel-code-to-rezoning-history chain.
- Give CODE2 and every later item a separate row; never compress history, plans, and overlays into the MapIndy layer route result.
- Attach the MapIndy layer route lookup time to Zoning (layer 9), while preserving this separate currency clue: Record the MapIndy query date and separately verify the effective date of any rezoning decision or ordinance text associated with the returned code.
- If Zoning (layer 9) and LABEL conflict, send the parcel-code-to-rezoning-history chain to MapIndy and ask whether plan context is being mistaken for operative zoning.
The MapIndy layer route worksheet is complete only when another reader can reproduce the parcel-code-to-rezoning-history chain from the same parcel key and official pages. Keep each source's legal role and effective date apart, then record whether plan context is being mistaken for operative zoning as unresolved instead of selecting the most convenient output. The local currency note remains part of that audit trail: Record the MapIndy query date and separately verify the effective date of any rezoning decision or ordinance text associated with the returned code.
When a planning designation is reported as an Indianapolis district
| Local situation | What went wrong | What to retain | How to resolve it |
|---|---|---|---|
| Scenario 1 | A DMD land-use-plan layer is reported as the parcel's legal zoning. | Preserve CODE1, the selected geometry, and both timestamps from the MapIndy layer route check. | Use MapIndy to settle whether plan context is being mistaken for operative zoning; then Compare with LABEL and investigate any difference. |
| Scenario 2 | An SU2 or other special-use code is generalized to a residential/commercial label without opening its ordinance provision. | Preserve CODE2, the selected geometry, and both timestamps from the MapIndy layer route check. | Use MapIndy to settle whether plan context is being mistaken for operative zoning; then A blank is a returned data state, not proof that no secondary control exists. |
If a DMD land-use-plan layer was reported as the parcel's legal zoning, move the layer 13 or 14 result into a plan-policy field and restore the code from Zoning layer 9. If SU2 or another special-purpose LABEL was converted into a generic residential or commercial category, restore LABEL and CODE1 character for character and open the specific ordinance provision. Compare any layer 8 rezoning record with its final decision and effective date, and retain layer 10 context separately. A focused city-county question is: For this MapIndy parcel, what current layer 9 LABEL and CODE1 control, does CODE2 have a legally relevant blank or secondary value, and which effective action supports any layer 8 history? Attach the plan-layer results only to clarify policy scope. This asks for the correct record chain without converting a plan or special-use code into approval.
Query date and rezoning effective date should not share one cell
Indianapolis and Marion County, Indiana date check: Record the MapIndy query date and separately verify the effective date of any rezoning decision or ordinance text associated with the returned code.
MapIndy supplies parcel and map lookup, the Indianapolis planning and zoning map service defines layers 8, 9, 10, 13, and 14, and the Indianapolis zoning page supplies code and application guidance. Record the MapIndy query date independently from the effective date of any rezoning decision or ordinance text associated with LABEL or CODE1. A service refresh can change data presentation without changing the law, while a rezoning decision can become effective on a date not visible in the layer name. Plan layers also have policy scope regardless of how current their metadata appears. When CODE2 is blank, preserve that service state and continue the official code and case search. Indianapolis currency is demonstrated by matching the parcel and returned code to an effective legal instrument, not by choosing the newest timestamp among unrelated sources.
Use MapIndy, OpenData PlanningZoning, and city guidance in separate roles
| Official page | What to check there | Local coverage shown |
|---|---|---|
| MapIndy | parcel and map lookup | Official Indianapolis map portal |
| Indianapolis planning and zoning map service | exact layer and zoning schema | Official gis.indy.gov service |
| Indianapolis zoning | code and application guidance | Official city-county page |
How should Zoning (layer 9) be checked in Indianapolis and Marion County, Indiana?
Open the official Zoning (layer 9) record and capture the value inside the MapIndy layer route. That record shows how Zoning (layer 9) returns the mapped zoning polygon; one displayed form is layer ID 9. Place the copied value in the parcel-code-to-rezoning-history chain, then follow its separate rule route: Read the exact LABEL in the Indianapolis zoning ordinance.
How should LABEL be checked in Indianapolis and Marion County, Indiana?
Open the official LABEL record and capture the value inside the MapIndy layer route. That record shows how LABEL stores the displayed zoning code; one displayed form is D1; SU2; D7. Place the copied value in the parcel-code-to-rezoning-history chain, then follow its separate rule route: Preserve SU and other special-purpose codes exactly.
How should CODE1 be checked in Indianapolis and Marion County, Indiana?
Open the official CODE1 record and capture the value inside the MapIndy layer route. That record shows how CODE1 stores the primary zoning code; one displayed form is D1; SU2; D7. Place the copied value in the parcel-code-to-rezoning-history chain, then follow its separate rule route: Compare with LABEL and investigate any difference.
- Selected parcel key, geometry, and responsible jurisdiction
- Every returned value from the local field table
- Page titles, URLs, lookup times, and update clues
- Opened code, plan, case, ordinance, or metadata records
- Unresolved blanks, boundary splits, dates, and competing outputs
- Proposed activity stated in code-relevant facts
- Agency contact, narrow question, reply date, and limits
The MapIndy layer route does not decide title, survey boundaries, private restrictions, vested rights, building-code compliance, utilities, licensing, or permit issuance. Request a written response when the parcel-code-to-rezoning-history chain leaves competing official results or when substantial reliance is planned. A useful request to MapIndy identifies the parcel, quotes Zoning (layer 9) and LABEL, gives their source dates, and asks whether plan context is being mistaken for operative zoning.
Use indianapolis zoning map by address, zoning code vs zoning map, zoning overlays special districts only where those methods clarify the parcel-code-to-rezoning-history chain. The MapIndy layer route evidence linked for Zoning (layer 9) and LABEL remains the local starting point.
Reviewed August 7, 2026. Recheck the MapIndy layer route, its cited ordinance, and the agency procedure before relying on the saved worksheet.