Self-storage and multifamily zoning in City of Mesa AZ — all 45 districts

Known limitations of this transcription

Published in full, because a dataset that hides its own caveats is worth less than one that doesn't have any.

1. Self-storage is allowed in 7 of 45 districts — LC, GC, MX, PEP, LI, GI, DB-2 — and by right in none of them. Every one is a Council Use Permit: a public City Council vote after a Planning & Zoning Board recommendation (§11-70-6). That is a materially harder gate than unincorporated Maricopa County, where all five storage districts run through a staff-level Plan of Development. It is the single biggest schedule and political risk in a Mesa storage deal and it belongs in the study, not in a footnote.
2. Mini-Storage is PROHIBITED in Heavy Industrial. Table 11-7-2 reads CUP / CUP / CUP / — across PEP / LI / GI / HI, while Indoor Warehousing and Storage is permitted by right in all four including HI. A warehouse is fine in HI; a self-storage facility is not. Any dataset that assumes "heavier zoning = more permissive" gets this backwards.
3. Chapter 31 contains no standards section for Mini-Storage. Thirty-seven use-specific standards sections — car washes, drive-thrus, pawn shops, data centres, BESS, middle housing — and nothing for Mini-Storage. There is no objective checklist to design against; the §11-70-6(D) CUP findings are the entire test, so conditions are invented at the hearing. Combined with §11-70-2 (a CUP may require the existing site to be brought into current-code conformance) that is real, unquantified cost and timeline risk.
4. far is blank for all 45 districts by design, not by omission. Across everything retrieved, "floor area ratio" appears five times and never in a development standards table — only as a Chapter 87 definition, in the §11-11-2(C)(2)(d) Planned Community land use budget, in §11-11-8, in §11-22-5 (PAD) and in Chapter 36 on nonconformities. Intensity in every base district is lot coverage + building coverage + height + (residential) density. Same finding as Maricopa County, reached independently. (Article 5, and the Article 7 chapters other than 69/70/81, were not retrieved, so the count is over the extracted text, not the printed title.)
5. max_du_per_acre_derived is CODE-STATED in Mesa, not derived — unlike the county file, where it is computed. Mesa publishes maximum density directly (RM-2/3/4/5 at 15/20/30/43 du per net acre; GC and MX at 25). Where a minimum lot area per dwelling unit is also published it agrees: RM-4 is 43,560 ÷ 1,452 = 30.0 exactly.
6. PEP allows storage but cannot physically hold a conventional one. Mini-Storage is CUP in a campus office park, but Table 11-30-7 forbids all outdoor storage in PEP, the minimum site is 2.5 acres (2.5× the other employment districts), and building separation minimums apply that do not apply in LI/GI/HI. A drive-up layout will not fit; a single enclosed multi-storey building might.
7. MX is a paper storage district. CUP (7) — fully enclosed, no outdoor storage or display — under a 30 ft height cap, in a district carrying a minimum residential density of 15 du/acre. The table says yes; the economics say no.
8. Prohibitions are largely inferred from absence. Where a use classification does not appear in a district's table, this dataset writes prohibited on the strength of the preamble sentence "Use classifications not listed are prohibited." That is exactly what the ordinance says, but it is an inference from a general rule, not a cell that was read. Rows where the cell was an explicit — carry that symbol in code_symbol; rows inferred from absence leave it blank.
9. The downtown P (16) footnote is almost certainly a drafting error and was not resolved. Table 11-8-2 gives Multiple Residence P (16) in DR-1/2/3 and DB-1, P/CUP (16) in DB-2, P (1, 16) in DC — but note 16 reads "Permitted if an existing non-conforming residential use is located on the lot", which makes no sense against districts whose own standards table publishes a full minimum-lot-area ladder and densities of 12 and 40 du/acre. Recorded as permitted at medium confidence, DB-2 at low. Confirm with Mesa Planning before underwriting any downtown multifamily unit count.
10. CUP/P and P/CUP are undefined in the ordinance. Nothing in any preamble legend defines the slash. The reading here — Development Plan Review inside the density cap and the 60% commercial-GFA test, Council Use Permit outside either (§11-31-31(D)–(E)) — is inference, recorded as conditional at medium confidence.
11. Adaptive Reuse in the employment districts does not obviously work. Table 11-7-2 makes Multiple Residence P (3) in PEP/LI/GI/HI where note 3 is "with approval of an Adaptive Reuse Permit", but §11-81-2 applies Chapter 81 to "an existing commercial, office, or mixed-use parcel" — which an employment-zoned parcel is not, on its face. Either Chapter 87's definitions are broader than they look or the two chapters are out of sync. medium confidence. Verify before relying on it.
12. RSL-4.5 and EO are both missing from the district roster in §11-3-1(A), yet RSL-4.5 has a full column of development standards in Table 11-5-3.A.2 and EO has its own Chapter 14. Both are included here — RSL-4.5 at high confidence, EO at medium. A naive scrape of §11-3-1 alone yields a 44-district roster and silently drops one.
13. Front setbacks are not single numbers. In the commercial, employment, RM, DR and PS tables they vary by street classification in the Mesa Transportation Plan, a document outside Title 11 that was not retrieved. setback_front_ft records the arterial/collector case; the full ladder is in setback_notes. On a local street the real number is often 20 ft, not 15.
14. No lot area or lot coverage standards are published for DB-1, DB-2, DC, PS or LR, and Chapter 15 (LR) has no development standards table at all. Those cells are blank because the code is silent, not because extraction failed. Likewise DB/DC residential height: Table 11-8-5 carries heights only in its non-residential half, and max_height_ft records that figure.
15. mixed is partly derived. Mesa genuinely has mixed-use districts (MX, DB, DC, the transects), so most mixed rows rest on real code — but the RS/RSL/RM rows come from §11-31-9 micro-commercial SUPs, PEP/LI/GI from the Live-Work Unit SUP, and T3N/T4N/T5N from a historic-structure office SUP. All are medium and flagged "DERIVED" in the notes. Middle Housing in the transects is likewise a building-type inference (Chapter 59 Duplex / Townhouse / Mansion Apartment / Bungalow Court), not a use-table read, and Chapter 59's per-type footprint and unit-count rules — which are what actually cap a transect project — were not extracted.
16. Staleness risk is supplement cadence plus annexation. Supplement 22 is codified through an ordinance adopted 2026-03-09 but was posted online 2026-08-03 — a five-month lag. Ordinances adopted after 2026-03-09 are not in this text. Municode's NOW / OrdBank feature exposes enacted-but-uncodified legislation and was not queried; that is the obvious next hardening step.