Zoning › Arizona › Maricopa County › Glendale

Glendale, AZ Zoning

Euclidean-zoning. 17 districts · 8 overlays · 8 applicable state preemptions.

Overview

Code type
euclidean
Naming convention
mixed

Euclidean base zones (A-1 agricultural, SR/R-1 single-family, R-2/R-3/R-4 multifamily, C-1/C-2/C-3 commercial, M-1/M-2 industrial) layered with overlay districts (Art. 2, §35.2.1000 et seq.). R-1-# district codes encode minimum lot size in 1,000s sf (R1-6 = 6,000 sf; SR-30 = 30,000 sf; RR-45 = 45,000 sf). PAD is the dominant mechanism for post-2000 mixed-use and Westgate-area development. The Military Airport and Ancillary Military Facility (MAAMF) overlay for Luke AFB is the single most restrictive constraint in the city. | naming_convention_raw=lot-size-encoded-sf ; sub_flags_raw=[pad-dominant, arizona-housing-bills-2024, state-preemption-active, military-airport-overlay-dominant] ; narrative_ref=narratives/glendale-az/b4c688c1-447f-47cd-9809-2e39adca5726.json

Worth knowing
  • Luke AFB MAAMF overlay prohibits all residential uses (SFD, MF, ADU) within high-noise / accident-potential zones unless Luke AFB issues a Military Compatibility Permit (MCP). This is the single largest zoning constraint in Glendale and preempts state ADU (HB 2720) and middle-housing (HB 2721) mandates via their federal-airport-noise carve-outs. Southern and southwestern Glendale parcels may appear available for residential zoning but are practically constrained by MCP requirement. — [c§35, Art. 2 MAAMF; ARS §28-8481; Luke AFB AICUZ Study]
  • Single-family district naming encodes minimum lot size in thousands of sf (R1-6 = 6,000 sf; R1-10 = 10,000 sf; SR-30 = 30,000 sf; RR-45 = 45,000 sf). Transparent convention shared with Phoenix-metro peers (Scottsdale, Gilbert, Chandler variants). Developers can determine lot-size constraint from district name without consulting code tables. — [c§35, Art. 2]
  • R1-6 is a frozen 'legacy hold' district. UDC limits new R1-6 rezoning to special circumstances with documented findings — functionally a non-growth zone. Likely motivated by Prop 207 exposure to block downzoning of larger parcels, combined with policy preference to direct new small-lot SFD to R1-4 patio-home product. Developers should not plan new projects expecting R1-6 as an entitlement. — [c§35, Art. 2 R1-6 purpose statement; AZ Prop 207 (2006)]

+ 8 more in Quirks & notes

Districts

residential_sf 8residential_mf 3commercial 3industrial 2agricultural 1
CodeNameCategory Min lotHeight CoverageFAR Du/acParking Setbacks F/S/R
A-1Agriculturalagricultural43,560 sf[4]35 ft[5]0.5[6]—1[7]2[8]25[1] / 25[2] / 10[3]
RR-45Rural Residence (45,000 sf min)residential_sf45,000 sf[12]35 ft[13]0.5[14]—0.95[15]2[16]50[9] / 25[10] / 25[11]
SR-30Suburban Residence (30,000 sf min)residential_sf30,000 sf[20]30 ft[21]0.5[22]—1.4[23]2[24]40[17] / 15[18] / 25[19]
SR-17Suburban Residence (17,000 sf min)residential_sf17,000 sf[28]30 ft[29]0.5[30]—2.3[31]2[32]35[25] / 10[26] / 25[27]
R1-10Single Residence (10,000 sf min)residential_sf10,000 sf[36]30 ft[37]0.5[38]—3.9[39]2[40]25[33] / 7[34] / 20[35]
R1-8Single Residence (8,000 sf min)residential_sf8,000 sf[44]30 ft[45]0.5[46]—4.8[47]2[48]25[41] / 5[42] / 20[43]
R1-7Single Residence (7,000 sf min)residential_sf7,000 sf[52]30 ft[53]0.5[54]—5.6[55]2[56]25[49] / 5[50] / 20[51]
R1-6Single Residence (6,000 sf min) — Legacy Hold Districtresidential_sf6,000 sf[60]30 ft[61]0.5[62]—7.3[63]2[64]20[57] / 5[58] / 20[59]
R1-4Single Residence (4,000 sf min) — Patio Home Productresidential_sf4,000 sf[68]30 ft[69]0.6[70]—10.9[71]2[72]15[65] / 5[66] / 20[67]
R-2Multifamily Lowresidential_mf5,000 sf[76]35 ft[77]0.5[78]0.75[79]13[80]1.75[81]25[73] / 10[74] / 20[75]
R-3Multifamily Mediumresidential_mf5,000 sf[85]45 ft[86]0.55[87]1.25[88]17[89]1.75[90]25[82] / 10[83] / 25[84]
R-4Multifamily Highresidential_mf5,000 sf[94]45 ft[95]0.6[96]1.75[97]20[98]1.5[99]25[91] / 10[92] / 25[93]
C-1Neighborhood Commercialcommercial—35 ft[103]0.5[104]1[105]—3.5[106]15[100] / 10[101] / 10[102]
C-2Community Commercialcommercial—45 ft[110]0.6[111]1.75[112]—3.5[113]20[107] / 10[108] / 10[109]
C-3Regional Commercialcommercial—55 ft[117]0.7[118]2.25[119]—3.5[120]25[114] / 10[115] / 10[116]
M-1Light Industrialindustrial—45 ft[124]0.6[125]1[126]—2[127]25[121] / 10[122] / 15[123]
M-2Heavy Industrialindustrial—55 ft[131]0.6[132]1.25[133]——[134]25[128] / 10[129] / 15[130]

Confidence: confirmed partial under review not found

Overlays

MAAMF
Military Airport and Ancillary Military Facility Overlay (Luke Air Force Base)
SPEC
c§35, Art. 2, §35.2.1000 et seq.; ARS §28-8481 (AZ state statute authorizing military compatibility overlays)

Non-contiguous parcels within Luke AFB high-noise (DNL >=65 dB) and accident-potential zones (APZ-1 and APZ-2) as delineated on the adopted Luke AFB / Maricopa County compatibility map. Concentrated in southern and southwestern Glendale; shared with Peoria jurisdictionally. Arizona Superior Court (State v. Maricopa County) + Maricopa County compliance certification per ARS §28-8481(I) in 2010.

CLO
Centerline Overlay (Scenic Corridor / Arterial Setback)
SPEC
c§35, Art. 2, §35.2.1010

Properties along designated centerline-setback arterials where future roadway widening or scenic corridor preservation is planned. Applies citywide to identified major arterials (Glendale Ave, Bell Rd, 59th Ave, Loop 101 adjacent parcels, among others).

HPO
Historic Preservation Overlay (Old Towne Glendale)
SPEC
c§35, Art. 2 (Historic Preservation provisions); Glendale Historic Preservation Commission authority

Old Towne Historic District — approximately 10 square blocks in downtown Glendale centered on Glendale Avenue and 58th Drive. Also applies to individually designated historic properties citywide.

AIO
Airport Impact Overlay (Civilian Airport)
SPEC
c§35, Art. 2 Airport Impact provisions

FAA Part 77 imaginary surfaces and AICUZ noise contours near Glendale Municipal Airport (civilian general-aviation) and overlap zones with Phoenix-area regional airports. Distinct from MAAMF — AIO applies to civilian aviation, MAAMF to military.

FOFFH
Floodplain Overlay (FEMA 100-Year / 500-Year Flood Hazard)
SPEC
c§35, Art. 2 Floodplain Management provisions; Maricopa County Flood Control District coordination; FEMA Flood Insurance Study

FEMA Special Flood Hazard Areas (SFHAs) with 1% annual chance of inundation (Zone A/AE), plus 500-year zones (Zone X shaded). Limited mapped floodplain in Glendale — primary areas near Westgate district and southwest industrial zones near Luke AFB; Agua Fria and New River corridor on western edge.

PAD
Planned Area Development (Master Plan Overlay)
SPEC
c§35, Art. 2 PAD provisions

Applied throughout Glendale via City Council rezoning action. Most post-2000 mixed-use, commercial, and residential master-planned developments are PAD-governed — Westgate Entertainment District, Glendale 303, Evergreen Loop 101, Centerline on Glendale, Parkway 303 West, Sarival 303.

MHOD
Middle Housing Overlay (HB 2721 Compliance)
SPEC
c§35, Art. 2 supplementary provisions implementing AZ HB 2721 (2024); specific article reference pending direct UDC amendment retrieval

1-mile CBD buffer centered on Old Towne Glendale, extending to SF-zoned parcels within the radius. Applies to SR-17, R1-10, R1-8, R1-7, R1-6, R1-4 base zones within buffer. Exempts MAAMF-overlaid parcels (federal preemption).

AROD
Adaptive Reuse Overlay (HB 2110 / HB 2297 Compliance)
SPEC
c§35, Art. 2 supplementary provisions implementing AZ HB 2110 and HB 2297 (2024); specific article reference pending direct retrieval

Commercial (C-2, C-3) and multifamily (R-3, R-4) parcels undergoing adaptive reuse of nonconforming or underutilized structures to residential or mixed-use. Glendale pop >75,000 threshold for HB 2110/2297 applicability met.

State preemptions

AZ HB 2720 — ADU by-right (2024, effective 2025)applies
Qualifying condition
qualifying_condition=Statewide preemption applies to all AZ cities. Glendale has single-family residential zones (A-1, RR-45, SR-30, SR-17, R1-10, R1-8, R1-7, R1-6, R1-4) subject to the mandate. ; local_status=Glendale must comply. KEY EXCEPTION: HB 2720 statute includes explicit carve-out for FAA-licensed / public airport noise zones >=65 dB. The Luke AFB MAAMF overlay (DNL >=65 dB + APZ-1/APZ-2) qualifies under this carve-out, so ADUs remain prohibited inside MAAMF per federal military compatibility. Outside MAAMF, HB 2720 governs.
Effect
ADUs permitted by-right on all SF lots: up to 1 attached + 1 detached (3rd permitted on lots >=1 acre if 1 is restricted-affordable). Cities cannot impose owner-occupancy, minimum-size, additional-parking, design-matching, or HOA-based restrictions more restrictive than the state floor. Minimum 5 ft rear/side setback; maximum 1,000 sf or 75% of principal GFA (whichever less). Supersedes Glendale local baseline (1,200 sf detached; additional parking requirement).
AZ HB 2721 — Middle Housing by-right (2024)applies
Qualifying condition
qualifying_condition=Statewide mandate. Cities must permit middle housing (duplex/triplex/fourplex/townhouses) by-right in SF zones within 1 mile of CBD by Jan 2026. ; local_status=Glendale compliance status at Jan 2026 requires verification with Planning Division (623-930-2800). Old Towne CBD anchors the 1-mile buffer. MAAMF carve-out honored — middle housing prohibited inside Luke AFB MAAMF.
Effect
Duplex/triplex/fourplex/townhouses permitted by-right in all SF base zones (SR-17, R1-10, R1-8, R1-7, R1-6, R1-4) within 1-mile radius of Old Towne Glendale. Cannot require design standards that effectively prohibit middle housing. Compliance mechanism is MHOD overlay (above). MAAMF preempts middle housing in overlay.
AZ HB 2110 — Commercial-to-Residential Adaptive Reuse (2024)applies
Qualifying condition
qualifying_condition=Statewide mandate; ministerial approval of commercial-to-residential conversions without public hearing. Glendale pop ~252k meets typical threshold. ; local_status=Glendale AROD overlay (above) is the implementation pathway. Specific Chapter 35 article reference not directly retrieved — under_review for next freshness pass.
Effect
Existing commercial (C-2, C-3), office, or mixed-use buildings may convert to multifamily housing without public hearing. HB 2110 (2025) eliminated prior 10% citywide cap. Administrative review only; skip public hearing + community comment. Westgate-adjacent office stock, C-2 retail near Loop 101, and other underutilized Glendale commercial buildings eligible.
AZ HB 2297 — Residential Conversion Streamlining (2024)applies
Qualifying condition
qualifying_condition=Statewide companion to HB 2110; additional provisions for converting commercial/office to residential with streamlined approval. ; local_status=Glendale implementation folded into AROD overlay alongside HB 2110. Pathway for converting Westgate edge-office and C-2 retail to multifamily in response to post-pandemic commercial vacancy.
Effect
At least 10% of gross building area in eligible commercial zones must allow residential or adaptive reuse. Reduces approval timelines; consolidates with HB 2110. Combined effect creates multiple pathways for residential development on non-SF-zoned land in Glendale.
AZ HB 2447 — Ministerial Site-Plan Approval (2024)applies
Qualifying condition
qualifying_condition=Statewide; requires administrative (non-hearing) approval of site plans, development plans, plats based on objective standards. Companion law to HB 2721 middle-housing. ; local_status=Glendale compliance at Dec 2025 deadline requires verification. Operative for MHOD and AROD approval pathways.
Effect
Glendale must allow administrative approval based on objective standards for qualifying site plans — no discretionary review. Reduces entitlement cycle from multi-month public-hearing process to administrative review. Applies to MHOD middle housing and AROD adaptive reuse pathways.
AZ HB 2928 — Short-Term Rentals (2022, amended 2024)applies
Qualifying condition
qualifying_condition=Statewide preemption of STR regulation with carve-outs for airport noise zones >=65 dB (AICUZ DNL) and FAA-licensed airports. ; local_status=Glendale registers STRs per state framework; no blanket ban. MAAMF STR use subject to Luke AFB MCP requirements.
Effect
Glendale cannot ban STRs in residential zones; may impose health/safety licensing and tax registration only. Luke AFB MAAMF (>=65 dB DNL) carve-out means STRs in MAAMF remain subject to military compatibility constraints. HB 2928 2024 amendment clarifies airport-noise carve-outs.
AZ Prop 207 — Private Property Rights Protection Act (2006)applies
Qualifying condition
qualifying_condition=Statewide; requires compensation for regulations that reduce property value. ; local_status=Glendale follows statewide practice of avoiding downzoning. Prop 207 waiver required on rezoning applications. Framework effect on PAD-dominance pattern.
Effect
Chilling effect on downzoning and new restrictive overlays. In Glendale context: (a) contributed to PAD-dominance (negotiated master plans avoid Prop 207 triggers because property owner consents), (b) R1-6 'legacy hold' policy may reflect Prop 207 liability concerns about downzoning to R1-6, (c) any MAAMF boundary expansion onto previously residential-zoned land could trigger Prop 207 compensation claims. City practice: Prop 207 waiver disclosure at point of rezoning application.
Federal / USAF — Luke AFB MAAMF Military Airport Preemption (ARS §28-8481)applies
Qualifying condition
qualifying_condition=Federal preemption layer enforced via AZ state statute. Luke Air Force Base is an active military installation; F-35A primary training base. FAA Part 77 imaginary surfaces and USAF AICUZ noise contours preempt local residential density and height. ARS §28-8481 requires Maricopa County cities within the MAAMF boundary to adopt compatibility overlays. ; local_status=Glendale has adopted MAAMF overlay per ARS §28-8481(I). The overlay is the single most restrictive regulatory constraint in Glendale — any residential development project in southern/southwestern Glendale must confirm parcel position relative to MAAMF before assuming base-zone entitlements. Contact Luke AFB Civil Engineering (480-896-3000) for MCP pre-application.
Effect
MAAMF overlay prohibits all residential uses within boundary (SFD, multifamily, ADU) unless Luke AFB issues a Military Compatibility Permit (MCP). 100 ft max height on non-residential. AICUZ disclosure required. Supersedes base zone AND state housing mandates (HB 2720 ADU, HB 2721 middle housing, HB 2110/2297 adaptive reuse all yield to MAAMF via their federal-airport-noise carve-outs). This is the defining pattern for Phoenix-west-valley cities (Glendale, Peoria, Goodyear, Surprise) adjacent to Luke AFB. Any MAAMF boundary changes or MCP denials on previously residential-zoned land may trigger Prop 207 compensation claims.

Adopted building codes

No statewide code; city-level

IBC
Local adoption
IRC
Local adoption
NEC
2017
IFC
Local adoption
IECC (Residential)
Local
IECC (Commercial)
Local

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

Quirks & notes

  • Luke AFB MAAMF overlay prohibits all residential uses (SFD, MF, ADU) within high-noise / accident-potential zones unless Luke AFB issues a Military Compatibility Permit (MCP). This is the single largest zoning constraint in Glendale and preempts state ADU (HB 2720) and middle-housing (HB 2721) mandates via their federal-airport-noise carve-outs. Southern and southwestern Glendale parcels may appear available for residential zoning but are practically constrained by MCP requirement. — [c§35, Art. 2 MAAMF; ARS §28-8481; Luke AFB AICUZ Study]
  • Single-family district naming encodes minimum lot size in thousands of sf (R1-6 = 6,000 sf; R1-10 = 10,000 sf; SR-30 = 30,000 sf; RR-45 = 45,000 sf). Transparent convention shared with Phoenix-metro peers (Scottsdale, Gilbert, Chandler variants). Developers can determine lot-size constraint from district name without consulting code tables. — [c§35, Art. 2]
  • R1-6 is a frozen 'legacy hold' district. UDC limits new R1-6 rezoning to special circumstances with documented findings — functionally a non-growth zone. Likely motivated by Prop 207 exposure to block downzoning of larger parcels, combined with policy preference to direct new small-lot SFD to R1-4 patio-home product. Developers should not plan new projects expecting R1-6 as an entitlement. — [c§35, Art. 2 R1-6 purpose statement; AZ Prop 207 (2006)]
  • R1-4 is a patio-home product-type district only, NOT a standard small-lot SFD zone. Requires patio-home subdivision design: attached/detached SFD on 4,000 sf lots with rear-yard privacy guarantee, common/shared open space (HOA-maintained), functional rear yard (20-25 ft depth), and architectural coordination. Standard SFD subdivisions (detached homes, no common open space) in R1-4 will not be approved. — [c§35, Art. 2 R1-4 purpose statement]
  • Centerline Overlay imposes a 15 ft building-height cap on affected parcels — effectively one story only. Applies along designated scenic corridors and future roadway-widening arterials. Overrides base district height limits regardless of zoning (R-4, C-3, M-1). Extremely restrictive; rarely waived. Any site planning on Glendale arterials (Bell Rd, Glendale Ave, 59th Ave, Loop 101 adjacent) must confirm Centerline Overlay status. — [c§35, Art. 2, §35.2.1010]
  • R-2 multifamily step-down requirement: when abutting an R-1 zone, R-2 structures must be <=1 story within 50 ft of the R-1 boundary and <=2 stories within 100 ft. Protects R-1 neighborhoods from abrupt density transitions. Distinct Glendale UDC provision. — [c§35, Art. 2 R-2]
  • Westgate Sports & Entertainment District (State Farm Stadium — Arizona Cardinals; Desert Diamond Arena — formerly Coyotes) is Glendale's economic anchor. Zoned mixed C-3 + PAD with special-purpose entertainment design standards. High-density mixed-use, hotels, retail, and residential integrated. Likely overlay/PAD framework; not a discrete base-zone classification. — [c§35, Art. 2 PAD; Westgate PAD ordinance]
  • Old Towne Historic District (downtown, ~10 square blocks) has Historic Preservation Overlay with Certificate of Appropriateness (COA) required for exterior alterations, new construction, and demolition. Height approximately 18-25 ft in historic core. Tax-incentive / facade rehabilitation grant eligibility. Distinct from adaptive-reuse overlay pathway. — [c§35, Art. 2 HPO; Old Towne Design Guidelines]
  • PAD is the dominant mechanism for post-2000 entitlement of mixed-use, large commercial, and master-planned residential projects (Glendale 303, Westgate, Evergreen Loop 101, Centerline on Glendale, Parkway 303 West, Sarival 303). Most material Glendale entitlement work flows through PAD rather than base-zone-only analysis. Prop 207 reinforces this pattern — negotiated master plans avoid Prop 207 triggers. — [c§35, Art. 2 PAD; approved PAD ordinances]
  • 2024 UDC (adopted Dec 12 2023, effective Jan 12 2024) replaced prior Ordinance No. 243 framework. All pre-2024 research is superseded. UDC_12.12.23_FINAL.pdf hosted at cdnsm5-hosted.civiclive.com; consolidated code at library.municode.com/az/glendale. — [Glendale UDC adoption ordinance; UDC_12.12.23_FINAL.pdf]
  • Federal-state conflict pattern: HB 2720 (ADU by-right) and HB 2721 (middle housing by-right) statutes explicitly carve out FAA-licensed and military airport noise zones >=65 dB. The Luke AFB MAAMF overlay qualifies under this carve-out. Within MAAMF, federal military compatibility preempts state housing mandates; outside MAAMF, state mandates preempt local restrictions. Glendale is the canonical example of this pattern for Arizona; Chandler and other IWA-adjacent cities apply a variant (no AFB but FAA/AICUZ carve-outs via Art. XXXV exemption language). — [AZ HB 2720; AZ HB 2721; ARS §28-8481; c§35 Art. 2 MAAMF]

Formulas

Definitions

height
Finished grade to highest point of roof; excludes mechanical equipment, antennas, roof overhangs
lot_coverage
Building footprint / lot area
far
Total gross floor area / lot area
du_ac
Dwelling units / gross acre
setback_front
Front property line to nearest building face
setback_side
Side property line to nearest building face
setback_rear
Rear property line to nearest building face
parking
Off-street spaces per dwelling unit (residential) or per 1,000 sf GFA (commercial)

Capacity calculations

max_footprint_sf
lot_area_sf * lot_coverage
max_gfa_sf
lot_area_sf * far
max_units_sf_based
lot_area_sf / minimum_lot_per_unit
buildable_width_ft
lot_width_ft - setback_side_ft * 2
buildable_depth_ft
lot_depth_ft - setback_front_ft - setback_rear_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
——
◄
prev
►
next
Copy zoning profile
Loading…
District Category Height FAR Coverage Setbacks Parking Density Min lot Overlays

Sources & references

Primary source
Glendale City Code, Chapter 35 — Unified Development Code (UDC)
UDC adopted Dec. 12, 2023 (UDC_12.12.23_FINAL); effective Jan. 12, 2024; current through 2026-04-01 supplement · retrieved 2026-04-18
Citations
  1. [1] c§35, Art. 2
  2. [2] c§35, Art. 2
  3. [3] c§35, Art. 2
  4. [4] c§35, Art. 2 (1 acre typical)
  5. [5] c§35, Art. 2
  6. [6] c§35, Art. 2
  7. [7] c§35, Art. 2
  8. [8] c§35 Glendale parking standards
  9. [9] c§35, Art. 2
  10. [10] c§35, Art. 2
  11. [11] c§35, Art. 2
  12. [12] c§35, Art. 2 (district code encodes min lot sf)
  13. [13] c§35, Art. 2
  14. [14] c§35, Art. 2
  15. [15] c§35, Art. 2
  16. [16] c§35 Glendale parking standards
  17. [17] c§35, Art. 2
  18. [18] c§35, Art. 2
  19. [19] c§35, Art. 2
  20. [20] c§35, Art. 2
  21. [21] c§35, Art. 2
  22. [22] c§35, Art. 2
  23. [23] c§35, Art. 2
  24. [24] c§35 Glendale parking standards
  25. [25] c§35, Art. 2
  26. [26] c§35, Art. 2
  27. [27] c§35, Art. 2
  28. [28] c§35, Art. 2
  29. [29] c§35, Art. 2
  30. [30] c§35, Art. 2
  31. [31] c§35, Art. 2
  32. [32] c§35 Glendale parking standards
  33. [33] c§35, Art. 2
  34. [34] c§35, Art. 2
  35. [35] c§35, Art. 2
  36. [36] c§35, Art. 2 (district code encodes min lot sf)
  37. [37] c§35, Art. 2
  38. [38] c§35, Art. 2
  39. [39] c§35, Art. 2
  40. [40] c§35 Glendale parking standards
  41. [41] c§35, Art. 2
  42. [42] c§35, Art. 2
  43. [43] c§35, Art. 2
  44. [44] c§35, Art. 2
  45. [45] c§35, Art. 2
  46. [46] c§35, Art. 2
  47. [47] c§35, Art. 2
  48. [48] c§35 Glendale parking standards
  49. [49] c§35, Art. 2
  50. [50] c§35, Art. 2
  51. [51] c§35, Art. 2
  52. [52] c§35, Art. 2
  53. [53] c§35, Art. 2
  54. [54] c§35, Art. 2
  55. [55] c§35, Art. 2
  56. [56] c§35 Glendale parking standards
  57. [57] c§35, Art. 2
  58. [58] c§35, Art. 2
  59. [59] c§35, Art. 2
  60. [60] c§35, Art. 2
  61. [61] c§35, Art. 2
  62. [62] c§35, Art. 2
  63. [63] c§35, Art. 2
  64. [64] c§35 Glendale parking standards
  65. [65] c§35, Art. 2
  66. [66] c§35, Art. 2
  67. [67] c§35, Art. 2
  68. [68] c§35, Art. 2
  69. [69] c§35, Art. 2
  70. [70] c§35, Art. 2
  71. [71] c§35, Art. 2
  72. [72] c§35 Glendale parking standards
  73. [73] c§35, Art. 2
  74. [74] c§35, Art. 2
  75. [75] c§35, Art. 2
  76. [76] c§35, Art. 2
  77. [77] c§35, Art. 2
  78. [78] c§35, Art. 2
  79. [79] c§35, Art. 2
  80. [80] c§35, Art. 2
  81. [81] c§35 Glendale MF parking standards; guest parking additional
  82. [82] c§35, Art. 2
  83. [83] c§35, Art. 2
  84. [84] c§35, Art. 2
  85. [85] c§35, Art. 2
  86. [86] c§35, Art. 2
  87. [87] c§35, Art. 2
  88. [88] c§35, Art. 2
  89. [89] c§35, Art. 2
  90. [90] c§35 Glendale MF parking standards
  91. [91] c§35, Art. 2
  92. [92] c§35, Art. 2
  93. [93] c§35, Art. 2
  94. [94] c§35, Art. 2
  95. [95] c§35, Art. 2
  96. [96] c§35, Art. 2
  97. [97] c§35, Art. 2
  98. [98] c§35, Art. 2
  99. [99] c§35 Glendale MF parking standards
  100. [100] c§35, Art. 2
  101. [101] c§35, Art. 2
  102. [102] c§35, Art. 2
  103. [103] c§35, Art. 2
  104. [104] c§35, Art. 2
  105. [105] c§35, Art. 2
  106. [106] c§35 Glendale parking standards; varies by use
  107. [107] c§35, Art. 2
  108. [108] c§35, Art. 2
  109. [109] c§35, Art. 2
  110. [110] c§35, Art. 2
  111. [111] c§35, Art. 2
  112. [112] c§35, Art. 2
  113. [113] c§35 Glendale parking standards
  114. [114] c§35, Art. 2
  115. [115] c§35, Art. 2
  116. [116] c§35, Art. 2
  117. [117] c§35, Art. 2
  118. [118] c§35, Art. 2
  119. [119] c§35, Art. 2
  120. [120] c§35 Glendale parking standards
  121. [121] c§35, Art. 2
  122. [122] c§35, Art. 2
  123. [123] c§35, Art. 2
  124. [124] c§35, Art. 2
  125. [125] c§35, Art. 2
  126. [126] c§35, Art. 2
  127. [127] c§35 Glendale parking standards; typically 1/500 to 1/1000 sf
  128. [128] c§35, Art. 2
  129. [129] c§35, Art. 2
  130. [130] c§35, Art. 2
  131. [131] c§35, Art. 2
  132. [132] c§35, Art. 2
  133. [133] c§35, Art. 2
  134. [134] c§35 Glendale parking standards

Research status

Publication gates

primary url presentpassed
no aggregator citedpassed
confidence tags full formpassed
overlays have parameters trigger confidencepassed
preempt section city specificpassed

Known issues

freshness:volatile

Verification

last_verified_at2026-04-18T23:50:00Z
verifier_specialistverification-pass
verifier_version1.0
verification_resultpassed_with_partials
atomic_claims_checked74
atomic_claims_confirmed28
atomic_claims_partial42
atomic_claims_not_found4
failed_claims
notesv1 extraction re-verified. High-confidence claims (MAAMF residential prohibition + ARS §28-8481 authority; Centerline Overlay 15 ft cap per §35.2.1010; residential lot-size-encoded naming; R1-6 legacy hold; R1-4 patio home requirement; R-2 step-down rule; 2024 UDC effective Jan 2024; all 9 overlays with structured parameters/trigger/citation; all 8 state preemption entries with Glendale-specific qualifying_condition and local_status) preserved and restructured. MF/C/I dimensional table values remain partial pending direct UDC Art. 2 dimensional-table extraction. No failed claims — no removals.

Other cities in this state

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

BuckeyeChandlerGilbertGoodyearMesaPeoriaPhoenixScottsdale