Local zoning · Cathedral City

Cathedral City — Overlay Districts

Q: What does the LH (Limited Height) overlay do to my allowed building height?

The LH overlay caps building height at 16 ft by default; the Planning Commission may grant an increase up to 26 ft after findings. Additional privacy/view requirements apply for structures over 16 ft § 9.54.020–030, § 9.54.050–060 .

Q: Do overlays change setback, parking or ADU rules?

Overlays are specific; some (like LH ) act only on height while others trigger broader planning processes (like S ). You must reconcile overlay text with base-zone development standards (setbacks, parking, ADU allowances). See the code’s various zone chapters and cross‑references to parking (Chapter 9.58 ) and to ADU allowances in the residential zone chapters — verify specific cross-references for your parcel § 9.02.050 .

Overlay Districts under the Cathedral City local zoning and planning code, with the controlling citations.

Ask a question free See coverage

Last reviewed: July 1, 2026

Overview

Cathedral City’s development code (Title 9, Planning and Zoning) establishes a small set of overlay districts that sit on top of base zoning and add special rules or processes. The code identifies four overlays by letter: S (Specific Plan), H (Hillside Review), LH (Limited Height), and P/IH (Public/Institutional Housing). The overlays are listed in § 9.02.050 and then detailed in Chapters 9.50 through 9.56 of the Development Code. § 9.02.050 ; Title 9 overview § 9.02.010 .

Note: This page stays strictly to what Cathedral City’s zoning ordinance says about overlays (no building-code or housing-law interpretation). For citywide context start with the Cathedral City zoning & planning overview.

First-time resource links used in this page (internal city pages): Cathedral City zoning & planning overview, Cathedral City Zoning, Cathedral City Development Standards, Cathedral City Parking, Cathedral City Design Review, Cathedral City ADUs, and the California Building Standards Code.

How overlays work in Cathedral City (quick mechanics)

Overlays are applied in combination with a base zone; the overlay supplements or modifies the underlying zone rules rather than replacing them, unless the overlay explicitly conflicts (follow the overlay text) § 9.02.050 .
Where an overlay is mapped only over part of a parcel, the specific plan overlay treats the entire parcel as within the overlay (see S specific plan application rule) § 9.50.020 .
The official zoning map/land use exhibit determines which parcels carry an overlay; verify parcel-level overlay status with the official map on file at the city clerk § 9.02.030–040 .

District-by-district breakdown

Below are the four overlay districts created by Cathedral City’s Development Code. Each subsection states purpose, typical permitted uses (if the municipal code enumerates them), key dimensional or operational standards, and where/how each overlay is applied.

S — Specific Plan Overlay Zone (the S overlay)

Purpose: To permit flexible, large-scale, comprehensively planned urban communities that implement the general plan and allow negotiated standards and uses for major projects § 9.50.010 .
Permitted uses: Any principal or conditional use allowed in the underlying zone may be permitted subject to conditions negotiated and adopted as part of the specific plan; additional complimentary uses may be authorized so long as they are less than twenty percent of the S area § 9.50.030(A–B) .
Key standards/process triggers:
- A development agreement is required for S overlays and will spell phasing, on-site/off-site improvements, and unit/commercial schedules § 9.50.030(C) .
- Architectural and site plan approval is mandatory for developments in an S overlay; the code points applicants to the specific plan submittal rules in Chapter 9.60 § 9.50.040 .
Where it applies: Applied where the general plan land use exhibit and official zoning map show the S overlay; if only part of a parcel is mapped, the entire parcel is treated as within the overlay § 9.50.020 .
Practical guidance: Expect negotiated, project-specific standards (development agreement + specific plan + architectural/site-plan approvals). Because permitted uses are tied to the underlying zone but can be expanded within negotiated limits, early pre-application meetings and illustrations are essential to define what counts toward the 20% complimentary-use cap § 9.50.030 .

First use of “development standards / setbacks” is linked to Cathedral City Development Standards. First use of “design review” is linked to Cathedral City Design Review.

H — Hillside Review / Hillside Protection (the H overlay)

Purpose: To preserve and limit development on the Santa Rosa Mountains and Palm Hills Annexation sector; protect ridgelines, scenic vistas, natural habitat, limit erosion/flooding impacts and ensure public participation and review for hillside proposals § 9.52.010 (A–F) .
Permitted/conditional uses: The text establishes policy objectives, protections and procedural controls; specific permitted uses are not fully enumerated in the hillside chapter excerpts in the retrieved materials. Permitted uses by right or CUP status within H are not listed in the retrieved excerpts — Verify with the jurisdiction (see Information Gaps). Not found in retrieved materials .
Key standards/process triggers:
- Chapter describes required findings, public hearing procedures, conservancy/land‑holding trust review and elevated amendment requirements (including a four‑fifths city council vote for amendments) § 9.52.020, § 9.52.090 .
- The chapter requires special attention to preservation of natural character and limits on development intensity to protect visual and biological resources § 9.52.010–020 .
Where it applies: To lands in the Santa Rosa Mountains within the city limits, sphere of influence, or annexation areas identified in the chapter (Palm Hills Annexation Sector) § 9.52.010 .
Practical guidance: For parcels in the mapped hillside area expect discretionary review, more extensive environmental/landscape/erosion controls, public hearings and possible additional conditions—plan early for biological and scenic analyses, and expect a higher bar to amend the chapter itself § 9.52.090 .

LH — Limited Height Overlay Zone (the LH overlay)

Purpose: Protect views and privacy where existing buildings are predominantly one story; the overlay only addresses building height § 9.54.010 .
Permitted uses: Uses remain those of the underlying zone; LH only regulates height and related conditions § 9.54.010–020 .
Key dimensional/operational standards:
- Base maximum: buildings in LH areas shall not exceed 16 ft in height, notwithstanding the base zone height limits § 9.54.020 .
- Increases: the Planning Commission may permit increases up to 26 ft after findings; buildings over 16 ft must meet overlay requirements § 9.54.030 .
- Side‑yard rule: no portion of a building may exceed 16 ft when measured within 10 ft of an interior side lot line § 9.54.040 .
- Privacy & view protections: second‑story windows facing interior side property lines must be at least 60 inches above floor; landscaping (evergreens 25 ft at maturity) may be required; planning commission may deny or condition height increases based on privacy/view findings § 9.54.050–060 .
- Review pathway: increases are reviewed through the design review process and require graphic analysis of view/privacy impacts § 9.54.080–090 .
Where it applies: On parcels mapped with the LH overlay on the official zoning map; the overlay controls height even if the underlying zone would otherwise allow taller structures § 9.02.050; § 9.54.020 .
Practical guidance: If your lot lies in an LH area, treat 16 ft as the default height cap and plan for a possible Planning Commission hearing if you seek more than that. Prepare view/ privacy graphics per § 9.54.090 to support a height increase request .

First use of “parking” is linked to Cathedral City Parking; first use of “ADUs” is linked to Cathedral City ADUs.

P/IH — Public/Institutional Housing Overlay District (the P/IH overlay)

Purpose: To provide appropriate areas for institutional housing, including emergency homeless shelters and supportive/transitional housing, and to accommodate at least one year‑round emergency homeless shelter § 9.56.010 .
District established: Mapped over certain I-1 (Light Industrial) parcels shown as P/IH on the official zoning map § 9.56.020 .
Permitted uses: Any permitted use in the underlying I‑1 zone, plus emergency homeless shelters, supportive housing, transitional housing and low-barrier navigation centers § 9.56.030 .
Conditional/prohibited uses:
- Conditional uses: any conditional use listed in the I‑1 district § 9.56.040 .
- Prohibited uses: any use prohibited in the I‑1 district § 9.56.050 .
Special operational rules (emergency shelters):
- Aggregate‑beds rule: if the total number of beds in all P/IH districts exceeds the city’s count of homeless persons (per Riverside County) then additional beds require a conditional use permit § 9.56.060(A) .
- Hours: hours for certain shelter operations are constrained (example: six p.m. to eight a.m. is listed as hours of operation for emergency homeless shelters) § 9.56.060(B) .
Where it applies: Only to I‑1 parcels specifically designated P/IH on the official zoning map § 9.56.020 .
Practical guidance: If proposing an institutional housing use in a mapped P/IH area, use the I‑1 use table as a baseline plus the P/IH permitted uses; be aware of aggregate-bed limits and potential CUP triggers § 9.56.030–060 .

Decision‑relevant summary table

Overlay	Purpose (short)	Most decision-relevant standards / outcomes	Code reference
S (Specific Plan)	Flexibly implement major planned projects	Any underlying permitted/conditional uses allowed subject to negotiated conditions; development agreement required; site & architectural approval mandatory; specific plan rules in Chapter 9.60	§ 9.50.010–040
H (Hillside)	Protect hillsides, ridgelines, vistas, biological resources	Discretionary hillside review, conservancy/land‑holding trust and public hearing processes; strict amendment procedure	§ 9.52.010–020, § 9.52.090
LH (Limited Height)	Protect views/privacy by limiting heights	Height cap 16 ft (may increase to 26 ft by PC); side-yard measurement rule; privacy/window and landscaping requirements; design review/graphics required	§ 9.54.010–090
P/IH (Public/Institutional Housing)	Accommodate shelters/supportive/transitional housing	Allows emergency shelters, supportive/transitional housing, navigation centers on mapped I‑1 parcels; aggregate-bed CUP trigger; hour limits	§ 9.56.010–060

Checklist

Confirm whether the subject parcel is mapped with an overlay on the official zoning map (check with city clerk / planning counter) § 9.02.030–040 .
For S overlays: prepare a specific plan package and expect a required development agreement and architectural/site plan approval per § 9.50.030–040 .
For LH overlays: dimension your building envelope to the 16 ft cap, or prepare view/privacy graphics for a Planning Commission increase request to 26 ft § 9.54.020–030, § 9.54.090 .
For P/IH overlays: if proposing an emergency shelter, confirm aggregate‑beds status and the potential CUP trigger; comply with listed operational rules § 9.56.030–060 .
For H overlays: plan for discretionary review, potential biological/scenic studies, conservancy notifications, and heightened amendment requirements § 9.52.010–020; § 9.52.090 .
Identify underlying base zone standards for setbacks, coverage, parking and ADU rules and reconcile them with overlay rules (use Chapter references listed in the underlying zone chapters) (various zone §§; see § 9.02.050) .
Confirm whether design review, site plan, or conditional use permits are required and prepare materials accordingly (see Chapter 9.78 for design-review procedures) § 9.16.160; § 9.54.080 .
Verify development‑standard cross-references (e.g., parking Chapter 9.58, signage Chapter 9.62) and include those analyses in submittals (example: CTR district standards referencing parking chapter) .

Risks & Ambiguities

Issue	Why it matters	What to verify
Overlay boundary uncertainty	Overlay application (and therefore regulatory effect) is map-driven; errors cause wrong project requirements	Confirm overlay boundaries on the official zoning map at the city clerk/planning counter; read § 9.02.030–040
Hillside permitted uses not explicit in retrieved excerpts	The hillside chapter emphasizes process and protections but does not list a full permitted-use table in our materials	Verify permitted/conditional uses inside Chapter 9.52 and with planning staff; our files show policy and procedural text § 9.52.010–020
LH increase discretion (privacy/view findings)	Planning Commission makes subjective findings on privacy/view, which can cause uncertain outcomes and conditions	Prepare clear view/privacy graphics per § 9.54.090 and be ready to mitigate impacts; verify specific findings required under § 9.54.050–060
P/IH aggregate-bed calculations	Meeting or exceeding the city’s homeless-population count triggers a CUP requirement for additional beds	Confirm current Riverside County homeless-count number used by the city and current aggregate bed totals before planning capacity § 9.56.060(A)
Conflicts between overlay text and base-zone standards	Some overlays (e.g., LH) supplant base-zone height regulations; others are additive — conflicts affect which rule controls	Rely on overlay language; consult § 9.02.050 and the specific overlay chapter text to determine which provision governs

Plain‑English summary

Cathedral City’s code creates four overlays — S, H, LH, and P/IH — that modify or add rules to the base zone where they are mapped: S (big negotiated projects with a required specific plan and development agreement), H (stricter review for hillside lands), LH (low height: default cap 16 ft, limited increases by Planning Commission), and P/IH (allows shelters and related institutional housing on certain light‑industrial sites). Confirm overlay mapping on the official zoning map and follow the cited chapter rules for the specific procedural and dimensional requirements § 9.02.050; §§ 9.50–9.56 .

Source References

Title 9 — Planning and Zoning (Cathedral City Development Code) — general purpose and applicability § 9.02.010–040 .
Overlay district list and general rule — § 9.02.050 .
Specific Plan Overlay (S) — § 9.50.010–040 (application, permitted uses, development agreement, site/architectural approval; see Chapter 9.60 for submittal rules) .
Hillside Protection (H) — Chapter 9.52: purpose, findings, amendment procedures § 9.52.010–020; § 9.52.090 .
Limited Height Overlay (LH) — Chapter 9.54: purpose, 16 ft cap, increase to 26 ft, side-yard and privacy rules, design-review application § 9.54.010–090 .
Public/Institutional Housing Overlay (P/IH) — Chapter 9.56: district establishment, permitted uses (emergency shelter, supportive housing, transitional housing, navigation centers), conditional/prohibited uses, shelter rules § 9.56.010–060 .
Official zoning map and boundaries rules — § 9.02.030–040 .
Design review processing reference (used by overlays) — e.g., design-review requirement language in other chapters; see Chapter 9.78 reference in site/architectural approvals § 9.16.160; § 9.54.080 .
Examples of base-zone cross-references (parking, sign chapters) appear in zone chapters (e.g., CTR referencing Chapter 9.58 for parking) — see § 9.32.050(D) for cross reference examples .

If you need a parcel‑specific determination (overlay present on a specific lot, exact map sheet, or staff interpretation of a provision), verify with Cathedral City Planning — the official zoning map and city staff rulings are controlling (Verify with the jurisdiction).

Sources

Retrieved passages

Cathedral City Zoning Code (§ 9.54.030.) High relevance
Cathedral City Zoning Code (§ 2) High relevance
Cathedral City Zoning Code (Chapter 9.48.) Medium relevance
Cathedral City Zoning Code (§ 9.32.010.) Medium relevance
Cathedral City Zoning Code (§ 3) Medium relevance
Cathedral City Zoning Code (§ 3) Medium relevance
Cathedral City Zoning Code (§ 9.80.070.) Medium relevance
Cathedral City Zoning Code (§ 1) Medium relevance

Cited sections

Official Cathedral City code library

Frequently asked questions

What exactly is an overlay district in Cathedral City?

An overlay district is a mapped zoning “layer” that sits on top of the base zoning designation and adds or modifies rules for properties where the overlay is shown; Cathedral City lists overlays in § 9.02.050 and details them in Chapters 9.50–9.56 .

How do I find out whether my lot is in an overlay?

Check the official zoning map on file with the city clerk and confirm with planning staff; the code treats mapped overlays as controlling and provides rules for boundary determinations in § 9.02.030–040 .

What does the LH (Limited Height) overlay do to my allowed building height?

The LH overlay caps building height at 16 ft by default; the Planning Commission may grant an increase up to 26 ft after findings. Additional privacy/view requirements apply for structures over 16 ft § 9.54.020–030, § 9.54.050–060 .

If my property is in the S Specific Plan overlay, can I build uses not allowed in the base zone?

The S overlay lets the specific plan negotiate permitted uses: generally any underlying permitted or conditional use can be authorized subject to specific plan conditions; complimentary uses may be added so long as they make up less than 20% of the S area. A development agreement is required § 9.50.030(A–C) .

Are emergency homeless shelters automatically allowed in Cathedral City?

Emergency homeless shelters are listed as a permitted use within mapped P/IH overlay areas (on certain I‑1 parcels). However, if the aggregate number of beds in P/IH districts exceeds the city’s homeless-population count, additional beds require a conditional use permit § 9.56.030; § 9.56.060(A) .

Will the hillside overlay stop all development on a mountain parcel?

No — the H overlay does not categorically ban development; it imposes stronger protections, discretionary review, and procedural requirements (conservancy/land‑holding trust input, public hearings, special findings) to limit impacts to ridgelines, habitat and scenic vistas § 9.52.010–020; § 9.52.090 .

Do overlays change setback, parking or ADU rules?

Overlays are specific; some (like LH) act only on height while others trigger broader planning processes (like S). You must reconcile overlay text with base-zone development standards (setbacks, parking, ADU allowances). See the code’s various zone chapters and cross‑references to parking (Chapter 9.58) and to ADU allowances in the residential zone chapters — verify specific cross-references for your parcel § 9.02.050 .

If an overlay conflicts with the base-zone rules, which controls?

If an overlay explicitly modifies a subject (e.g., LH controls height), the overlay control governs for that subject; otherwise the underlying zone provisions remain in effect. Confirm the controlling provision in the overlay chapter and the base zone text § 9.02.050 .

What approvals should I expect if my project is in an S overlay?

Expect a specific plan submittal, architectural and site plan approval, and a development agreement. Chapter 9.60 contains more submittal specifics and Chapter 9.78 describes design-review processes referenced by overlay chapters § 9.50.040; § 9.50.030(C) .

Who decides on height increases in LH areas and what do they look for?

The Planning Commission reviews height increase requests (up to 26 ft) and will consider topography, adjacent building heights, privacy, and view impacts; the applicant must provide graphic evidence of view or privacy impacts per § 9.54.080–090 .

Ask about any Cathedral City property

Get a cited, plain-English answer on Cathedral City zoning, setbacks, FAR, ADUs and permits — for any address.

Start Free Trial