Overview
Tucson operates two parallel Euclidean codes — legacy Land Use Code (LUC, Chapter 23) for pre-UDC parcels and Unified Development Code (UDC, Chapter 23B) for post-2013 rezonings. Base-district naming encodes density tier rather than lot-size-in-thousands: Rural (RH, SR), Suburban (SH, RX-1, RX-2), Urban Residence (R-1, R-2, R-3), Mobile Home (MH-1, MH-2), Office (O-1/2/3), Commercial (C-1/2/3), Office/Commercial/Residential (OCR-1/2), Industrial (P-I, I-1, I-2). Floodplain (Ch. 25) and WASH watercourse/habitat (Ch. 29) regulations sit outside the UDC in separate Tucson Code chapters. Middle Housing Zone (Aug 2025) is the HB 2721 compliance mechanism. | naming_convention_raw=density-tier-encoded ; sub_flags_raw=[dual-code-regime, arizona-housing-bills-2024, state-preemption-active, afb-adjacent-dmafb, part77-active-ktus]
- Two parallel zoning codes operate simultaneously in Tucson — the legacy Land Use Code (LUC, Chapter 23) continues to govern parcels zoned under that system, while the newer Unified Development Code (UDC, Chapter 23B) governs parcels rezoned since UDC adoption (2013). Both remain active. A parcel-level zoning analysis must first determine which code applies before any dimensional lookup. — [Tucson Code Chapter 23 (LUC) and Chapter 23B (UDC); Tucson Planning & Development Services practice]
- Height-based perimeter yards — interior setbacks in Tucson are not fixed in feet but are expressed as the GREATER of a minimum value or a multiple of building height (e.g., 6' or 2/3(H) residential-adjacent; 10' or 3/4(H) nonresidential-adjacent). Taller buildings generate larger required yards. This is a structural difference from typical fixed-dimension setbacks and materially affects massing studies in R-2/R-3/OCR-1/OCR-2. — [c§UDC Art. 6.3.4]
- Two-track street setbacks — street perimeter yards operate on an Established Area versus Developing Area (MS&R) track. Established Area front yards = greater of 20 ft or 1.5(H). Developing Area front yards = determined by MS&R map centerline offset. This creates dynamic setback requirements depending on how an area is classified. — [c§UDC Art. 6.3.4; Art. 5.4 (MSR)]
+ 7 more in Quirks & notes
Districts
| Code | Name | Category | Min lot | Height | Coverage | FAR | Du/ac | Parking | Setbacks F/S/R |
|---|---|---|---|---|---|---|---|---|---|
| RH | Rural Homestead | residential_sf | 180,000 sf[4] | 30 ft[5] | 0.2[6] | 0.5[7] | 0.24[8] | — | 25[1] / 25[2] / 10[3] |
| SR | Suburban Ranch | residential_sf | 144,000 sf[12] | 30 ft[13] | 0.15[14] | 0.5[15] | 0.3[16] | — | 25[9] / 25[10] / 10[11] |
| SH | Suburban Homestead | residential_sf | 36,000 sf[20] | 30 ft[21] | 0.15[22] | 0.5[23] | 1.21[24] | — | 25[17] / 25[18] / 10[19] |
| RX-1 | Suburban Residence 1 | residential_sf | 36,000 sf[28] | 30 ft[29] | 0.15[30] | 0.5[31] | 1.21[32] | — | 25[25] / 25[26] / 10[27] |
| RX-2 | Suburban Residence 2 | residential_sf | 16,000 sf[36] | 25 ft[37] | 0.15[38] | 0.5[39] | 2.72[40] | — | 25[33] / 25[34] / 10[35] |
| R-1 | Urban Residence (Low) | residential_sf | 7,000 sf[44] | 70 ft[45] | 0.25[46] | 0.5[47] | 8[48] | — | 25[41] / 6[42] / 10[43] |
| R-2 | Urban Residence (Medium) | residential_sf | 5,000 sf[52] | 70 ft[53] | 0.25[54] | 0.5[55] | 15[56] | — | 25[49] / 6[50] / 10[51] |
| R-3 | Urban Residence (High) | residential_mf | 5,000 sf[60] | 70 ft[61] | 0.25[62] | 0.5[63] | —[64] | — | 25[57] / 6[58] / 10[59] |
| MH-1 | Mobile Home (Low) | residential_sf | 5,000 sf[68] | 70 ft[69] | 0.25[70] | 0.5[71] | 8[72] | — | 25[65] / 6[66] / 10[67] |
| MH-2 | Mobile Home (Medium) | residential_sf | 5,000 sf[76] | 75 ft[77] | 0.25[78] | 0.5[79] | 15[80] | — | 25[73] / 6[74] / 10[75] |
| O-1 | Office (Low) | office | 5,000 sf[84] | 70 ft[85] | 0.5[86] | 0.5[87] | 8[88] | — | 25[81] / 10[82] / 10[83] |
| O-2 | Office (Medium) | office | 5,000 sf[92] | 70 ft[93] | 0.5[94] | 0.5[95] | 8[96] | — | 25[89] / 10[90] / 10[91] |
| O-3 | Office (High) | office | 5,000 sf[100] | 75 ft[101] | 0.5[102] | 0.5[103] | 22[104] | — | 25[97] / 10[98] / 10[99] |
| C-1 | Commercial (Neighborhood) | commercial | 5,000 sf[108] | 75 ft[109] | 0.5[110] | 0.5[111] | 36[112] | — | 25[105] / 10[106] / 10[107] |
| C-2 | Commercial (General) | commercial | 5,000 sf[116] | 70 ft[117] | 0.5[118] | 0.5[119] | 44[120] | — | 25[113] / 10[114] / 10[115] |
| C-3 | Commercial (High Intensity) | commercial | 5,000 sf[124] | 80 ft[125] | 0.5[126] | 0.5[127] | 87[128] | — | 25[121] / 10[122] / 10[123] |
| OCR-1 | Office/Commercial/Residential 1 | mixed_use | 5,000 sf[132] | 140 ft[133] | 0.8[134] | 0.5[135] | —[136] | — | 25[129] / 25[130] / 10[131] |
| OCR-2 | Office/Commercial/Residential 2 | mixed_use | 5,000 sf[140] | 300 ft[141] | 0.8[142] | 0.5[143] | —[144] | — | 25[137] / 25[138] / 10[139] |
| NC | Neighborhood Commercial | commercial | 5,000 sf[148] | 16 ft[149] | 0.5[150] | 0.5[151] | — | — | 25[145] / 10[146] / 10[147] |
| P-I | Park Industrial | industrial | 5,000 sf[155] | 50 ft[156] | 0.5[157] | 0.5[158] | — | — | 25[152] / 25[153] / 10[154] |
| I-1 | Light Industrial | industrial | 5,000 sf[162] | 75 ft[163] | 0.5[164] | 0.5[165] | — | — | 25[159] / 25[160] / 10[161] |
| I-2 | Heavy Industrial | industrial | 5,000 sf[169] | 140 ft[170] | 0.5[171] | 0.5[172] | — | — | 25[166] / 25[167] / 10[168] |
Confidence: confirmed partial under review not found
Overlays
Designated hillside areas shown on the official Hillside Development Zone Map — generally parcels with slopes greater than 15%. Applies across residential, commercial, mixed-use, and office base zones where mapped.
Parcels adjacent to designated scenic routes — primarily mountain-approach corridors and arterials with ridgeline views into the Tucson, Catalina, Rincon, and Tortolita mountains.
Parcels fronting on corridors designated on the Tucson Major Streets and Routes (MS&R) map — primarily arterials and collectors slated for future ROW expansion.
Designated gateway corridor locations — major entry routes into Tucson (I-10, I-19, Speedway, Grant, 22nd St, Broadway, etc.). Applied to residential, commercial, office, and mixed-use parcels along those corridors.
Parcels within the Airport Influence Area for Tucson International Airport (KTUS) AND Davis-Monthan Air Force Base (DMAFB), as defined by FAA-approved airport layout plans and military AICUZ noise-contour maps. Combined AEZ geography covers substantial portions of south and southeast Tucson.
Open lands and habitat resource areas designated on the Environmental Resource Zone Map — typically washes, riparian corridors, and significant wildlife habitat (including Sonoran Desert saguaro forest).
Specific neighborhoods and individual properties designated by Mayor and Council after nomination and hearing process. Current HPZs include Barrio Historico, Barrio Viejo, Armory Park, El Presidio, West University, Fort Lowell, and others.
Specific area around the former Drachman School site (downtown-adjacent neighborhood near 16th St and Convent).
Specific established neighborhoods designated by petition and Council action. Protects existing character from incompatible infill.
Sites along designated community corridors near transit facilities, located in the City's Central Core (primarily along Broadway, Grant, 22nd, Speedway — streets with bus rapid transit or planned streetcar extensions).
Defined downtown area (roughly bounded by the Santa Cruz River, 6th St, Stone Ave, and 22nd St) with designated sub-districts per §5.12.9.
Floating overlay — established by petition and Council action for specific areas needing customized urban-form standards.
Defined geography within Tucson where middle-housing use is permitted by-right in SF and some commercial zones; ordinance specifies mapped eligible parcels per HB 2721 mandate for cities ≥70,000 population.
FEMA-mapped Special Flood Hazard Areas (SFHA) under Chapter 25; Pima County / City-mapped washes, riparian habitat, and buffer zones under Chapter 29 (WASH). Tucson's braided arroyo network means substantial portions of the city intersect WASH.
State preemptions
Adopted building codes
No statewide code; city-level
Click a code label to open its state-by-state adoption atlas.
Quirks & notes
- Two parallel zoning codes operate simultaneously in Tucson — the legacy Land Use Code (LUC, Chapter 23) continues to govern parcels zoned under that system, while the newer Unified Development Code (UDC, Chapter 23B) governs parcels rezoned since UDC adoption (2013). Both remain active. A parcel-level zoning analysis must first determine which code applies before any dimensional lookup. — [Tucson Code Chapter 23 (LUC) and Chapter 23B (UDC); Tucson Planning & Development Services practice]
- Height-based perimeter yards — interior setbacks in Tucson are not fixed in feet but are expressed as the GREATER of a minimum value or a multiple of building height (e.g., 6' or 2/3(H) residential-adjacent; 10' or 3/4(H) nonresidential-adjacent). Taller buildings generate larger required yards. This is a structural difference from typical fixed-dimension setbacks and materially affects massing studies in R-2/R-3/OCR-1/OCR-2. — [c§UDC Art. 6.3.4]
- Two-track street setbacks — street perimeter yards operate on an Established Area versus Developing Area (MS&R) track. Established Area front yards = greater of 20 ft or 1.5(H). Developing Area front yards = determined by MS&R map centerline offset. This creates dynamic setback requirements depending on how an area is classified. — [c§UDC Art. 6.3.4; Art. 5.4 (MSR)]
- Floodplain (Ch. 25) and WASH (Ch. 29 — Watercourse, Amenities, Stormwater, Habitat) regulations are codified SEPARATELY from the zoning UDC. Unlike most cities, Tucson's flood and riparian rules sit in standalone Tucson Code chapters, not as an overlay in the zoning code. The UDC references them but they must be consulted independently and can materially constrain buildable area in wash-intersecting parcels. — [Tucson Code Ch. 25 (Floodplain) and Ch. 29 (WASH); UDC §9-1 cross-reference]
- Dual-airport AEZ coverage — both Tucson International Airport (KTUS) and Davis-Monthan Air Force Base (DMAFB) generate Airport Environs Zones under UDC §5.6, meaning parts of Tucson's urban fabric sit under TWO concurrent airport-related overlays. Combined coverage spans south and southeast Tucson including residential, commercial, and some industrial areas. DMAFB additionally triggers the federal MAAMF/AICUZ overlay with use and intensity restrictions that federally preempt state HB 2720/2721 mandates on affected parcels. — [c§UDC Art. 5.6 (AEZ); federal-overlays/MAAMF.json; federal-overlays/AICUZ.json; federal-overlays/PART77.json]
- Middle Housing Zone (Aug 2025) — Tucson's HB 2721 compliance ordinance modifies permitted uses in R-1 through MH-2 and several commercial zones within a defined mapped geography. Dimensional standards for middle-housing use in those zones differ from SF-use dimensional standards in the same zone. The ordinance explicitly preserves DMAFB / KTUS AEZ compatibility — middle housing NOT permitted where it would violate Part 77 or >65 dB DNL carve-outs. — [Tucson Code — Middle Housing Zone ordinance, adopted August 2025]
- OCR-2 permits up to 300 ft in height — one of the highest district maxes in the Mountain West — but this is heavily constrained in practice by AEZ / Part 77 surfaces on south- and downtown-adjacent parcels near KTUS. OCR-2 parcels in the downtown IID sub-district may not be able to actually reach 300 ft due to federal airspace ceilings. — [c§UDC Art. 6, Table 6.3-3.C; Art. 5.6 AEZ]
- Prop 207 (2006) statewide creates a chilling effect on downzoning and new restrictive overlays. Tucson has managed this primarily by layering permissive overlays (IID, CCT, MHZ) rather than downzoning existing districts. No major Prop 207 claims documented in current research pass. — [A.R.S. §§12-1131 to 12-1138 (Prop 207, 2006); Tucson zoning amendment history]
- Neighborhood Commercial (NC) has a 16 ft height cap — among the most restrictive in the UDC. Intentional neighborhood-scale limit designed to preserve walkable small-format commercial character in established neighborhoods. — [c§UDC Art. 6, Table 6.3-3.B]
- Tucson's AMARG 'Boneyard' at DMAFB is the world's largest military aircraft storage and maintenance facility. Its presence reinforces DMAFB's strategic long-term status — AICUZ contours are unlikely to contract and federal preemption is durable. — [DoD AMARG facility documentation; DMAFB AICUZ study]
Formulas
Definitions
- height
- Grade to highest point of structure; measured per UDC §6.4.5
- lot_coverage
- Building footprint / lot area
- far
- Gross floor area / lot area
- du_ac
- Dwelling units per gross acre
- setback_front
- Front (street) property line to nearest building face; two tracks — Established Area = greater of fixed minimum or 1.5(H); Developing Area = determined by Major Streets & Routes (MS&R) map centerline offset
- setback_side
- Side property line to nearest building face; interior setback = greater of fixed minimum or 2/3(H) [residential adjacency] or 3/4(H) [nonresidential adjacency]
- setback_rear
- Rear property line to nearest building face; greater of fixed minimum or height multiple
- parking
- Use-specific ratios per UDC §7.4; not modeled as per-unit in base district table
- height_based_yard_rule
- Tucson interior setbacks are expressed as the GREATER of a fixed minimum OR a multiple of building height (2/3H residential-adjacent, 3/4H nonresidential-adjacent). This means taller buildings generate larger required yards, unusual compared to typical fixed-dimension setbacks.
Capacity calculations
- max_footprint_sf
lot_area_sf * lot_coverage- max_gfa_sf
lot_area_sf * far- buildable_width_ft_residential
lot_width_ft - 2 * max(side_min_ft, (2/3) * proposed_height_ft)- buildable_depth_ft_residential
lot_depth_ft - max(front_min_ft, 1.5 * proposed_height_ft) - max(rear_min_ft, (2/3) * proposed_height_ft)- max_stories_approx
max_height_ft / 10
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.
| District | Category | Height | FAR | Coverage | Setbacks | Parking | Density | Min lot | Overlays |
|---|
Sources & references
- [1] c§UDC Art. 6.3.4 — perimeter yards; street yard rule applies (greater of 20 ft or 1.5(H) in Established Area)
- [2] c§UDC Art. 6.3.4
- [3] c§UDC Art. 6.3.4
- [4] c§UDC Art. 6, Table 6.3-2.A (per PDSD Dimensional Standards Summary July 2020)
- [5] c§UDC Art. 6, Table 6.3-2.A
- [6] c§UDC Art. 6, Table 6.3-2.A
- [7] c§UDC Art. 6
- [8] c§UDC Art. 6
- [9] c§UDC Art. 6.3.4
- [10] c§UDC Art. 6.3.4
- [11] c§UDC Art. 6.3.4
- [12] c§UDC Art. 6, Table 6.3-2.A
- [13] c§UDC Art. 6, Table 6.3-2.A
- [14] c§UDC Art. 6, Table 6.3-2.A
- [15] c§UDC Art. 6
- [16] c§UDC Art. 6
- [17] c§UDC Art. 6.3.4
- [18] c§UDC Art. 6.3.4
- [19] c§UDC Art. 6.3.4
- [20] c§UDC Art. 6, Table 6.3-2.A
- [21] c§UDC Art. 6, Table 6.3-2.A
- [22] c§UDC Art. 6, Table 6.3-2.A
- [23] c§UDC Art. 6
- [24] c§UDC Art. 6
- [25] c§UDC Art. 6.3.4
- [26] c§UDC Art. 6.3.4
- [27] c§UDC Art. 6.3.4
- [28] c§UDC Art. 6, Table 6.3-2.A
- [29] c§UDC Art. 6, Table 6.3-2.A
- [30] c§UDC Art. 6, Table 6.3-2.A
- [31] c§UDC Art. 6
- [32] c§UDC Art. 6
- [33] c§UDC Art. 6.3.4
- [34] c§UDC Art. 6.3.4
- [35] c§UDC Art. 6.3.4
- [36] c§UDC Art. 6, Table 6.3-2.A
- [37] c§UDC Art. 6, Table 6.3-2.A
- [38] c§UDC Art. 6, Table 6.3-2.A
- [39] c§UDC Art. 6
- [40] c§UDC Art. 6
- [41] c§UDC Art. 6.3.4
- [42] c§UDC Art. 6.3.4
- [43] c§UDC Art. 6.3.4
- [44] c§UDC Art. 6, Table 6.3-2.B (SF use)
- [45] c§UDC Art. 6, Table 6.3-2.B
- [46] c§UDC Art. 6, Table 6.3-2.B
- [47] c§UDC Art. 6
- [48] c§UDC Art. 6, Table 6.3-2.B (SF use cap)
- [49] c§UDC Art. 6.3.4
- [50] c§UDC Art. 6.3.4
- [51] c§UDC Art. 6.3.4
- [52] c§UDC Art. 6, Table 6.3-2.B (SF); 7,000 sf for mobile-home use
- [53] c§UDC Art. 6, Table 6.3-2.B (SF)
- [54] c§UDC Art. 6, Table 6.3-2.B
- [55] c§UDC Art. 6
- [56] c§UDC Art. 6, Table 6.3-2.B (MF / MH-park); 8 du/ac SF use
- [57] c§UDC Art. 6.3.4
- [58] c§UDC Art. 6.3.4
- [59] c§UDC Art. 6.3.4
- [60] c§UDC Art. 6, Table 6.3-2.B
- [61] c§UDC Art. 6, Table 6.3-2.B (SF/civic); 40 ft for nonres
- [62] c§UDC Art. 6, Table 6.3-2.B
- [63] c§UDC Art. 6
- [64] c§UDC Art. 6, Table 6.3-2.B
- [65] c§UDC Art. 6.3.4
- [66] c§UDC Art. 6.3.4
- [67] c§UDC Art. 6.3.4
- [68] c§UDC Art. 6, Table 6.3-2.B
- [69] c§UDC Art. 6, Table 6.3-2.B
- [70] c§UDC Art. 6, Table 6.3-2.B
- [71] c§UDC Art. 6
- [72] c§UDC Art. 6, Table 6.3-2.B
- [73] c§UDC Art. 6.3.4
- [74] c§UDC Art. 6.3.4
- [75] c§UDC Art. 6.3.4
- [76] c§UDC Art. 6, Table 6.3-2.B
- [77] c§UDC Art. 6, Table 6.3-2.B (MF)
- [78] c§UDC Art. 6, Table 6.3-2.B
- [79] c§UDC Art. 6
- [80] c§UDC Art. 6, Table 6.3-2.B (MF/MH park)
- [81] c§UDC Art. 6.3.4
- [82] c§UDC Art. 6.3.4
- [83] c§UDC Art. 6.3.4
- [84] c§UDC Art. 6, Table 6.3-3.A
- [85] c§UDC Art. 6, Table 6.3-3.A
- [86] c§UDC Art. 6
- [87] c§UDC Art. 6
- [88] c§UDC Art. 6
- [89] c§UDC Art. 6.3.4
- [90] c§UDC Art. 6.3.4
- [91] c§UDC Art. 6.3.4
- [92] c§UDC Art. 6, Table 6.3-3.A
- [93] c§UDC Art. 6, Table 6.3-3.A
- [94] c§UDC Art. 6
- [95] c§UDC Art. 6
- [96] c§UDC Art. 6
- [97] c§UDC Art. 6.3.4
- [98] c§UDC Art. 6.3.4
- [99] c§UDC Art. 6.3.4
- [100] c§UDC Art. 6, Table 6.3-3.A
- [101] c§UDC Art. 6, Table 6.3-3.A
- [102] c§UDC Art. 6
- [103] c§UDC Art. 6
- [104] c§UDC Art. 6
- [105] c§UDC Art. 6.3.4
- [106] c§UDC Art. 6.3.4
- [107] c§UDC Art. 6.3.4
- [108] c§UDC Art. 6, Table 6.3-3.B
- [109] c§UDC Art. 6, Table 6.3-3.B
- [110] c§UDC Art. 6
- [111] c§UDC Art. 6
- [112] c§UDC Art. 6
- [113] c§UDC Art. 6.3.4
- [114] c§UDC Art. 6.3.4
- [115] c§UDC Art. 6.3.4
- [116] c§UDC Art. 6, Table 6.3-3.B
- [117] c§UDC Art. 6, Table 6.3-3.B
- [118] c§UDC Art. 6
- [119] c§UDC Art. 6
- [120] c§UDC Art. 6
- [121] c§UDC Art. 6.3.4
- [122] c§UDC Art. 6.3.4
- [123] c§UDC Art. 6.3.4
- [124] c§UDC Art. 6, Table 6.3-3.B
- [125] c§UDC Art. 6, Table 6.3-3.B
- [126] c§UDC Art. 6
- [127] c§UDC Art. 6
- [128] c§UDC Art. 6
- [129] c§UDC Art. 6.3.4
- [130] c§UDC Art. 6.3.4
- [131] c§UDC Art. 6.3.4
- [132] c§UDC Art. 6, Table 6.3-3.C
- [133] c§UDC Art. 6, Table 6.3-3.C
- [134] c§UDC Art. 6, Table 6.3-3.C
- [135] c§UDC Art. 6
- [136] c§UDC Art. 6
- [137] c§UDC Art. 6.3.4
- [138] c§UDC Art. 6.3.4
- [139] c§UDC Art. 6.3.4
- [140] c§UDC Art. 6, Table 6.3-3.C
- [141] c§UDC Art. 6, Table 6.3-3.C
- [142] c§UDC Art. 6, Table 6.3-3.C
- [143] c§UDC Art. 6
- [144] c§UDC Art. 6
- [145] c§UDC Art. 6.3.4
- [146] c§UDC Art. 6.3.4
- [147] c§UDC Art. 6.3.4
- [148] c§UDC Art. 6, Table 6.3-3.B
- [149] c§UDC Art. 6, Table 6.3-3.B
- [150] c§UDC Art. 6
- [151] c§UDC Art. 6
- [152] c§UDC Art. 6.3.4
- [153] c§UDC Art. 6.3.4
- [154] c§UDC Art. 6.3.4
- [155] c§UDC Art. 6, Table 6.3-4
- [156] c§UDC Art. 6, Table 6.3-4
- [157] c§UDC Art. 6
- [158] c§UDC Art. 6
- [159] c§UDC Art. 6.3.4
- [160] c§UDC Art. 6.3.4
- [161] c§UDC Art. 6.3.4
- [162] c§UDC Art. 6, Table 6.3-4
- [163] c§UDC Art. 6, Table 6.3-4
- [164] c§UDC Art. 6
- [165] c§UDC Art. 6
- [166] c§UDC Art. 6.3.4
- [167] c§UDC Art. 6.3.4
- [168] c§UDC Art. 6.3.4
- [169] c§UDC Art. 6, Table 6.3-4
- [170] c§UDC Art. 6, Table 6.3-4
- [171] c§UDC Art. 6
- [172] c§UDC Art. 6
Research status
Publication gates
| primary url present | passed | source.primary_url = https://codelibrary.amlegal.com/codes/tucson/latest/tucson_az_udc/ present, https, resolves to Tucson UDC Chapter 23B on amlegal platform. |
|---|---|---|
| no aggregator cited | passed | No zoneomics / steadily / siteplanguide / siteplancreator references anywhere in record. All citations point to UDC Chapter 23B (c§UDC Art. X.Y), Tucson Code Chapters 25/29, AZ session laws (HB 2720/2721/2297/2110, Prop 207), federal overlays (MAAMF/AICUZ/Part 77), or the Tucson PDSD Dimensional Standards Summary July 2020. |
| confidence tags full form | passed | All confirmed/partial claims carry explicit {status, citation, reason|search_performed|note} structure with c§UDC Art. X.Y section citations where applicable. Bare [confirmed] tags eliminated. Every overlay has status + citation. |
| overlays have parameters trigger confidence | passed | All 14 overlays (HDZ, SCZ, MSR, GCZ, AEZ, ERZ, HPZ_HL, DSO, NPZ, CCT, IID, UOD, MHZ, FP_WASH) have non-empty parameters[] arrays (5-7 entries each), populated geographic_trigger, status ∈ {confirmed, partial}, and citation. Primary Gate 4 failure mode from v1 resolved — v1 had loose params dicts with some missing trigger/status; v2 normalizes all 14. |
| preempt section city specific | passed | state_preemptions_applicable[] contains 7 city-specific entries (HB 2720, HB 2721, HB 2297, HB 2110, Prop 207, federal DMAFB AICUZ/MAAMF, federal KTUS Part 77) each with qualifying_condition_checked (carrying population arithmetic ~545k against the 30k/70k/75k thresholds with 2020 Decennial + 2023 PEP vintages), effect, effective_date, local_status, and citation. Record does NOT link-stub to arizona.md. Federal DMAFB + KTUS overlays promoted to explicit federal_state_conflict entries with federal_overlay_refs populated — resolves the FM-P concern about mis-tagging federal overlays as state preemption. |
Known issues
Verification
| last_verified_at | 2026-04-19T08:10:00Z |
|---|---|
| verifier_specialist | verification-pass |
| verifier_version | 1.0 |
| verification_result | passed_with_partials |
| atomic_claims_checked | 71 |
| atomic_claims_confirmed | 34 |
| atomic_claims_partial | 32 |
| atomic_claims_not_found | 5 |
| failed_claims | |
| notes | Format-transformation pass: v1 data (PDSD Dimensional Standards Summary July 2020 + UDC Article 5 TOC extraction) carried forward with normalized {status, citation} structure. High-confidence claims: base-district min-lot-sf and max-height-ft values (from confirmed summary PDF); AEZ structure (dual-airport KTUS + DMAFB); MHZ Aug 2025 adoption. Partial claims: overlay numerical parameters (amlegal 403 prevented full Article 5 text retrieval); full parking ratio tables (deferred to UDC §7.4 use-based lookup). Not-found: parking ratios across all districts (search_performed: UDC §7.4); specific GCZ and DSO parameters (search_performed: UDC §5.5 and §5.9 via amlegal). |
Other cities in this state
Nearest-alphabetical profiles. Click through to compare zoning patterns side-by-side.