Base district · form based code · City of Mesa AZ
Transect 6: Main Street (Form-Based Code). The FBC REPLACES the base zoning regulations on a parcel that has opted in. Mini-Storage and all Warehousing and Storage uses are absent from the FBC composite use table and are therefore prohibited
Every verdict below is the base-district answer read out of the ordinance of record, with the section that says so. A use with no row is shown as unknown rather than folded into “no”.
Not allowed
Mini-Storage does not appear anywhere in the Form-Based Code composite use table. The FBC replaces base zoning on an opted-in parcel, so opting in extinguishes any storage entitlement
Permitted by right
Permitted only on upper floor(s) or behind an allowed ground floor use (note 2). The FBC sets no dwelling-units-per-acre cap; intensity is governed by building type, build-to lines and height
Not allowed
Absent from the FBC composite use table
Not allowed
DERIVED. The allowed building types in these transects (Main Street Mixed-Use, Mid-Rise, High-Rise, Apartment House, Courtyard Building) do not include Duplex or Townhouse, so middle-housing product is not buildable even though Multi-Unit Residence is a permitted use
Permitted by right
Retail, eating and drinking, services and residential all appear in the column. Vertical mixing is the design assumption: several residential and office rows are marked 'upper floors or behind an allowed ground floor use'
Not allowed
No storage use of any kind appears in the FBC composite use table
A blank cell means this dataset carries no number for that standard — read it as “go and look”, not as zero.
| Standard | Value | Field |
|---|---|---|
| Floor area ratio (FAR) | — | far |
| Maximum height | 135 ft | max_height_ft |
| Maximum site coverage | — | site_coverage |
| Minimum lot area | — | min_lot_area_sf |
| Minimum lot width | 50 ft | min_lot_width_ft |
| Minimum lot area per dwelling unit | — | min_lot_area_per_du_sf |
| Maximum density | — | max_du_per_acre_derived |
| Front setback | 0 ft | setback_front_ft |
| Street-side setback | 0 ft | setback_side_street_ft |
| Interior side setback | 0 ft | setback_side_interior_ft |
| Rear setback | 0 ft | setback_rear_ft |
Dimensional standards from MZO 11-58-3 (Table 11-58-3.A) / 11-58-11.
Standards notes. Height stated as 4 stories min; 135 ft max. The FBC sets no lot area, lot coverage or dwelling-units-per-acre standard; intensity is controlled by building type (Chapter 59), build-to lines and frontage. Front and side street figures for T4NF and beyond are BUILD-TO LINE maxima, not minimum setbacks. Rear setback in T4NF, T4MS, T5N and T5MSF is 5 ft adjacent to T5N/T4N/T3N and 0 ft adjacent to all other transects and to an alley. Applies only in the Downtown and Pioneer/Temple regulating-plan area and to parcels that have executed a notarised Form-Based Code Opt-In (11-56-2(C))
No district in this dataset publishes a floor area ratio: intensity in this code is governed by lot coverage, height and — for residential — density or minimum lot area per dwelling unit. See the metro page for the provenance note on that.
Run the envelope this district allows, free, in about a minute — lot area, FAR or height, and the residual land value it supports.
The quick screen is free and needs no account. The sample study is the seven-page deliverable the Feasibility Desk produces.
base district only; overlay geometry not checked — an Airfield or Form-Based Code designation can flip answers
This is a base-district reading of the ordinance text, transcribed from the source below. It is not a Zoning Verification Letter, not a determination by the jurisdiction, not legal advice, and not a substitute for asking the planning department about a specific parcel. Overlays, recorded plan conditions, rezoning stipulations and parcel geometry are not checked here, and any one of them can change the answer on this page.
Verify locally before you spend money. Call the planning counter, pull the parcel's zoning-map designation and its case history, and confirm the section cited above still reads the way it reads here.
Full provenance, the source hashes and the known limitations for City of Mesa AZ →