Local zoning · Apple Valley

Apple Valley — Zoning

Zoning under the Apple Valley local zoning and planning code, with the controlling citations.

Ask a question free See coverage

Last reviewed: July 3, 2026

Overview

This page summarizes what the Town of Apple Valley Development Code (often referred to locally as the Town's zoning ordinance) actually says about zoning: the official districts, overlays, typical permitted uses, and the controlling development standards you will rely on when planning projects. It is grounded in the Town Development Code chapters establishing districts, site development standards, overlays, and specific plans — cited to the controlling sections below. See the checklist and risks for practical next steps and items to verify with staff.

How the code is organized (quick)

  • Zoning districts are created in § 9.05.030 (table of districts and map designations) .
  • The Official Zoning Districts Map is incorporated into the Code in § 9.05.040 (adoption of zoning map) .
  • Residential development standards live in Chapter 9.28 (see § 9.28.040 for dimensional rules cited below) .
  • Commercial/office site development standards are collected in § 9.35.040 (Table 9.35.040‑A) .
  • Specific plan areas and custom zoning (SP) are authorized in Chapter 9.03 and example Apple Valley Commercial Specific Plan rules are in Chapter 9.40 .

Note: For parking calculations and reductions, the Code points to Chapter 9.72; see the Town's parking rules for shared-parking and study procedures. Link to parking in-text here for applicants: parking .

District-by-district breakdown

Below each district is given a concise, practical description: stated purpose, typical permitted uses (what the Code anticipates), key dimensional standards you will check first, and where that district generally applies in Apple Valley (as stated in the Code). All requirements cited to the controlling Town Code section.

Notes on sources: the master list of district names is appointed in § 9.05.030 . Dimensional tables are primarily from § 9.28.040 for residential and § 9.35.040 for commercial/office standards file.

R-VLD (Very Low Density Residential)

  • Purpose: Very low density — the largest-lot residential classification (1 dwelling unit / 5+ gross acres in some suffixes). § 9.05.030 .
  • Typical uses: Single-family dwellings, large estate lots, limited accessory structures. § 9.05.030 .
  • Key standards: Very large minimum lot sizes (suffixes indicate 10, 20, or 40 acre minimums for some lands outside Town limits); consult Chapter 9.28 for setbacks and lot‑coverage rules applicable to very-low-density categories. § 9.28.040 .
  • Where: Townwide where mapped; see the Official Zoning Districts Map in § 9.05.040 for parcel-specific application.

R-A (Residential Agriculture)

  • Purpose: Combine low‑density residential with agricultural uses (acre‑scale lots). § 9.05.030 .
  • Typical uses: Single-family homes, hobby agriculture, animal keeping subject to animal-keeping buffers. See animal buffer standards noted in § 9.29.030 and Table notes. .
  • Key standards: Setbacks, min lot area, and max lot coverage referenced in Table for residential districts in § 9.28.040.
  • Where: Mapped in lower‑density fringes and sphere-of‑influence; prezoning rules apply per § 9.05.110.

R-LD (Low Density Residential)

  • Purpose: Typical detached single-family neighborhood lots at lower densities. § 9.05.030 .
  • Typical uses: Single-family homes, accessory structures, small home-based businesses if permitted. § 9.28.040 contains the dimensional rules (setbacks, height 35 ft typical, lot coverage ~25% in many single-family districts) .
  • Where: Common inside town, consult the Official Zoning Map § 9.05.040.

R-E / R-E ¾ (Estate Residential / Estate Residential ¾)

  • Purpose: Large estate lots; R‑E ¾ is the ¾‑acre variant. § 9.05.030 .
  • Typical uses: Estate single‑family homes, equestrian accessory uses possible (see R-EQ).
  • Key standards: Larger setbacks and lower lot coverage; sidewalk/curb rules differ (rolled curbs allowed in low‑density and estate districts; sidewalks sometimes not required) — see § 9.28.040 and sidewalk provisions.

R-EQ (Equestrian Residential)

  • Purpose: Residential with equestrian facilities (larger lot sizes 0.4–0.9 net acre). § 9.05.030 .
  • Typical uses: Homes with horse facilities; animal‑keeping compatibility buffers apply (see Table notes and § 9.29.030). file

R-SF (Single-Family Residential)

  • Purpose: Standard single-family neighborhoods. § 9.05.030 .
  • Typical uses: Detached single-family houses; accessory dwellings must follow ADU rules. See the Town ADU guidance: ADUs .
  • Key standards: Minimum dwelling unit sizes (typical 1,200 sq ft floor area minimum listed as baseline in Table notes), setbacks and height (35 ft typical). See § 9.28.040 for full numeric table.

R-M (Multi-Family Residential)

  • Purpose: Medium to higher-density residential (2–20 du/net acre). § 9.05.030 .
  • Typical uses: Apartments, duplexes, townhomes. Multi-family design standards are in Chapter 9.31 and Planned Residential Development rules in § 9.29.080 apply for PRDs. .
  • Key standards: Density bands (2–20 du/ac), building height may vary (some multi-family allowances up to 50 ft in designated zones); parking, open space, trash enclosures, bicycle parking and other site elements are specified in Chapters 9.31, 9.72 and related sections. § 9.29.080 and § 9.31 file

MHP (Mobile Home Park)

  • Purpose: Mobile home park development rules and minimums; see § 9.05.030.
  • Typical uses: Manufactured-home communities, accessory buildings. Special development standards in Chapter 9.29 apply.

M-U (Mixed Use)

  • Purpose: Allow combination of residential and commercial/office uses; density and commercial standards cross‑reference residential and commercial chapters. § 9.05.030 and mixed-use development standards reference Chapters 9.35–9.37 and parking 9.72. file
  • Typical uses: Ground‑floor retail with residential above; residential permitted on any story, commercial on first/second, commercial above residential with CUP. See Mixed Use standards and development standards: § 9.35.x and § 9.36.

PRD (Planned Residential Development)

  • Purpose: Flexible project-level standards when a unified plan is approved; development standards not covered revert to similar Code standards. See § 9.29.080 and related Planned Development sections.
  • Typical uses: Master-planned residential subdivisions, shared amenities, HOA obligations. Key: development standards are set by the approved PRD permit and must comply with the Code minimums. § 9.29.080

O-P (Office Professional)

  • Purpose: Professional offices and lower‑intensity commercial; standards in § 9.35.040 apply.
  • Typical uses: Small offices, clinics, professional services.
  • Key standards (commercial table): Minimum lot area 7,500 sf; front setbacks from local streets 35 ft; height limits vary (25 ft within 100' of residential; up to 48 ft elsewhere per Table) — see § 9.35.040 (Table 9.35.040‑A).

C-G (General Commercial)

  • Purpose: Broad retail and service uses, shopping centers along major roadways. See the Apple Valley Commercial Specific Plan narrative (Chapter 9.40) for an example of C‑G application. § 9.40.020 and § 9.35.040 file
  • Typical uses: General retail, grocery, restaurants, convenience stores, off‑sale alcohol; minor auto repair conditionally permitted; drive‑throughs require Special Use Permit. § 9.40.020
  • Key standards: Minimum lot area 10,000 sf; front setback 35 ft from local streets; height limits generally 35 ft, reduced to 25 ft within 100' of residential — see § 9.35.040.

C-S (Service Commercial), C-R (Regional Commercial), C-V (Village Commercial)

  • Purpose: Graduated commercial intensity classes (service, regional shopping, village‑center). § 9.35.040 and Table identify distinct minimum lot sizes, setbacks and heights.
  • Typical uses and key standards: Refer to Table 9.35.040‑A (min lot area 10,000 sf typical for C‑S/C‑R; C‑V often allows smaller front setbacks 10 ft on local streets to create village typology). § 9.35.040

I-P (Planned Industrial) / I-RE (Resource Extraction)

  • Purpose: Industrial, processing and extractive operations; specific industrial zones also exist in specific plans (e.g., NAVISP). § 9.05.030 and NAVISP excerpts. file
  • Typical uses: Warehousing, light manufacturing, airport‑related industry (see Airport Overlay and NAVISP). § 9.65 and NAVISP text detail compatibility and airport overlay procedures.

P-F (Public Facilities)

  • Purpose: Municipal buildings, public services and utilities. § 9.05.030.

OS-C / OS-R (Open Space — Conservation / Recreation)

  • Purpose: Open-space lands, parks, recreation and conservation. § 9.05.030 and used for parks such as Civic Center Park in the Commercial Specific Plan example. § 9.40.020 mentions OS‑R. file

SP (Specific Plan)

  • Purpose: Allows area‑specific rules; SP zoning is adopted by ordinance and the SP document governs uses, density and development standards for the SP area. See § 9.03.070 and Apple Valley Commercial SP in Chapter 9.40. file

Overlay Districts (Airport, Flood, Seismic, Ranchos Residential Overlay, etc.)

  • Purpose: Overlays add requirements on top of the underlying zone. For example, the Airport Overlay (A‑1, A‑2) and the Airport compatibility review rules are in Chapter 9.65; the Flood Hazard (FH) overlay uses FEMA FIRM maps and Chapter 9.62; the Ranchos Residential Overlay (RRO) modifies setbacks in some areas. § 9.65, § 9.62, § 9.63 and § 9.05.030. filefile
  • Practical note: When an overlay applies, the more restrictive rule controls. See § 9.62.060.A (Flood Hazard: overlay in addition to underlying district).

Quick reference — decision‑relevant standards (sample)

This table pulls the most commonly checked numbers a planner, homeowner or developer will use at intake. Always confirm the parcel's specific mapped district and any overlay or recorded map setback lines (see § 9.35.040 and § 9.28.040).

Topic / District Typical standard (example) Code Reference
Minimum lot area — O‑P 7,500 sq ft § 9.35.040
Minimum lot area — C‑G 10,000 sq ft § 9.35.040
Front setback (local street) — C‑G / O‑P 35 ft § 9.35.040
Front setback — C‑V (village) 10 ft § 9.35.040
Height — typical residential 35 ft (25 ft where within 100' of residential uses for some commercial buildings) § 9.28.040 and § 9.35.040 file
Lot coverage — typical R zones 25% (varies by residential district) § 9.28.040
Animal‑keeping buffer 25–65 ft depending on facility; see animal-keeping rules and PRD notes § 9.29.030 and Table notes file
Mixed‑use parking study allowed Shared parking accepted with Planning Commission approval as CUP/Conditional Use Mixed‑Use standards and § 9.72 (parking) file

Practical guidance & interpretation notes

  • Always start at the Official Zoning Districts Map adopted in § 9.05.040 to confirm the parcel's mapped district and overlays — the code treats the map as part of the Development Code. § 9.05.040 .
  • For commercial projects check § 9.35.040 Table 9.35.040‑A first (lot area, setbacks, heights) then the specific-use rules in Chapter 9.36, design standards in 9.37, performance standards 9.70, and parking 9.72. § 9.35.040 . Link for design details: Design Review (first mention).
  • For residential development consult Chapter 9.28 (site design, front‑setback averaging, projections above height limit, curb/sidewalk rules). Note the allowance for rolled curbs and lack of sidewalks in some very‑low/estate districts; see § 9.28.040. § 9.28.040
  • Overlay districts (airport, flood, seismic, Ranchos Residential Overlay) are additive; the Code explicitly states the stricter rule controls. See overlay chapters 9.62 (flood), 9.65 (airport) and Ranchos Overlay chapter references. § 9.62.060 and § 9.65.040 file. Link for overlays: Overlay Districts.
  • For ADUs: The Code refers to accessory dwelling provisions and state law constraints; local ADU rules are summarized in the Town ADU guidance. See ADUs and cross-check against § 9.05.070 (Similar Uses) when a use is not listed.
  • For parking reductions and shared parking studies in Mixed Use projects, the Code allows modification via an approved parking study; the Planning Commission must approve off‑street parking modifications as a CUP/Conditional Use. See Mixed Use rules and § 9.72 (parking). parking

Checklist (what an applicant must satisfy at intake)

  • Confirm parcel's mapped zone and overlays on the Official Zoning Districts Map (§ 9.05.040) .
  • Identify applicable district and read the numeric standards in § 9.28.040 (residential) or § 9.35.040 (commercial) — setbacks, heights, lot area, lot coverage. file.
  • Check overlay chapters that may add constraints (Airport § 9.65, Flood § 9.62). file
  • If mixed‑use or commercial, prepare parking consistent with § 9.72; consider a parking study for shared parking reductions. parking
  • Confirm design review or development-permit triggers (Chapters 9.17, 9.36, 9.37) and prepare materials for Design Review.
  • If requesting deviations, Deviation Permits rules and limits are in § 9.25.030 (minor exceptions) — verify what the Director can approve vs. what requires a variance. § 9.25.030
  • For any use not explicitly listed, the Director may find it “similar” under § 9.05.070 — be prepared to justify similarity. § 9.05.070

Risks & Ambiguities

Issue Why it matters What to verify
District mapping vs. recorded final‑map setbacks Some properties have recorded Final Maps or Parcel Maps that show different building setback lines — those control unless modified via variance or deviation. § 9.35.040 notes recorded maps override typical table setbacks. Verify the parcel's recorded Final Map or Composite Development Plan at Town offices and read the map note. Verify with the jurisdiction.
Overlay requirements (Airport, Flood) Overlays can impose stricter restrictions (noise, safety, elevations); failure to check may block permits or require compatibility review. § 9.65 and § 9.62. file Confirm overlays on the Official Zoning Map; request Airport compatibility review if inside Airport Overlay. Verify with the jurisdiction.
Differences between PRD/SP approvals and base zone SP/PRD documents can supersede base standards where expressly regulated. § 9.03.070 and § 9.40 explain that SP regulations govern the area. file Check whether property lies in an SP/PRD and read the SP document. Recorded conditions may control.
Interpretation of “similar uses” Director discretion under § 9.05.070 can interpret whether an unlisted use is allowed — can be subjective. Prepare evidence comparing use intensity and impacts to listed uses; verify likely required findings with staff.
Off‑street parking reductions for Mixed Use Parking studies can be accepted, but reductions require Commission approval as a Conditional Use / Development Permit per Mixed Use rules. If seeking shared‑parking reductions, prepare a professional parking study and plan for Planning Commission review.

Plain‑English summary

Apple Valley’s Development Code creates named zones (for example, R‑SF, C‑G, O‑P, I‑P) and overlay districts (for example, Airport (A‑1/A‑2), Flood Hazard (FH), Ranchos Residential Overlay). The Official Zoning Districts Map plus the numeric tables in § 9.28.040 (residential) and § 9.35.040 (commercial) tell you the setbacks, lot sizes, heights and lot coverage to design to; overlays and specific plans can change those rules and the more restrictive rule controls — always confirm the parcel mapping and any recorded final‑map setback lines before submitting. filefile

Source References

  • § 9.05.030 (establishment of zoning districts; Table 9.05.030‑A)
  • § 9.05.040 (adoption of the Official Zoning Districts Map)
  • § 9.28.040 (residential site development standards, front‑setback averaging, curb/sidewalk rules)
  • § 9.35.040 (Site Development Standards — Table 9.35.040‑A for commercial/office districts)
  • § 9.03.070 and Chapter 9.40 (Specific Plan rules; Apple Valley Commercial Specific Plan example) file
  • § 9.25.030 (Deviation Permit authority and the scope of minor exceptions)
  • § 9.05.070 (Similar uses — Director authority)
  • § 9.62.060 (Flood Hazard Overlay general provisions)
  • § 9.65.030–9.65.040 (Airport Overlay applicability and review)

Sources

Retrieved passages

  • Apple Valley Zoning Code (Section 9.72) High relevance
  • Apple Valley Zoning Code (Section 9.25) High relevance
  • Apple Valley Zoning Code High relevance
  • Apple Valley Zoning Code (Section 9.72.060) High relevance
  • Apple Valley Zoning Code (Chapter 9.40) High relevance
  • Apple Valley Zoning Code (Section 9.03.050) High relevance
  • Apple Valley Zoning Code (Section 9.31.050) High relevance
  • Apple Valley Zoning Code (Chapter 9.05) High relevance

Cited sections

Frequently asked questions

What can I build on an R‑SF lot in Apple Valley?

You can generally build a single‑family dwelling and usual accessory structures, subject to the R‑SF dimensional standards (setbacks, height ~35 ft, lot coverage ~25%) listed in the residential site development table; accessory dwelling units must follow ADU rules. Confirm your parcel’s specific mapped zone and any overlays on the Official Zoning Districts Map § 9.05.040 and the numeric details in § 9.28.040. file

What are Apple Valley setback requirements?

Setbacks depend on the zoning district and are tabulated in the Code. Commercial/office setbacks are listed in § 9.35.040 (Table 9.35.040‑A — e.g., 35 ft front from local streets for O‑P and C‑G; C‑V can be 10 ft) and residential setbacks are in § 9.28.040. Always check for recorded Final Map setback lines which may supersede the table. file

Do I need design review in Apple Valley?

Possibly — commercial development and many exterior changes reference Chapter 9.37 design standards and Chapter 9.17 for Development Permits; the Code requires design compliance for commercial projects in § 9.35.040 and related chapters. See the Town design review page for application triggers and submittal requirements.

How do overlays like the Airport or Flood Hazard affect my project?

Overlays are in addition to the base zoning and the more restrictive rule applies. The Airport Overlay requires compatibility review for new nonresidential development (§ 9.65) and the Flood Hazard overlay relies on FEMA maps and Chapter 9.62 requirements. Always check the Official Zoning Map for overlays and follow the overlay chapter’s special procedures. file

Can I reduce parking by doing a shared‑parking study for a mixed‑use project?

Yes — the Code allows parking reductions in Mixed‑Use projects through an approved parking study; shared‑parking assumptions require Planning Commission approval (mixed‑use rules reference Chapter 9.72 for parking). Prepare a professional study and plan for Commission review. parking

Where do specific plan rules fit versus the base zone?

A Specific Plan (SP) adopted by ordinance becomes the zoning for that area and its customized regulations control where they are explicit. The Code explains SP adoption and that, unless otherwise specified, base Code regulations still apply. See § 9.03.070 and the Apple Valley Commercial SP example in Chapter 9.40. file

What are the limits of Director authority for deviations or "similar uses"?

The Director can grant minor deviations (e.g., up to 10% interior side setback reductions in residential districts; certain commercial exceptions) under § 9.25.030 and can determine whether a use not listed is “similar” under § 9.05.070 — both require findings set out in the Code. More substantial relief requires variance procedures. § 9.25.030 and § 9.05.070. file

Does the Code mention landscaping or screening requirements?

Yes — landscaping and water‑conservation rules and minimum landscape areas are referenced across Chapters and specific standards (for example, multi‑family and commercial landscaping minimums, and Chapter 9.75 for water conservation/landscaping). See the Development Standards and Landscaping chapters; link to landscaping: Landscaping and Screening.

Are there special rules for properties near the Apple Valley Airport?

Yes — properties in the Airport Overlay are subject to airport compatibility review and some uses/expansions require extra review or referral to the Airport Manager; the Airport Overlay chapters describe applicability and prohibitions. See § 9.65 (Airport Overlay) and the NAVISP excerpts.

More in Apple Valley code

Ask about any Apple Valley property

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

Start Free Trial

More Apple Valley zoning topics

Apple Valley Land Use

Apple Valley Development Standards

Apple Valley Parking

Apple Valley Design Review

Apple Valley Overlay Districts

Apple Valley Historic Preservation

Apple Valley Signage

Apple Valley Nonconforming Uses

Apple Valley Variances and Exceptions

Apple Valley Landscaping and Screening

Apple Valley overview