Detroit publishes base zoning and zoning changes through separate services, so the parcel number must connect the revision code to New_Zoning, Amend_Date, and Ordinance. The dated clue in the base layer cannot answer whether a later map amendment changed that parcel. It is not an approval.
Last checked: August 7, 2026.
Begin the parcel-revision-to-ordinance sequence at Detroit Zoning Map Index, which supplies official zoning-map and agency workflow. Cross-check the selected geometry through Detroit official zoning layer, the route used for current mapped district schema. Before copying ZONING_REV, verify owner uses @detroitmi.gov and City of Detroit ArcGIS tenant qvkbeam7Wirps6zC; those markers keep the Detroit Zoning Changes service tied to the intended jurisdiction and record period.
ZONING_REV and New_Zoning should never be flattened into one label
Detroit's current and historical zoning records meet through exact identifiers. ZONING_REV supplies a revised symbol such as W1, M4, or R2. ZCODE_N provides a numeric cross-check such as 760, 340, or 120, and ZDESCR_N expands the district name, including Waterfront-Industrial District or Two-Family Residential District. The change archive then adds PARCELNO, New_Zoning, Amend_Date, and Ordinance. Those fields are not interchangeable: PARCELNO ties an action to land, New_Zoning states the recorded change, Amend_Date places it in time, and Ordinance points to the adopting instrument. A reliable Detroit result compares New_Zoning with current ZONING_REV, checks the numeric and descriptive fields for consistency, and retrieves the ordinance and legal description. The archive explains a possible transition; it does not independently certify today's district.
| Returned local record | Record to compare | When to stop | Next decision |
|---|---|---|---|
| ZONING_REV returns W1; M4; R2 | Compare with ZCODE_N, which stores the numeric district code | Stop the parcel-revision-to-ordinance sequence if ZCODE_N is missing, dated differently, or points to another record. | Continue through the Detroit Zoning Changes service: Search the exact symbol in the Detroit Zoning Ordinance. Then test whether ZCODE_N changes that route. |
| ZCODE_N returns 760; 340; 120 | Compare with ZDESCR_N, which expands the district name | Stop the parcel-revision-to-ordinance sequence if ZDESCR_N is missing, dated differently, or points to another record. | Continue through the Detroit Zoning Changes service: Use it to cross-check, not replace, the published district symbol and description. Then test whether ZDESCR_N changes that route. |
| ZDESCR_N returns Waterfront-Industrial District; Two-Family Residential District | Compare with PARCELNO, which identifies the parcel in the change archive | Stop the parcel-revision-to-ordinance sequence if PARCELNO is missing, dated differently, or points to another record. | Continue through the Detroit Zoning Changes service: Read the named district article and use table. Then test whether PARCELNO changes that route. |
| PARCELNO returns 01001920.006 | Compare with New_Zoning, which records the amended district in the change layer | Stop the parcel-revision-to-ordinance sequence if New_Zoning is missing, dated differently, or points to another record. | Continue through the Detroit Zoning Changes service: Match it to the current parcel before attaching an amendment. Then test whether New_Zoning changes that route. |
| New_Zoning returns SD2 | Compare with Amend_Date, which records the amendment date | Stop the parcel-revision-to-ordinance sequence if Amend_Date is missing, dated differently, or points to another record. | Continue through the Detroit Zoning Changes service: Compare the new district with current ZONING_REV and the ordinance. Then test whether Amend_Date changes that route. |
| Amend_Date returns 06/01/2017 | Compare with Ordinance, which points to the adopting ordinance | Stop the parcel-revision-to-ordinance sequence if Ordinance is missing, dated differently, or points to another record. | Continue through the Detroit Zoning Changes service: Separate the amendment date from the service refresh date. Then test whether Ordinance changes that route. |
| Ordinance returns 16-17 | Compare with ZONING_REV, which stores the revised zoning symbol | Stop the parcel-revision-to-ordinance sequence if ZONING_REV is missing, dated differently, or points to another record. | Continue through the Detroit Zoning Changes service: Retrieve the ordinance and legal description before treating the change as parcel-specific. Then test whether ZONING_REV changes that route. |
PARCELNO keeps the base layer and change service on the same land
The Detroit Zoning Changes service table keeps each returned label beside its displayed scope and the separate legal record still waiting to be opened. Its first checkpoint is ZONING_REV, which may appear as W1; M4; R2; from there, Search the exact symbol in the Detroit Zoning Ordinance. A blank in the parcel-revision-to-ordinance sequence 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_REV field | stores the revised zoning symbol | W1; M4; R2 | Search the exact symbol in the Detroit Zoning Ordinance. | Open exact record |
| ZCODE_N field | stores the numeric district code | 760; 340; 120 | Use it to cross-check, not replace, the published district symbol and description. | Open exact record |
| ZDESCR_N field | expands the district name | Waterfront-Industrial District; Two-Family Residential District | Read the named district article and use table. | Open exact record |
| PARCELNO field | identifies the parcel in the change archive | 01001920.006 | Match it to the current parcel before attaching an amendment. | Open exact record |
| New_Zoning field | records the amended district in the change layer | SD2 | Compare the new district with current ZONING_REV and the ordinance. | Open exact record |
| Amend_Date field | records the amendment date | 06/01/2017 | Separate the amendment date from the service refresh date. | Open exact record |
| Ordinance field | points to the adopting ordinance | 16-17 | Retrieve the ordinance and legal description before treating the change as parcel-specific. | Open exact record |
Start with the 10/5/2022 snapshot clue, then look for Amend_Date
Detroit, Michigan date check: The base layer name includes a 10/5/2022 snapshot clue, while the change service carries Amend_Date; both must be checked against the live city record before reliance.
The Detroit official zoning layer carries a base-layer name with a 10/5/2022 snapshot clue, while the zoning changes service carries Amend_Date for individual archive records. These dates describe different things. The snapshot clue marks the dataset context; Amend_Date marks the recorded zoning action; the ordinance carries its own adoption and legal-effect evidence. Detroit's zoning guidance supplies the live agency and ordinance workflow. Preserve all three before relying on W1, M4, R2, SD2, or another returned symbol. A service modified after 2022 does not by itself prove the mapped legal classification changed, and a 2017 amendment does not prove the archive row still matches current ZONING_REV. Scope also depends on PARCELNO and the ordinance legal description. Currency without a parcel match is not a defensible Detroit conclusion.
Reconstruct a Detroit amendment from district code to ordinance
- Open the Detroit Zoning Changes service; fix the parcel, boundary, jurisdiction, and official key before reading thematic records.
- Start the parcel-revision-to-ordinance sequence by copying ZONING_REV exactly as returned, including W1; M4; R2.
- Keep ZCODE_N in a second Detroit Zoning Changes service worksheet field because it stores the numeric district code.
- Test ZDESCR_N independently, then mark its value, service layer, or documented blank in the parcel-revision-to-ordinance sequence.
- Give PARCELNO and every later item a separate row; never compress history, plans, and overlays into the Detroit Zoning Changes service result.
- Attach the Detroit Zoning Changes service lookup time to ZONING_REV, while preserving this separate currency clue: The base layer name includes a 10/5/2022 snapshot clue, while the change service carries Amend_Date; both must be checked against the live city record before reliance.
- If ZONING_REV and ZCODE_N conflict, send the parcel-revision-to-ordinance sequence to Detroit Zoning Map Index and ask whether a later amendment displaced the base-service snapshot.
The Detroit Zoning Changes service worksheet is complete only when another reader can reproduce the parcel-revision-to-ordinance sequence from the same parcel key and official pages. Keep each source's legal role and effective date apart, then record whether a later amendment displaced the base-service snapshot as unresolved instead of selecting the most convenient output. The local currency note remains part of that audit trail: The base layer name includes a 10/5/2022 snapshot clue, while the change service carries Amend_Date; both must be checked against the live city record before reliance.
A parcel can show an old description beside a later action
For a hypothetical Detroit record, the change layer returns PARCELNO 01001920.006, New_Zoning SD2, Amend_Date 06/01/2017, and Ordinance 16-17. The researcher first matches that parcel number to the current parcel and property address. Ordinance 16-17 and its legal description are then retrieved to confirm that the action actually covers the selected land. Current ZONING_REV is compared with SD2; a mismatch is preserved rather than resolved by choosing the older row. ZCODE_N and ZDESCR_N are used to cross-check the current symbol and locate the correct ordinance article, but neither replaces ZONING_REV. Amend_Date is recorded as the amendment date, not as the GIS service refresh date. This hypothetical workflow prevents a valid historic action on one parcel from being reported as the present zoning of a nearby parcel.
When the base service and Zoning Changes disagree
| Local situation | What went wrong | What to retain | How to resolve it |
|---|---|---|---|
| Scenario 1 | A legacy change-archive row is reported as the current zoning without comparing ZONING_REV. | Preserve ZDESCR_N, the selected geometry, and both timestamps from the Detroit Zoning Changes service check. | Use Detroit Zoning Map Index to settle whether a later amendment displaced the base-service snapshot; then Read the named district article and use table. |
| Scenario 2 | An ordinance number is attached to a nearby parcel because PARCELNO and PROPADDR were not reconciled. | Preserve PARCELNO, the selected geometry, and both timestamps from the Detroit Zoning Changes service check. | Use Detroit Zoning Map Index to settle whether a later amendment displaced the base-service snapshot; then Match it to the current parcel before attaching an amendment. |
When a Detroit legacy change row was reported as current zoning, retain the row as history and compare New_Zoning with current ZONING_REV. Add the base-layer snapshot clue, current query date, Amend_Date, and ordinance date as separate evidence. When Ordinance 16-17 or another ordinance was attached to the wrong land, reconcile PARCELNO, property address, current parcel geometry, and the ordinance legal description before continuing. The agency question should quote the disagreement: For parcel 01001920.006, does current ZONING_REV reflect the district established by the cited New_Zoning and ordinance, and what effective record controls today? Attach ZCODE_N and ZDESCR_N only as cross-checks. This correction preserves useful amendment history while preventing a nearby parcel, stale archive row, or service date from being elevated into a current legal determination.
Give the map index and change service different evidence jobs
| Official page | What to check there | Local coverage shown |
|---|---|---|
| Detroit Zoning Map Index | official zoning-map and agency workflow | Current official Detroit BSEED page |
| Detroit official zoning layer | current mapped district schema | City ArcGIS owner [email protected] |
| Detroit zoning changes layer | parcel amendment history | Same City ArcGIS tenant and zoning-change scope |
How should ZONING_REV be checked in Detroit, Michigan?
Open the official ZONING_REV record and capture the value inside the Detroit Zoning Changes service. That record shows how ZONING_REV stores the revised zoning symbol; one displayed form is W1; M4; R2. Place the copied value in the parcel-revision-to-ordinance sequence, then follow its separate rule route: Search the exact symbol in the Detroit Zoning Ordinance.
How should ZCODE_N be checked in Detroit, Michigan?
Open the official ZCODE_N record and capture the value inside the Detroit Zoning Changes service. That record shows how ZCODE_N stores the numeric district code; one displayed form is 760; 340; 120. Place the copied value in the parcel-revision-to-ordinance sequence, then follow its separate rule route: Use it to cross-check, not replace, the published district symbol and description.
How should ZDESCR_N be checked in Detroit, Michigan?
Open the official ZDESCR_N record and capture the value inside the Detroit Zoning Changes service. That record shows how ZDESCR_N expands the district name; one displayed form is Waterfront-Industrial District; Two-Family Residential District. Place the copied value in the parcel-revision-to-ordinance sequence, then follow its separate rule route: Read the named district article and use table.
- 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 Detroit Zoning Changes service 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-revision-to-ordinance sequence leaves competing official results or when substantial reliance is planned. A useful request to Detroit Zoning Map Index identifies the parcel, quotes ZONING_REV and ZCODE_N, gives their source dates, and asks whether a later amendment displaced the base-service snapshot.
Use detroit zoning map by address, zoning code vs zoning map, zoning overlays special districts only where those methods clarify the parcel-revision-to-ordinance sequence. The Detroit Zoning Changes service evidence linked for ZONING_REV and ZCODE_N remains the local starting point.
Reviewed August 7, 2026. Recheck the Detroit Zoning Changes service, its cited ordinance, and the agency procedure before relying on the saved worksheet.