Pomona — Zoning

Last reviewed: July 2, 2026

Overview

Pomona’s Zoning & Development Code establishes a mapped system of 32 zoning districts (grouped into RND, NED, UND, ACD, TOD, WD, SCD, PLD) that implement the General Plan place types and control permitted uses, building form, and site standards. The Code ties each district to a specific Form Module, Frontage Module, and Use Module so that dimensional rules (setbacks, height, coverage) come from the applied modules rather than a single “R‑1/R‑2/C‑1” legacy scheme (§ 200; § 330.B) . The official Zoning Code Maps are digital GIS layers maintained by Development Services and are the legal zoning map (§ 110.C) .

Links to related Pomona reference pages appear where those topics are first mentioned in the text: development-standards, parking, design-review, overlay-districts, ADUs, and the California Building Standards Code.

Part-by-part note: this page summarizes what the Pomona Zoning & Development Code says about zoning districts, the map, and how to read district rules. For raw regulatory text consult the Code and the adopted Zoning Code Maps (Verify with the jurisdiction).

District-by-district breakdown

Below each district is summarized in plain English. Where a district’s numeric dimensional standards are controlled by an applied Form Module (typical), I cite the Code bracket that shows the applied modules and point to the part where the module standards live so you can find exact setbacks, heights, lot-area, lot-coverage, and frontage rules.

General authority establishing the districts: § 200 (Zoning Districts Established) . For how to read the bracketed modules, see the district summaries and the referenced module sections (Form = Part 3, Frontage = Part 4, Use = Part 5) (§ 200; § 330.B; § 440) .

Note on format: every district below is labeled bold and shows the district intent, typical permitted uses (by Use Module), where to find the dimensional standards (Form Module), and a short “where it applies” note.

Residential Neighborhood Districts (RND)

The RND set is intended for lower-intensity, walkable residential areas (up to 2.5 stories). See § 200.B for intent and district list .

• RND1 — Purpose: lowest‑intensity residential neighborhood; Typical uses: single‑unit homes, ADUs where allowed by Use Module; Standards: see applied Form Module listed in the district bracket (see § 200 and the district’s bracketed Form Module) (§ 200.B; see applied Form Module) . Verify with parcel map.
• RND2 — Purpose: small‑scale residential; Typical uses: single‑family, duplexes, small multifamily; Standards: see district bracket/Form Module (§ 200.B) .
• RND3 — Purpose: moderate-density neighborhood housing; Typical uses: townhouses, triplexes, fourplexes; Standards: see Form Module (§ 200.B) .
• RND4 — Purpose: medium house-scale neighborhoods; Typical uses: small multifamily up to 2.5 stories; Standards: see Form Module; Example module cross-reference in summary charts (§ 200.B; § 330) .
• RND5 — Purpose: medium residential with more flexible ground story uses; Typical uses: mixed small commercial + housing where allowed by Use Module; Standards: see Form Module (§ 200.B) .

Neighborhood Edge Districts (NED)

NED districts transition between residential neighborhoods and more active or commercial zones. See § 200.C for intent and list .

• NED1 – NED5 — Purpose: up to 3 stories, mix of townhouses and small‑scale multifamily with limited commercial at ground floor; Typical uses: residential and limited nonresidential per the Use Module; Standards: bracket indicates applied Form Module (for example NED1 shows LM2 form, G1 frontage, CX1 use) — consult the bracket (§ 200.C; Secs. 330.B, 440.A, 520.C) .

Urban Neighborhood Districts (UND)

Higher-density neighborhood contexts with more intensive frontage and form standards. See § 200.D (§ 200.D) .

• UND1 – UND3 — Purpose: mid-rise neighborhood centers supporting mixed housing types; Typical uses: multifamily; Standards: see the district bracket and Part 3/Part 4 Form & Frontage Modules (§ 200.D) .

Activity Center Districts (ACD)

Centers of commerce and activity—higher intensity, pedestrian focus. See § 200.E (§ 200.E) .

• ACD1 – ACD3 — Purpose: commercial/mixed‑use centers; Typical uses: retail, offices, housing above; Standards: see applied Form and Use modules in the district bracket (§ 200.E) .

Transit Oriented Districts (TOD)

Transit-served nodes with the most intense mix of uses and development forms. See § 200.F (§ 200.F) .

• TOD1 – TOD6 — Purpose: highest-intensity transit corridors and station areas; Typical uses: mixed‑use, multifamily, limited workplace uses; Standards: see bracketed Form/Frontage/Use Modules (§ 200.F) .

Workplace Districts (WD)

Industrial/office/workplace districts with controlled street presence and screening requirements. See § 200.G (§ 200.G) .

• WD1 – WD5 — Purpose: low‑ to mid‑rise industrial and small manufacturing; Typical uses: light industrial, offices, limited retail per Use Module; Standards: see district bracket and Part 3 Form modules (examples: WD4 = LM4/G2/I1) (§ 200.G; see Sec. 440.B) .

Special Campus Districts (SCD)

Large civic, institutional, campus settings (Civic Center, Cal Poly Pomona, Fairplex). See § 200.H (§ 200.H) .

• SCD1 – SCD3 — Purpose: institutional/civic campuses; Typical uses: public buildings, institutional uses, campus support; Standards: SCD districts allow taller buildings (examples: SCD1 up to 8 stories) and refer to specific Form and Use Modules in the district brackets (§ 200.H; Sec. 350.B) .

Parkland Districts (PLD)

Public parks and open space regulation. See § 200.I (§ 200.I) .

• PLD1 – PLD2 — Purpose: parks and open space uses only; Typical uses: public parks, recreation; Standards: see Form/Frontage modules tied to park uses (§ 200.I; Sec. 460.D) .

Quick reference table — most decision‑relevant district facts

For exact numeric values (buildable height in feet/stories, minimum lot area, front/side/rear setbacks, lot coverage, FAR when used) consult the district’s bracketed Form Module in Part 3 (Form), frontage in Part 4, and uses in Part 5 — the Code is modular by design (§ 200; § 330; § 350; § 520) .

How the Zoning Map works (basic rules)

• The legal map is the set of official Zoning Code Maps (GIS layers) maintained by Development Services; the maps are adopted as part of the Code (§ 110.C) .
• Boundaries default to street, alley, or lot lines unless otherwise shown on the Zoning Map; vacated streets/alley rules and annexation treatment are set out in the Code (§ 1-13; § 1-14) .
• Minor zone boundary adjustments (to correct mapping errors or conform to new parcel lines) may be approved administratively by the Development Services Director, limited to 50 feet, and the Zoning Map updated accordingly (§ 2 Zone Boundary Adjustments) .

Table: Where to find the numeric standards you will most need

Checklist — what an applicant must satisfy (high level)

• Confirm the parcel’s official zoning on the Development Services GIS Zoning Code Map (the GIS map is the legal map) (§ 110.C) .
• Identify the district bracket (Form / Frontage / Use Modules) that applies to the parcel (§ 200; district bracket) .
• Use the referenced Form Module (Part 3) to determine setbacks, height, lot coverage, and building form (§ 330; § 350) .
• Use the referenced Use Module (Part 5 / § 520) to confirm permitted uses, accessory uses, and whether your use requires a Conditional Use/Development Plan (§ 520.C) .
• Show compliance with Part 6 Site rules (parking, access, landscaping, trash) — see parking and landscaping-and-screening (§ 600; § 610) .
• Determine whether your project triggers Development Plan, Administrative Review, or public hearings (Part 11) — consult design-review (§ 1100.A; § 1170) .
• Check overlays or Specific Plans that may modify the underlying district rules (see overlay-districts; § 700.D) .
• If construction is involved, comply with building-code permits separately — the Zoning Code is not the Building Code (see California Building Standards Code). Verify all code intersections with the jurisdiction.

Risks & Ambiguities

Plain‑English summary

Pomona replaced traditional numeric residential/commercial zone labels with place‑type‑based districts (e.g., RND, NED, TOD) where each parcel’s bracket tells you which Form, Frontage, and Use rules apply; to know what you can build you must look up the parcel on the official Zoning Code Maps, read its district bracket in § 200, then read the linked Form (Part 3), Frontage (Part 4), and Use (Part 5) modules for numeric setbacks, heights, and permitted uses (§ 200; § 110.C; Part 3/4/5) .

Information Gaps

• Exact parcel-to-parcel map lookups and GIS map URLs: Not found in retrieved materials (the Code says maps are maintained by Development Services but the file does not include the city’s public GIS link) (§ 110.C) .
• Full text of every Form/Frontage/Use Module numeric table for each district in one consolidated place: the Code references many modules (Parts 3–5) but a parcel‑specific numeric summary requires checking the district bracket and the cited Form Module (Part 3) for that district — see those sections for the numbers (Verify with the jurisdiction) (§ 330; § 350; § 390) .
• Local ADU-specific numeric adjustments in each district: Not found in retrieved materials; consult the local ADU page and Part 5 Use Modules and state ADU law for mandatory allowances (ADUs; California ADU law).

Source References

• Pomona Zoning & Development Code — Part 2 (Summary of Zoning Districts), § 200 (Zoning Districts Established) .
• Pomona Zoning & Development Code — Part 1, § 110.C (Zoning Code Maps: intent, maintenance, legal map) .
• Pomona Zoning & Development Code — Part 3 (Form Modules) and representative module sections (e.g., Sec. 330, Sec. 350, Sec. 390) for building form and numeric standards .
• Pomona Zoning & Development Code — Part 4 (Frontage Modules, examples Sec. 440, Sec. 460) .
• Pomona Zoning & Development Code — Part 6 (Site: parking, access, landscaping — Sec. 600, Sec. 610) .
• Pomona Zoning & Development Code — Part 7 (Alternate Typologies) and § 700.C–700.D (relationship to districts, Specific Plans, overlays) .
• Pomona Zoning & Development Code — Part 11 (Administration; Development Plan rules and review authority § 1100.A, § 1110) .

If you want, I can:

• Pull the exact numeric standards (height in feet/stories; minimum lot area; front/side/rear setbacks; max coverage) for one specific district (for example RND3) and the module that applies to a particular parcel — provide the parcel APN or address and I’ll extract the correct Form/Frontage/Use module and the numeric values from the applicable module. Verify with the jurisdiction.

Retrieved passages

• Pomona Zoning Code High relevance show source text
• Pomona Zoning Code High relevance show source text
• Pomona Zoning Code High relevance show source text
• Pomona Zoning Code High relevance show source text
• Pomona Zoning Code (Section when) High relevance show source text
• Pomona Zoning Code (Section when) Medium relevance show source text
• Pomona Zoning Code Medium relevance show source text
• Pomona Zoning Code Medium relevance show source text

Cited sections

• Pomona Zoning & Development Code — Part 2 (Summary of Zoning Districts), § 200 (Zoning Districts Established) . (§ 200)
• Pomona Zoning & Development Code — Part 1, § 110.C (Zoning Code Maps: intent, maintenance, legal map) . (§ 110.C)
• Pomona Zoning & Development Code — Part 3 (Form Modules) and representative module sections (e.g., Sec. 330, Sec. 350, Sec. 390) for building form and numeric standards .
• Pomona Zoning & Development Code — Part 4 (Frontage Modules, examples Sec. 440, Sec. 460) .
• Pomona Zoning & Development Code — Part 6 (Site: parking, access, landscaping — Sec. 600, Sec. 610) .
• Pomona Zoning & Development Code — Part 7 (Alternate Typologies) and § 700.C–700.D (relationship to districts, Specific Plans, overlays) . (§ 700.C)
• Pomona Zoning & Development Code — Part 11 (Administration; Development Plan rules and review authority § 1100.A, § 1110) . (§ 1100.A)
• Pull the exact numeric standards (height in feet/stories; minimum lot area; front/side/rear setbacks; max coverage) for one specific district (for example **RND3**) and the module that applies to a particular parcel — provide the parcel APN or address and I’ll extract the correct Form/Frontage/Use module and the numeric values from the applicable module. Verify with the jurisdiction.
• Pomona_ZoningCode.md

• Official Pomona code library