Grand Rapids, MI Zoning

Euclidean-zoning. 20 districts · 6 overlays · 5 applicable state preemptions.

Overview

Code type
euclidean
Naming convention
mixed
Naming convention by category
residentialCompound: {Neighborhood Classification}-{Density Class}. Neighborhood = TN (Traditional Neighborhood) / MCN (Mid-20th Century Neighborhood) / MON (Modern Era Neighborhood); Density = LDR (Low-Density Residential) / MDR (Mixed-Density Residential). Six base residential zones: TN-LDR, TN-MDR, MCN-LDR, MCN-MDR, MON-LDR, MON-MDR.
mixed_use_commercialCompound + role: TN-CC (City Center), TN-TCC (Transitional City Center), TN-TBA (Traditional Business Area / Linear), TN-TOD (Transit-Oriented Development), MCN-C (Commercial), MCN-TOD, MON-C, MON-TOD, NOS (Neighborhood Office Service — stand-alone, not Neighborhood Classified)
special_districtsSD-AP (Airport), SD-OS (Open Space), SD-IT (Industrial-Transportation), SD-IC (Institutional Campus), SD-PRD (Planned Redevelopment)
overlaysOD-DH (Downtown Height), OD-GR (Grand River), OD-EBL (East Beltline), OD-FP (Floodplain), OD-WS (Wayfinding Signs), OD-SC (Special Conditions)

2017 Chapter 61 introduces the Neighborhood Classification framework — every base residential and most commercial zones inherit context from one of three historical-era neighborhood types (TN/MCN/MON). Same density class (e.g., LDR) carries different lot-area and setback minimums in each Neighborhood Classification. v1 profile codes like 'LDR-TN', 'MUC-L', 'MUC-Core', 'TBA', 'TCC', 'SD-NOS' are corruptions / partial transliterations of the actual code names: TN-LDR, TN-TBA, TN-CC, TN-TCC, NOS. | naming_convention_raw=neighborhood-class + density-class compound ; sub_flags_raw=[neighborhood-classification-framework, form-influenced, midwest-mid-size]

Worth knowing
  • Neighborhood Classification framework (TN/MCN/MON) is the foundational structural device — same density class (LDR or MDR) carries different lot-area, lot-width, setback, and height standards depending on Neighborhood Classification. The compound code (e.g., MCN-LDR) is essential to retrieve the correct dimensional rule.
  • MDR is wider than 'medium density' suggests — it covers ATTACHED SF, two-family, and MULTI-FAMILY by-right (not just middle-density forms). LDR is restricted to detached SF + AFC family home + ADU by-right with attached/two-family/multi-family pushed to Special Land Use.
  • TN uses Required Building Line (RBL) — building face must be placed AT the RBL, not behind it. MCN-LDR/MDR also uses RBL. MON uses traditional front setback (face can be at or behind setback line). This is the form-based-influenced design device imported into a Euclidean chassis.

+ 7 more in Quirks & notes

Districts

mu 5spec 4res_sf 3res_mf 3com 2cbd 1off 1ind 1
CodeNameCategory Min lotHeight CoverageFAR Du/acParking Setbacks F/S/R
TN-LDRTN-LDR Traditional Neighborhood — Low-Density Residentialres_sf3,800 sf[4]35 ft[5][6][7]11.5[8][9]27[1] / 5[2] / 25[3]
TN-MDRTN-MDR Traditional Neighborhood — Mixed-Density Residentialres_mf2,500 sf[13]45 ft[14][15][16]17.4[17][18]22[10] / 5[11] / 20[12]
MCN-LDRMCN-LDR Mid-20th Century Neighborhood — Low-Density Residentialres_sf5,000 sf[22]35 ft[23][24][25]8.7[26][27]35[19] / 7[20] / 25[21]
MCN-MDRMCN-MDR Mid-20th Century Neighborhood — Mixed-Density Residentialres_mf3,000 sf[31]45 ft[32][33][34]14.5[35][36]30[28] / 5[29] / 30[30]
MON-LDRMON-LDR Modern Era Neighborhood — Low-Density Residentialres_sf7,000 sf[40]35 ft[41][42][43]6.2[44][45]30[37] / 7[38] / 40[39]
MON-MDRMON-MDR Modern Era Neighborhood — Mixed-Density Residentialres_mf3,500 sf[49]52 ft[50][51][52]12.4[53][54]20[46] / 7[47] / 30[48]
TN-CCTN-CC Traditional Neighborhood — City Centercbd[58][59][60][61][62]14[55] / 0[56] / 0[57]
TN-TCCTN-TCC Traditional Neighborhood — Transitional City Centermu[66][67][68][69][70]19[63] / 0[64] / 10[65]
TN-TBATN-TBA Traditional Neighborhood — Traditional Business Area (Linear)mu3,000 sf[74][75][76][77][78]19[71] / 0[72] / 18[73]
TN-TODTN-TOD Traditional Neighborhood — Transit-Oriented Developmentmu[82][83][84][85][86]19[79] / 0[80] / 18[81]
MCN-CMCN-C Mid-20th Century Neighborhood — Commercialcom4,000 sf[90][91][92][93][94]20[87] / 10[88] / 25[89]
MCN-TODMCN-TOD Mid-20th Century Neighborhood — Transit-Oriented Developmentmu[98][99][100][101][102]19[95] / 0[96] / 18[97]
MON-CMON-C Modern Era Neighborhood — Commercialcom4,000 sf[106][107][108][109][110]25[103] / 10[104] / 25[105]
MON-TODMON-TOD Modern Era Neighborhood — Transit-Oriented Developmentmu[114][115][116][117][118]19[111] / 0[112] / 18[113]
NOSNOS Neighborhood Office Serviceoff5,000 sf[122][123][124][125][126]25[119] / 10[120] / 25[121]
SD-APSD-AP Special District — Airportspec[130][131][132][133][134][127] / [128] / [129]
SD-OSSD-OS Special District — Open Spacespec[138][139][140][141][142][135] / [136] / [137]
SD-ITSD-IT Special District — Industrial-Transportationind10,000 sf[146][147][148][149][150]25[143] / 25[144] / 25[145]
SD-ICSD-IC Special District — Institutional Campusspec[154][155][156][157][158][151] / [152] / [153]
SD-PRDSD-PRD Special District — Planned Redevelopmentspec[162][163][164][165][166][159] / [160] / [161]

Confidence: confirmed partial under review not found

Overlays

OD-DH
Downtown Height Overlay District
DT
c§5.8.02 (Grand Rapids Chapter 61)

Geographic — Map A of the Zoning Map depicts the boundaries of the Downtown Height Overlay area. Pairs with Section 5.08.03 Grand River Overlay subareas for properties in both.

purposeAllow a variety of building heights in Downtown that sustain it as a regional asset
base_height_modificationBonus heights added to base district per Table 5.6.08.A; subareas govern by-subarea base + bonus
bonus_height_criteria§5.8.02.G — public benefits (e.g., public access easements, affordable housing per §5.6.08.B.3 bonus table) earn additional stories
interaction_with_grand_river_overlay§5.8.02.H — projects in both OD-DH and OD-GR may earn height bonuses per Table 5.8.02.G.2 with combined criteria
bonus_table_referenceTable 5.6.08.B.3 Bonus Table — public-benefit menu including affordability, urban open space, public access
tn_cc_specialBonus heights for TN-CC Zone District described in §5.8.02.C under the OD-DH framework
OD-GR
Grand River Overlay District
ENV
c§5.8.03 (Grand Rapids Chapter 61)

Geographic — parcels fronting / abutting Grand River corridor. Capitalizes on river as an asset; transition from historic industrial use to open space and mixed-use development.

allowed_uses_baselineAll uses in TN-TCC (Transitional City Center) Zone District allowed in OD-GR per §5.8.03.C
site_layout_tableTable 5.8.03.D — Site Layout and Building Placement (overrides base district where specified)
building_elements_tableTable 5.8.03.E — Building Elements (overrides base district where specified)
height_bonus_interactionCombined with OD-DH per §5.8.02.H; bonuses in Table 5.8.02.G.2
public_access_bonus30-ft public access easement earns bonus height per §5.8.02 Bonus Heights table for OD-DH+OD-GR
river_protection_intentQuality of life + new mixed-use introduction along riverfront
OD-EBL
East Beltline Overlay District
COR
c§5.8.04 (Grand Rapids Chapter 61)

Geographic — East Beltline corridor frontage. Designed to establish development character along East Beltline arterial.

corridor_characterEstablishment of particular development character along East Beltline
review_trackadditional design-review requirements per §5.8.04
dimensional_parametersnot_captured — full §5.8.04 table not extracted in this v2 pass; would require Municode access to current text
OD-FP
Floodplain Overlay District
FP
c§5.8.05 (Grand Rapids Chapter 61); FEMA NFIP framework via MCL 324.31501 et seq.

Property within FEMA-mapped Special Flood Hazard Area (1% annual chance / 100-year floodplain) per Grand Rapids FIRM panels for Kent County.

fema_referenceFEMA FIRM panels for Kent County / Grand Rapids
bfe_complianceBase Flood Elevation + freeboard required for new construction / substantial improvement
substantial_improvement_threshold50% of pre-improvement market value (NFIP standard)
fill_excavation_reviewpermit + no-rise certification required for fill in floodway
interaction_with_grand_river_overlayProperties along Grand River frequently subject to both OD-FP and OD-GR; OD-FP elevation overrides apply
freeboard_incrementnot_captured — GR-specific freeboard inches above BFE not extracted in this v2 pass
OD-WS
Wayfinding Signs Overlay District
SPD
c§5.8.06 (Grand Rapids Chapter 61)

Designated areas where wayfinding sign program operates — typically downtown and major destinations.

sign_programCity-managed wayfinding sign system
applicable_zone_classesTN-CC; TCC; TBA; TOD
dimensional_parametersnot_captured — sign-specific dimensions not extracted
OD-SC
Special Conditions Overlay District
SPD
c§5.8.07 (Grand Rapids Chapter 61)

Parcel-by-parcel special conditions imposed via City Commission action under the overlay framework — used for negotiated conditions on rezonings and PUD-like situations.

use_patternNegotiated parcel-specific conditions layered onto base district
review_authorityCity Commission imposes conditions per §5.8.07
applies_to_zonesany base district
common_usesParcels in TN-CC subject to §5.8.07.D special-conditions track; TN-TBA parcels subject to §5.8.07.C
dimensional_parametersvaries per parcel-specific condition list

State preemptions

MI-MZEA-125-3205-IZ-banapplies
Qualifying condition
Grand Rapids operates voluntary / incentive-based affordability programs (density bonuses, FAR bonuses, fee waivers) per state preemptions.json city_specific_overrides for mi-mcl-125-3205-iz-ban. Chapter 61 Section 5.6.08.B (commercial bonuses) and Section 5.5.06.I (residential bonuses) are incentive-track, not mandatory-set-aside.
Effect
Grand Rapids may NOT condition zoning approvals on below-market unit set-asides as a zoning requirement. Existing voluntary density/FAR bonuses tied to affordable units in §5.6.08.B / §5.5.06.I remain permissible because they are opt-in incentives, not zoning mandates.
MI-MZEA-125-3207-moratoriaapplies
Qualifying condition
All MI local units exercising zoning under the MZEA are subject to §3207 moratorium duration caps. Grand Rapids' ZoneGR rewrite process has not employed a §3207 moratorium and could not without complying with statutory safeguards.
Effect
Any Grand Rapids moratorium ordinance is subject to MZEA §3207 durational caps and concurrent-study requirements; cannot function as de facto permanent ban.
MI-MZEA-125-3206-group-homesapplies
Qualifying condition
Licensed adult foster-care family homes serving 6 or fewer adults must be treated as a residential use in all districts where SF homes are permitted. Per Chapter 61 Table 5.5.05 use table, AFC family homes (1-6 residents) are listed as Permitted use in both LDR and MDR — already statute-compliant.
Effect
Grand Rapids may not impose conditional-use, special-exception, or distance-separation requirements on licensed AFC family homes (≤6 residents) in LDR or MDR. Small (7-12) and large (13-20) group homes are appropriately tracked as Special Land Use.
MI-MZEA-125-3206-manufactured-housingapplies
Qualifying condition
HUD-code manufactured homes may not be excluded from R districts based on construction method. Chapter 61 Table 5.5.05 lists 'Manufactured housing community' as Permitted in MDR districts. Apparent compliance with §3206 parity rule.
Effect
Any Chapter 61 standard that singles out manufactured-construction methods for stricter treatment in LDR/MDR is facially invalid. Mobile-home parks separately governed by MCL 125.2301 et seq.
MI-HB5585-statewide-aduapplies
Qualifying condition
HB 5585 (103rd Legislature, introduced Feb 2026) — if enacted — would make ADUs by-right in residential districts statewide, prohibit density-counting, prohibit parking minimums, and prohibit owner-occupancy requirements. Status as of 2026-05-18: PENDING in House Committee on Government Operations. Chapter 61 currently lists ADU as 'QR' (Quasi-required / quietly-regulated) in both LDR and MDR per §5.9.03 — locally regulated.
Effect
If enacted, Grand Rapids would lose discretion over ADU density-counting, parking, and owner-occupancy in LDR/MDR; §5.9.03 ADU framework would be partially displaced. Impact deferred until enactment.

Adopted building codes

Statewide

2021
2015
2023
Local
IECC (Residential)
2015
IECC (Commercial)
2015

Click a code label to open its state-by-state adoption atlas.

Quirks & notes

  • Neighborhood Classification framework (TN/MCN/MON) is the foundational structural device — same density class (LDR or MDR) carries different lot-area, lot-width, setback, and height standards depending on Neighborhood Classification. The compound code (e.g., MCN-LDR) is essential to retrieve the correct dimensional rule.
  • MDR is wider than 'medium density' suggests — it covers ATTACHED SF, two-family, and MULTI-FAMILY by-right (not just middle-density forms). LDR is restricted to detached SF + AFC family home + ADU by-right with attached/two-family/multi-family pushed to Special Land Use.
  • TN uses Required Building Line (RBL) — building face must be placed AT the RBL, not behind it. MCN-LDR/MDR also uses RBL. MON uses traditional front setback (face can be at or behind setback line). This is the form-based-influenced design device imported into a Euclidean chassis.
  • Bonus heights are accessed via Table 5.6.08.B.3 menu — affordability, urban open space, public access easement (Grand River), qualifying transit station proximity all earn additional stories. OD-DH and OD-GR overlays stack additional bonus tiers on top of Table 5.6.08.A base height.
  • Min lot area per dwelling unit (NOT du/ac) is the primary density metric. TN-LDR detached SF interior 3,800 sf/unit (~11.5 du/ac), MON-LDR 7,000 sf/unit (~6.2 du/ac).
  • Side setbacks for commercial use abutting ground-floor residential carry a stricter dimension (15 ft in MCN-C, 10 ft in TN-CC/TCC/TBA) than for all-other cases — a use-context modifier embedded in the dimensional table.
  • SD-IT side/rear setbacks are height-tied for parcels adjacent to residential or SD-OS — 'equal to the height of the building' (with 15 ft landscape buffer min) — uncommon in MI codes and creates a slope-dependent envelope for industrial-residential interfaces.
  • NOS was inserted post-2017 by Ord. No. 2020-13 (4-28-20) as a stand-alone non-Neighborhood-Classified district — the only commercial district outside the TN/MCN/MON framework. Reflects a post-rewrite recognition that some commercial parcels don't fit a neighborhood-era classification.
  • OD-GR Grand River Overlay imports the TN-TCC use list wholesale (§5.8.03.C) — a use-substitution overlay pattern (the entire use list of a different base district) rather than a use-addition overlay pattern (additions to existing base list).
  • Single-family attached has different treatment in LDR by Neighborhood Classification — only Special Land Use in TN-LDR (or Permitted if parcel within 500 ft of TBA/TOD/TCC/C), Permitted in MDR. Hard distance threshold creates a measurable proximity-based use right.

Formulas

Definitions

height
Measured per Section 5.2.06. Building Height (Measurement). Story counts in §5.5.07.A use half-story increments (e.g., 2½ stories / 35 ft for LDR). First/ground floor must be at or above grade for TN Neighborhood Classification.
lot_coverage
Not the primary intensity lever in Chapter 61 — replaced by Building Façade Along RBL %, Minimum Green Space at Grade %, and Minimum Tree Canopy %.
far
Not used as a primary intensity metric in Chapter 61. Intensity controlled via: min lot area per dwelling unit, max stories / max feet, RBL placement, transparency %, façade-along-RBL %, and bonus criteria in §5.6.08.B.
du_ac
Inverse — Chapter 61 expresses density as 'minimum lot area per dwelling unit' rather than du/ac. LDR detached SF interior: 3,800 sf/unit (TN), 5,000 sf (MCN), 7,000 sf (MON) ≈ 11.5 / 8.7 / 6.2 du/ac. MDR detached SF interior: 2,500 sf (TN), 3,000 sf (MCN), 3,500 sf (MON) ≈ 17.4 / 14.5 / 12.4 du/ac.
setback_front
Either RBL (Required Building Line — 27/22/35/30 ft for TN/MCN residential) or front setback (20/25 ft for MON residential / commercial). MON gets a traditional setback; TN/MCN get an RBL meaning building face must be at or behind the RBL line.
setback_side
Interior side setback table in §5.5.06.E. — LDR 5/7/7 ft TN/MCN/MON, MDR 5/5/7 ft. Aggregate (both sides) 14/18/18 ft LDR; 14/14/20 ft MDR.
setback_rear
§5.5.06.F. — LDR 25/25/40 ft TN/MCN/MON; MDR 20/30/30 ft.
parking
Off-street parking minimums controlled by Article 5 Section 5.X (not extracted in this pass). TN-CC, TCC, TBA, TOD zones get reduced parking (2 spaces/unit cap referenced in §5.6.08 narratives).
rbl
Required Building Line — Chapter 61 form-influenced device. Building façade must be placed on the RBL with façade-along-RBL % requirements (60/60/50/50 in TN/MCN LDR/MDR; 90/80/70/70% in CC/TCC/TBA/TOD).
green_space
Minimum Green Space at Grade (% of lot area): SF detached 40/50/60 LDR / 30/40/50 MDR (TN/MCN/MON). Replaces traditional max-impervious lever.

Capacity calculations

max_units_lot
lot_area_sf / min_lot_area_per_unit (use district + classification specific value from Table 5.5.06.A)
max_footprint_sf
lot_area_sf * (1 - green_space_pct / 100)
max_height_ft
Table 5.5.07.A height (35-52 ft for residential by-right; 60-120 ft via Special Land Use)
buildable_width_ft
lot_width_ft - aggregate_side_setback_ft
buildable_depth_ft
lot_depth_ft - front_setback_or_rbl_ft - rear_setback_ft

Massing explorer

Interactive 3D comparison across every district. Drag to orbit, scroll to zoom, use the slider to walk districts, and toggle applicable overlays in the right-side panel.

Sort by
LOW
HIGH
drag to orbit · scroll to zoom
Max height
ft
Floor area ratio
Lot coverage
%
Setbacks (F / S / R)
ft
Parking
/unit
Max density
du/ac
Min lot size
sf
Copy zoning profile
Loading…
District Category Height FAR Coverage Setbacks Parking Density Min lot Overlays

Sources & references

Citations
  1. [1] §5.5.06.A
  2. [2] §5.5.06.A / E
  3. [3] §5.5.06.A / F
  4. [4] §5.5.06.A Table
  5. [5] §5.5.07.A Table
  6. [6] z
  7. [7] z
  8. [8] §5.5.06.A (derived from 3800 sf/unit detached SF)
  9. [9] z
  10. [10] §5.5.06.A
  11. [11] §5.5.06.A / E
  12. [12] §5.5.06.A / F
  13. [13] §5.5.06.A Table
  14. [14] §5.5.07.A Table
  15. [15] z
  16. [16] z
  17. [17] §5.5.06.A (derived from 2500 sf/unit detached SF)
  18. [18] z
  19. [19] §5.5.06.A
  20. [20] §5.5.06.A / E
  21. [21] §5.5.06.A / F
  22. [22] §5.5.06.A Table
  23. [23] §5.5.07.A Table
  24. [24] z
  25. [25] z
  26. [26] §5.5.06.A (derived from 5000 sf/unit detached SF)
  27. [27] z
  28. [28] §5.5.06.A
  29. [29] §5.5.06.A / E
  30. [30] §5.5.06.A / F
  31. [31] §5.5.06.A Table
  32. [32] §5.5.07.A Table
  33. [33] z
  34. [34] z
  35. [35] §5.5.06.A (derived from 3000 sf/unit detached SF)
  36. [36] z
  37. [37] §5.5.06.A
  38. [38] §5.5.06.A / E
  39. [39] §5.5.06.A / F
  40. [40] §5.5.06.A Table
  41. [41] §5.5.07.A Table
  42. [42] z
  43. [43] z
  44. [44] §5.5.06.A (derived from 7000 sf/unit detached SF)
  45. [45] z
  46. [46] §5.5.06.A
  47. [47] §5.5.06.A / E
  48. [48] §5.5.06.A / F
  49. [49] §5.5.06.A Table
  50. [50] §5.5.07.A Table
  51. [51] z
  52. [52] z
  53. [53] §5.5.06.A (derived from 3500 sf/unit detached SF)
  54. [54] z
  55. [55] §5.6.07.A
  56. [56] §5.6.07.A
  57. [57] §5.6.07.A
  58. [58] §5.6.07.A
  59. [59] §5.6.08.A + §5.8.02.C
  60. [60] z
  61. [61] z
  62. [62] z
  63. [63] §5.6.07.A
  64. [64] §5.6.07.A
  65. [65] §5.6.07.A
  66. [66] §5.6.07.A
  67. [67] §5.6.08.A
  68. [68] z
  69. [69] z
  70. [70] z
  71. [71] §5.6.07.A
  72. [72] §5.6.07.A
  73. [73] §5.6.07.A
  74. [74] §5.6.07.A
  75. [75] §5.6.08.A
  76. [76] z
  77. [77] z
  78. [78] z
  79. [79] §5.6.07.A
  80. [80] §5.6.07.A
  81. [81] §5.6.07.A
  82. [82] §5.6.07.A
  83. [83] §5.6.08.A
  84. [84] z
  85. [85] z
  86. [86] z
  87. [87] §5.6.07.A
  88. [88] §5.6.07.A
  89. [89] §5.6.07.A
  90. [90] §5.6.07.A
  91. [91] §5.6.08.A
  92. [92] z
  93. [93] z
  94. [94] z
  95. [95] §5.6.07.A
  96. [96] §5.6.07.A
  97. [97] §5.6.07.A
  98. [98] §5.6.07.A
  99. [99] §5.6.08.A
  100. [100] z
  101. [101] z
  102. [102] z
  103. [103] §5.6.07.A
  104. [104] §5.6.07.A
  105. [105] §5.6.07.A
  106. [106] §5.6.07.A
  107. [107] §5.6.08.A
  108. [108] z
  109. [109] z
  110. [110] z
  111. [111] §5.6.07.A
  112. [112] §5.6.07.A
  113. [113] §5.6.07.A
  114. [114] §5.6.07.A
  115. [115] §5.6.08.A
  116. [116] z
  117. [117] z
  118. [118] z
  119. [119] §5.6.07.A
  120. [120] §5.6.07.A
  121. [121] §5.6.07.A
  122. [122] §5.6.07.A
  123. [123] §5.6.08.A
  124. [124] z
  125. [125] z
  126. [126] z
  127. [127] z
  128. [128] z
  129. [129] z
  130. [130] §5.7.02 / Table 5.7.02.C
  131. [131] z
  132. [132] z
  133. [133] z
  134. [134] z
  135. [135] z
  136. [136] z
  137. [137] z
  138. [138] §5.7.03 / Table 5.7.03.C
  139. [139] z
  140. [140] z
  141. [141] z
  142. [142] z
  143. [143] §5.7.04 / Table 5.7.04.C
  144. [144] §5.7.04 / Table 5.7.04.C
  145. [145] §5.7.04 / Table 5.7.04.C
  146. [146] §5.7.04 / Table 5.7.04.C
  147. [147] §5.7.04 / Table 5.7.04.D
  148. [148] z
  149. [149] z
  150. [150] z
  151. [151] z
  152. [152] z
  153. [153] z
  154. [154] §5.7.05
  155. [155] z
  156. [156] z
  157. [157] z
  158. [158] z
  159. [159] z
  160. [160] z
  161. [161] z
  162. [162] §5.7.06
  163. [163] z
  164. [164] z
  165. [165] z
  166. [166] z

Research status

Publication gates

primary url presentpassedcode_source is https://library.municode.com/mi/grand_rapids/codes/code_of_ordinances?nodeId=TITV--ZONING_PLANNING_CH61ZOOR — Municode is the City of Grand Rapids-designated authoritative repository (not an aggregator). The archival mirror at energyzoning.org provided the actual extraction surface for this v2 pass.
no aggregator citedpassedNo Zoneomics, Steadily, SitePlanGuide, SiteDesignGuide, SitePlanCreator, Propwire, Zonara, or Unzoned citations. All §-citations point to Chapter 61 sections (§5.5.06.A, §5.6.07.A, §5.7.04, §5.8.02-07, etc.), MCL §X, FEMA NFIP, or MI Const. Art. VII.
confidence tags full formpassedAll confirmed claims carry full-form §-citations (c§5.5.06.A through c§5.8.07 for districts and overlays; c MCL 125.3205, etc.). Fields without primary-source extraction in this pass are tagged 'not_captured' with explicit reason rather than bare [confirmed].
overlays have parameters trigger confidencepassedAll 6 overlays (OD-DH, OD-GR, OD-EBL, OD-FP, OD-WS, OD-SC) have a non-empty params object, a trigger string, and a confidence field tagged c with full-form §-citation. OD-EBL, OD-FP, OD-WS, OD-SC carry partial-confidence sub-fields with explicit reason for not_captured items.
preempt section city specificpassedstate_preemptions_applicable[] contains 5 entries: MI-MZEA-125-3205 IZ ban (city-specific: GR operates voluntary/incentive bonuses per §5.6.08.B / §5.5.06.I — confirmed compliant), MI-MZEA-125-3207 moratoria, MI-MZEA-125-3206 group homes (city-specific: §5.5.05 already lists AFC family home as Permitted in LDR/MDR — statute-compliant), MI-MZEA-125-3206 manufactured housing parity (city-specific: Table 5.5.05 lists manufactured housing community as Permitted in MDR), and MI-HB5585 statewide ADU (under_review pending 103rd Legislature; §5.9.03 currently regulates ADU as QR).

Data quality

58%completeness95 confirmed8 partial
Documented gaps
  • Max height base values in Table 5.6.08.A for commercial zones (TN-CC, TCC, TBA, TOD, MCN-C, MON-C, NOS) — extracted summary references the table but does not capture per-zone story/foot caps.
  • OD-DH bonus-height tiers per subarea — §5.8.02 references subareas with distinct base + bonus heights but specific values not extracted.
  • OD-EBL East Beltline corridor design standards — §5.8.04 dimensional table not captured.
  • OD-FP floodplain freeboard increment — Grand Rapids-specific inches above BFE not captured.
  • Sign overlays (OD-WS) dimensional/sign-type rules.
  • Parking minimums citywide (Article 5 parking section reference) — not extracted.
  • Lot coverage / impervious cover — Chapter 61 substitutes Min Green Space and Min Tree Canopy; relationship between these and traditional coverage was noted but specific Tree Canopy % per district not all populated in this v2 pass for SD districts.
  • SD-AP, SD-OS, SD-IC, SD-PRD dimensional tables — Tables 5.7.02.C / 5.7.03.C / 5.7.05 / 5.7.06 referenced but specific values not extracted.
  • Building Elements tables 5.5.07.A / 5.6.08.A — transparency %, façade variation, materials standards captured at framework level but not all per-district specifics.
  • Post-2022-06-29 amendments — would need access to current Municode compilation to confirm 2023-2026 ordinances haven't shifted any of the captured values; freshness:volatile tag reflects this exposure.

Known issues

freshness:volatileblocker:municodedata:gaps-present

Other cities in this state

Nearest-alphabetical profiles. Click through to compare zoning patterns side-by-side.