Yucca Valley — Land Use

Last reviewed: July 3, 2026

Overview

This page summarizes what the Town of Yucca Valley Development Code (the local zoning ordinance) says about land use: how uses are listed in the code, how to read the use tables, what uses are permitted vs. conditional, and the district-by-district rules that most affect decisions (setbacks, lot coverage, FAR, and permit triggers). The Development Code creates use tables for each zoning district and specific rules for overlays and special plans; read the cited code sections and confirm parcel‑specific details with the Town. See the town's zoning map and chapter headings in the development code for the official district assignment and map. § 9.06.030 governs permitted uses and permit types in the code .

Note: when the page mentions administrative topics like design review, parking, overlays, or ADUs it links to the related GoCodebook pages for quick navigation: the town’s Yucca Valley Zoning, Yucca Valley Development Standards, Yucca Valley Parking, Yucca Valley Design Review, Yucca Valley Overlay Districts, Yucca Valley ADUs, and the California Building Standards Code.

How Yucca Valley organizes land uses (quick rules)

• Land uses are listed in use tables that accompany each zoning chapter. The use tables for the town’s zoning districts are found in chapters covering Residential through Industrial (chapters covering 9.07–9.12) and are enforced via § 9.06.030 .
• Each table uses shorthand permit codes (for example P = permitted, CUP = conditional use permit, SPR = site plan & design review, PD = planned development, NP = not allowed); the meaning of these permit types and processing rules is in the code and summarized under § 9.06.030 and related permit chapters .
• If a use is not listed, the Director may find it “similar and compatible” and allow it after written findings — see § 9.06.030 A.3 .
• Specific plans (the SP/Specific Plan Zone) supplant or amplify the base code for properties covered by a specific plan; where silent, the Development Code applies (§ 9.13.020 ) .

District-by-district breakdown

Below are the most decision-relevant districts in the Yucca Valley Development Code. Each subsection gives the district purpose, typical permitted uses, key dimensional standards, and where the rules apply or are found in the code. For full permitted‑use tables see the chapters referenced below and the use tables in chapters 9.07–9.12 as directed by § 9.06.030 .

Residential districts (R-HR, RL, RS variants, RM)

• Purpose: Provide for a range of residential densities from large-lot, hillside, and rural living to multi‑family; preserve neighborhood character and accommodate housing types permitted by the General Plan (see § 9.07.010 ) .
• Typical permitted uses: Single‑family dwellings, accessory uses (garages, sheds, patios), home occupations (subject to HOP rules), small family day care (listed per table), and limited agriculture/landscaping when allowed in the district (see the residential use tables) — permit levels vary by use and district (P / SUP / CUP / NP) .
• Key dimensional standards (typical / decision‑relevant):
  • Typical front setback: 25 ft for many residential and multi‑family standards (see multi‑family and subdivision deviation tables) — see Table 7 and multi‑family Table 2‑13; check § 9.07 tables for exact district values .
  • Side/rear setbacks and lot coverage vary by RS / RM / RL designation; multi‑family projects have explicit unit size and open-space minimums (private open space, common usable open space 30% net site area for most multi‑family) — see § 9.07 and Table 2‑13 for specifics .
  • Animal keeping and small-animal limits are regulated by table (Allowed Number of Small Animals) in § 9.02/9.08 sequences — see Table 2‑7 .
• Where it applies / references: Residential chapters (chapter starting at 9.07) and related use/standards tables; accessory dwelling unit rules are cross‑referenced in § 9.08.100 (see the ADU link for guidance) .

Commercial districts (C-C, C-G, C-O, C-MU, C-N)

• Purpose: Accommodate a range of commercial activities from neighborhood‑serving to general commercial and mixed‑use; implement General Plan commercial land use designations.
• Typical permitted uses: Retail, office, restaurant, personal services, professional offices, and mixed‑use projects where identified. Some care uses (child daycare) and residential (mixed‑use) may be allowed or require CUP/SPR depending on district — see the commercial use table (Table 2‑15) and the notes for use‑specific conditions .
• Key dimensional/permit points:
  • Many commercial uses require SPR (site plan & design review) or CUP depending on intensity and district; check Table 2‑15 for per‑use permit triggers (see § 9.06.030 for the general rule that tables control permit levels) .
  • Design and parking standards apply from article 3 (see the Yucca Valley Design Review and Yucca Valley Parking pages).
• Where it applies / references: Commercial use table in the commercial chapter (Table 2‑15) and associated notes; see § 9.06.030 and the commercial tables for per‑use conditions .

Industrial district (I)

• Purpose: Support industrial, manufacturing, wholesaling, and similar activities with performance standards to limit off‑site impacts.
• Typical permitted uses: Accessory uses (parking, storage when screened), limited industrial uses by right for operations in existing historically used structures (with no enlargement), and other industrial/manufacturing uses that may require CUP, SUP, or SPR per the Industrial use table (Table 2‑18). Hazardous operations and recycling have special notes and cross‑references (see the table notes) .
• Key dimensional standards (Table 2‑19 / § 9.10.030):
  • Minimum lot size: 5 acres (with exceptions via PD/platting)
  • Front setback: 15 ft; rear and side setbacks often 0 ft depending on adjacent use; street side 15 ft
  • Maximum FAR 1.0, maximum lot coverage 70%, height up to 75 ft — see § 9.10.030 and Table 2‑19 .
• Where it applies / references: Industrial chapter (Table 2‑18 & Table 2‑19) and performance standards (chapter 9.34) .

Specific Plan zones (SP / adopted Specific Plans)

• Purpose: The Specific Plan Zone implements locally adopted specific plans (Old Town, Home Depot site, Super Wal‑Mart site) and can set custom land use and development standards for its area; once adopted the specific plan governs uses and standards within its boundaries (see § 9.13.020 and § 9.13.040) .
• Typical effect: SP may allow uses or development standards different from the base zone; when an SP is silent, the Development Code applies. A specific plan also frequently requires additional implementing approvals and CEQA review .
• Where it applies / references: See the list of adopted specific plans (Table 2‑23) and each specific plan document for the exact standards .

Overlay districts (Airport, Fire Safety, AR, etc.)

• Purpose: Overlays place additional constraints where special conditions exist (airports, fire risk, scenic/hillside). Overlays can limit height, uses, require easements, or impose noise/avisory requirements.
• Example: Airport-related overlay rules include height and use limits tied to FAA standards and require avigation easements/noise disclaimers; see § 9.16.060 for airport safety review area requirements .
• Fire Safety overlay (chapter 9.17) imposes slope/fire‑safety development standards and affects lotting and permissible density; see chapter 9.17 for details .
• Where it applies / references: Overlay chapters listed in article 2; overlay maps on the zoning map. Consult Yucca Valley Overlay Districts.

Key decision table (sample of most decision‑relevant standards and where they live)

(Use tables above are summary; consult the code tables in chapters 9.07–9.12 and the notes to each table for per‑use qualifiers and cross‑references — § 9.06.030) .

Practical guidance and interpretation (plain-English synthesis)

• Start with the zoning map to identify the parcel's base zone and any overlays; the use table for that base zone (found with the chapter for that zone) tells you whether a proposed use is P, CUP, SPR, PD, NP, etc. This is the single most important step because it tells you the permit path and whether discretionary hearings or CEQA review are likely (see § 9.06.030 ) .
• If the proposed use is not explicitly listed, the Director can allow it only after a written determination that it is similar and compatible (see the 4 required findings in § 9.06.030 A.3) — plan for that written analysis and possible referral to the Commission .
• Even a “P” (permitted) use must still meet all development standards (setbacks, height, coverage), parking and screening standards, and any overlay requirements — consult Yucca Valley Development Standards, Yucca Valley Parking, and overlay chapters early in design .
• Conditional uses often trigger required public noticing and may require infrastructure or mitigation (see § 9.63.020 for CUP applicability and required improvements/conditions) — budget time and cost for required improvements such as frontage work, drainage, landscaping, and possibly utility undergrounding .
• Where a Specific Plan applies, the specific plan document governs; don’t assume the base table applies — check § 9.13.020 and the listed adopted plans (Table 2‑23) .

Checklist

• Confirm the parcel’s base zoning and overlays on the official Town zoning map (chapter headers and map) — see § 9.01.050 for applicability .
• Read the use table for that zoning district (chapters 9.07–9.12) to determine the use code (P / CUP / SPR / NP) — § 9.06.030 .
• If use is unlisted, prepare justification for a “similar & compatible” determination per § 9.06.030 A.3 .
• Identify development standards (setbacks, lot coverage, FAR, height) for the district and any overlay limits — see the district’s development standard table (e.g., § 9.10.030 for Industrial) .
• Confirm parking requirements and off‑street loading per the parking chapter and incorporate in site plan — see Yucca Valley Parking.
• Check for design review or site plan review triggers and link to Yucca Valley Design Review.
• Check overlay rules (fire, airport, AR) and any avigation or easement requirements — see § 9.16.060 and chapter 9.17 .
• Determine if the project will require CUP/PD and prepare for public noticing, CEQA, and potential infrastructure conditions per § 9.63.020 .
• If proposing or affected by an ADU, follow the ADU-specific rules (see § 9.08.100 and Yucca Valley ADUs) .
• Verify building code (Title 24 / California Building Standards Code) requirements for structure safety and habitability during the permit phase.

Risks & Ambiguities

Plain-English Summary

The Yucca Valley Development Code lists allowed and conditional uses in district-specific tables; your first step is to identify the parcel’s zone and check that table. If the use is allowed (P) you still must meet development standards for setbacks, coverage, parking, and overlays; if it’s listed as CUP or unlisted you will need discretionary review and written findings. Key code rules are in § 9.06.030 (use tables and permit types) and the district chapters (e.g., § 9.07 for residential and § 9.10.030 for industrial) — consult those sections early and verify parcel‑specific overlays and specific plans .

Source References

• Town of Yucca Valley Development Code, “Permitted Land Uses and Planning Permit Requirements,” § 9.06.030 — use tables located in chapters 9.07–9.12 .
• Town of Yucca Valley Development Code, Residential/Hillside Reserve districts and use/standard tables, chapter 9.07 and related tables (multi‑family standards Table 2‑13) .
• Town of Yucca Valley Development Code, Commercial use tables (Table 2‑15) and notes (see commercial chapter tables) .
• Town of Yucca Valley Development Code, Industrial uses and development standards, § 9.10.030 (Table 2‑19, Table 2‑18) .
• Town of Yucca Valley Development Code, Conditional Use Permit applicability and thresholds, § 9.63.020 and Table 4.2 .
• Town of Yucca Valley Development Code, Specific Plans (SP) effect and adopted specific plans (Table 2‑23), § 9.13.020 / 9.13.040 .
• Town of Yucca Valley Development Code, Airport overlay standards and avigation easements, § 9.16.060 .
• Town of Yucca Valley Development Code (title/administration), § 9.01.010 – 9.01.050 (Development Code title and applicability) .

Retrieved passages

• Yucca Valley Zoning Code (section identifies) High relevance show source text
• Yucca Valley Zoning Code (section identifies) High relevance show source text
• Yucca Valley Zoning Code (section 9.06.030) High relevance show source text
• Yucca Valley Zoning Code (Chapter 9.66) High relevance show source text
• Yucca Valley Zoning Code (chapter 9.71) High relevance show source text
• Yucca Valley Zoning Code (section 9.31.030) High relevance show source text
• California Building Code (section for) High relevance show source text
• Yucca Valley Zoning Code (chapter 9.33) High relevance show source text

Cited sections

• Town of Yucca Valley Development Code, “Permitted Land Uses and Planning Permit Requirements,” **§ 9.06.030** — use tables located in chapters 9.07–9.12 . (§ 9.06.030)
• Town of Yucca Valley Development Code, Residential/Hillside Reserve districts and use/standard tables, chapter **9.07** and related tables (multi‑family standards Table 2‑13) .
• Town of Yucca Valley Development Code, Commercial use tables (Table 2‑15) and notes (see commercial chapter tables) . (chapter tables)
• Town of Yucca Valley Development Code, Industrial uses and development standards, **§ 9.10.030** (Table 2‑19, Table 2‑18) . (§ 9.10.030)
• Town of Yucca Valley Development Code, Conditional Use Permit applicability and thresholds, **§ 9.63.020** and Table 4.2 . (§ 9.63.020)
• Town of Yucca Valley Development Code, Specific Plans (SP) effect and adopted specific plans (Table 2‑23), **§ 9.13.020 / 9.13.040** . (§ 9.13.020)
• Town of Yucca Valley Development Code, Airport overlay standards and avigation easements, **§ 9.16.060** . (§ 9.16.060)
• Town of Yucca Valley Development Code (title/administration), **§ 9.01.010 – 9.01.050** (Development Code title and applicability) . (§ 9.01.010)
• YuccaValley_ZoningCode.md

• Official Yucca Valley code library