Lompoc — Overlay Districts

Last reviewed: July 2, 2026

Overview

Overlay districts in Lompoc are zoning layers that add or change rules for specific areas on top of the base zones on the official zoning map. They modify permitted uses, development standards, and review procedures so projects better protect airport operations, cultural resources, H Street redevelopment goals, winery event activity, or allow planned development flexibility. See the City's zoning map first to confirm whether a parcel lies inside an overlay and then read the applicable overlay rules in § 17.224 of the Zoning Code .

How to read this page

• Wherever the overlay modifies a base-zone rule I quote the controlling code cross‑reference (for example § 17.224.030). Each such requirement is grounded in the City ordinance cited below. For fuller project-level rules (parking, landscaping, signs, design review, etc.) see the other topic pages linked in the text (first occurrence only): development standards, parking, design review, historic preservation, ADUs, and the California Building Standards Code.

What the Code says — district-by-district

Notes: All overlays are collected in Chapter 17.224 of Lompoc’s Zoning Code (start at § 17.224.010). Allowed uses follow the base zone except where Table 17.224.030.A modifies the base zone; development standards follow the base zone except where Table 17.224.040.A modifies them. Where an overlay refers to an approval process (e.g., Preliminary Development Plan, Temporary Use Permit), the cited subsections or chapters control. See § 17.224.010–050 for the chapter-level rules and Tables 17.224.030.A and 17.224.040.A for use and standard matrices .

Airport Overlay (AO)

• Purpose: The AO protects aircraft operations and safety around Lompoc Airport, using limits derived from the Santa Barbara County Airport Land Use Plan and the local Lompoc Airport Master Plan (LAMP) § 17.224.020.A .
• Typical permitted uses: Uses default to the base zone but Table 17.224.030.A identifies specific allowances or higher-permit thresholds inside the AO (for example, some agricultural uses are allowed, others require a Conditional Use Permit (CUP)); check the AO column in Table 17.224.030.A for a complete list .
• Key dimensional / operating standards:
  • Height limits in the clear zone: no structure or vegetation may exceed 15 ft above the airport elevation baseline of 88.04 ft MSL; the approach zone height limit is 150 ft above that elevation § 17.224.050.A.3 .
  • Prohibited or limited activities: illuminated signs, uses that direct flashing/steady light at aircraft, reflective surfaces that could glare toward aircraft, and activities that generate electrical interference are explicitly restricted § 17.224.050.A.2 .
  • Processing requirement: any development in the AO must be referred to and cleared by the Airport Land Use Commission before Building or Grading Permits are issued (ALUC review required) § 17.224.050.A.4 .
• Where it applies: parcels mapped on the City Zoning Map as AO; use the zoning map and the Airport Land Use Commission boundaries referenced in § 17.224.020.A .

Cultural Resources Overlay (CRO)

• Purpose: The CRO protects archaeological and cultural resources (notably on Lompoc's south side) and prescribes procedures where ground disturbance is planned § 17.224.020.B .
• Typical permitted uses: Default to the base zone unless specifically modified in Table 17.224.030.A; most non‑archaeological uses defer to the base zone language (see the CRO column in Table 17.224.030.A) .
• Key procedures & standards:
  • Applicability is defined geographically (properties south of Olive Ave centerline with average slope <30% and the Archaeological High Sensitivity Zone) and applies to any permit involving ground disturbance, public-right-of-way private-utility work, annexation projects, and demolition that disturbs ground § 17.224.050.B.1 .
  • Where ground‑disturbing work is proposed the applicant must either obtain a Phase 1 archaeological evaluation or retain a qualified archaeological monitor for ground‑disturbing activity; findings/reports are submitted to the Department and a Cultural Resource Protection Program must be implemented if resources are uncovered § 17.224.050.B.3–4; Table 17.224.050.A lists evaluation options and triggers .
  • Environmental review: projects remain subject to CEQA/NEPA as required, but when cultural resources are the only issue the CRO standards can be applied directly without separate environmental documentation § 17.224.050.B.2 .
• Where it applies: parcels identified in the CRO mapping described above; the ordinance specifies the CRO mapping references (Spanne, 1988 Cultural Resources Study) § 17.224.050.B.1 .

Southside Overlay (SO)

• Purpose: The SO recognizes special status for defined “Southside Residential Properties”; it treats those properties as legally conforming despite underlying base‑zone density changes adopted at the time Ordinance No. 1566(13) was effective § 17.224.020.C .
• Typical permitted uses: Base-zone uses control unless the Table 17.224.030.A or the SO text modifies them; the main legal effect is the non‑conforming/legally conforming status for the properties listed in the implementing exhibit § 17.224.020.C .
• Key standards: The SO itself doesn't rewrite setbacks or FAR in the chapter tables — it operates mainly as a legal status overlay (see Table 17.224.040.A where SO column shows “refer to base zone” for most standards) § 17.224.040.A .
• Where it applies: specific parcels listed in Exhibit A to Ordinance No. 1566(13) — verify parcel inclusion with the City (the SO text and map are the determinative source) § 17.224.020.C .

Planned Development Overlay (PD)

• Purpose: The PD provides a flexible, design-based route for projects that need tailored standards (density, setbacks, lot coverage, etc.) approved through a Preliminary Development Plan § 17.224.020.D .
• Typical permitted uses: Uses default to the base zone but the PD can authorize mixes or exceptions that otherwise conflict with the base standards; Table 17.224.030.A lists uses for PD and the PD's own approved Preliminary Development Plan controls specific deviations .
• Key dimensional / process standards:
  • Development standards inside PD generally refer to the base zone or to the approved Preliminary Development Plan; the PD overlay expects a site‑specific Preliminary Development Plan processed under Chapter 17.532 (see findings required in § 17.532.050) .
  • The PD may be adopted in any zone (except Specific Plan zone) and density cannot exceed the General Plan Land Use Element maximum § 17.224.050.C; § 17.532.050.C .
  • Preliminary Development Plan applications follow the public hearing and noticing rules in Chapter 17.608 and must satisfy PD findings in § 17.532.050 .
• Where it applies: where the PD overlay is mapped or adopted concurrent with a rezoning; specific PD standards are set by the approved Preliminary Development Plan § 17.224.040.A .

Special Event Overlay (SEO)

• Purpose: The SEO enables and regulates hospitality/tasting/event uses in industrial‑zoned winery/micro‑alcohol areas so events are allowed but controlled § 17.224.020.E .
• Typical permitted uses: The SEO modifies the I and BP base zones to explicitly allow events and tasting activities with permitting thresholds listed in Table 17.224.030.A (SEO column) — consult the Table for specific use-by‑zone permit types .
• Key operating standards:
  • Short events may be exempt from a Temporary Use Permit if they are under 72 hours, do not exceed approved occupant loads, and do not conduct manufacturing while open to event attendees § 17.224.050.D.1 .
  • A Special Event Temporary Use Permit (TUP) can be issued (valid up to 365 days, limited normally to one event per month under a single TUP) and has specific application and operational conditions (noise, circulation, removal of temporary signage/equipment, repairs to public facilities if damaged) § 17.224.050.D.3 .
  • On‑street parking adjacent to the lot can count toward required non‑residential parking in the SEO (see parking chapter and § 17.308. provisions) § 17.308. and § 17.224.040.A / § 17.224.050.D .
• Where it applies: mapped SEO areas (I or BP base zones that are tourist‑oriented); check Table 17.224.030.A and the zoning map for parcel-level applicability .

H Street Overlay (HSO)

• Purpose: The HSO focuses redevelopment of lots along the H Street corridor to encourage pedestrian‑oriented mixed use, higher intensity infill, and multimodal access § 17.224.020.F .
• Typical permitted uses: The HSO generally enables the base commercial/mixed‑use spectrum and Table 17.224.030.A shows many retail, multi‑family, ADU, and live/work uses as permitted or allowed with an Administrative/Minor/Conditional Use Permit in HSO § 17.224.030.A .
• Key dimensional / urban‑design standards:
  • The HSO column in Table 17.224.040.A gives a front setback of 10 ft along H Street, 0 ft interior side setback, a 0 ft rear setback in some circumstances, and a Floor Area Ratio (FAR) up to 1.0 (check the table for lot‑type exceptions) § 17.224.040.A .
  • Build‑to, build‑to‑area width, and corner lot build‑to requirements may also interact with HSO rules in Chapter 17.212 for Old Town and H Street area standards — consult § 17.212 and the HSO column notes when designing along H Street .
• Where it applies: parcels along the H Street corridor mapped as HSO; confirm precise boundaries with the City zoning map § 17.224.020.F .

Quick reference table — most decision‑relevant items

Checklist — what an applicant must satisfy for overlay projects

• Confirm overlay mapping for the parcel on the official zoning map (Zoning Map / § 17.204.020) .
• Confirm base‑zone allowed uses and then check Table 17.224.030.A for overlay modifications; the overlay controls if conflicts exist § 17.224.030.A .
• If in the AO, obtain ALUC clearance and confirm compliance with LAMP restrictions; design for the 15 ft clear‑zone limit where applicable § 17.224.050.A.1–4 .
• If in the CRO and project involves ground disturbance, submit a Phase 1 evaluation or commit to archaeological monitoring and budgeting for a Cultural Resource Protection Program § 17.224.050.B.3–4 .
• If proposing a PD, prepare a Preliminary Development Plan and satisfy Chapter 17.532 application, noticing, and findings § 17.532.030–050 .
• If proposing events in the SEO, map event types to exemption criteria (≤72 hrs, occupant load limits), or apply for a Special Event TUP with required operations conditions § 17.224.050.D.1–3 .
• For projects in HSO, design to H Street build‑to/setback/FAR rules and expect pedestrian‑oriented frontage requirements; consult Chapter 17.212 and Table 17.224.040.A § 17.224.040.A; § 17.212 .
• Coordinate required reviews: design review (see design review), parking analysis (parking), landscape/screening (landscaping and screening) and sign compliance (signage); confirm any nonconforming status with § 17.620 if needed .
• Verify building permits will comply with the California Building Standards Code where structural or life‑safety work is involved.

Risks & Ambiguities

Plain-English Summary

If your property lies in one of Lompoc’s overlays (AO, CRO, SO, PD, SEO, HSO), the overlay can add safety, cultural‑resource, design, or event rules on top of the base zone. For example, the AO limits heights and lighting near the airport and needs ALUC sign‑off, the CRO requires archaeology studies or monitoring for ground work, the PD lets you seek a site‑specific Preliminary Development Plan, the SEO sets how wineries run special events, and the HSO changes setbacks and FAR along H Street — all rules are in Chapter 17.224 and the overlay tables cited above .

Source References

• City of Lompoc Zoning Code, Chapter 17.224 (Overlay Zones) — § 17.224.010–050 (purpose, overlays list, allowed uses, additional standards) .
• Table 17.224.030.A: Overlay Zones Allowed Uses (use matrix and permit types) — Table text and notes (see Table 17.224.030.A) .
• Table 17.224.040.A: Overlay Zones Development Standards (setbacks, heights, FAR references) — Table text (see Table 17.224.040.A) .
• AO additional standards (LAMP compliance, height/lighting prohibitions, ALUC processing): § 17.224.050.A .
• CRO standards and cultural resource evaluation requirements: § 17.224.050.B and Table 17.224.050.A .
• PD procedural and findings requirements (Preliminary Development Plan): Chapter 17.532, especially § 17.532.020–050 .
• SEO event rules and Special Event TUP process: § 17.224.050.D and § 17.404.210 (Temporary Uses) .
• H Street / Old Town development standards referenced in overlay tables: Chapter 17.212 and Table 17.212.040.A (build‑to and frontage rules) .
• Zoning map and zone establishment rules: § 17.204.010–020 (Zones established; Zoning Map) .
• Parking reductions and related standards referenced by overlays: Chapter 17.308 (Parking Standards) § 17.308. .

Retrieved passages

• Lompoc Zoning Code (§ 11) Medium relevance show source text
• Lompoc Zoning Code (§ 11) Medium relevance show source text
• Lompoc Zoning Code (§ 11) Medium relevance show source text
• Lompoc Zoning Code (§ 11) Medium relevance show source text
• Lompoc Zoning Code (Section 17.324.070.B) Medium relevance show source text
• Lompoc Zoning Code (Title 17.) Medium relevance show source text
• Lompoc Zoning Code (§ 11) Medium relevance show source text
• Lompoc Zoning Code (§ 17.104.030.) Medium relevance show source text
• Lompoc Zoning Code (§ 17.224.040.) High relevance show source text
• Lompoc Zoning Code (§ 11) High relevance show source text
• Lompoc Zoning Code High relevance show source text
• Lompoc Zoning Code High relevance show source text
• Lompoc Zoning Code (§ 11) High relevance show source text

Cited sections

• City of Lompoc Zoning Code, Chapter 17.224 (Overlay Zones) — **§ 17.224.010–050** (purpose, overlays list, allowed uses, additional standards) . (Chapter 17.224)
• Table 17.224.030.A: Overlay Zones Allowed Uses (use matrix and permit types) — Table text and notes **(see Table 17.224.030.A)** .
• Table 17.224.040.A: Overlay Zones Development Standards (setbacks, heights, FAR references) — Table text **(see Table 17.224.040.A)** .
• AO additional standards (LAMP compliance, height/lighting prohibitions, ALUC processing): **§ 17.224.050.A** . (§ 17.224.050.A)
• CRO standards and cultural resource evaluation requirements: **§ 17.224.050.B** and Table **17.224.050.A** . (§ 17.224.050.B)
• PD procedural and findings requirements (Preliminary Development Plan): Chapter **17.532**, especially **§ 17.532.020–050** . (§ 17.532.020)
• SEO event rules and Special Event TUP process: **§ 17.224.050.D** and **§ 17.404.210** (Temporary Uses) . (§ 17.224.050.D)
• H Street / Old Town development standards referenced in overlay tables: Chapter **17.212** and Table **17.212.040.A** (build‑to and frontage rules) .
• Zoning map and zone establishment rules: **§ 17.204.010–020** (Zones established; Zoning Map) . (§ 17.204.010)
• Parking reductions and related standards referenced by overlays: Chapter **17.308** (Parking Standards) **§ 17.308.** . (§ 17.308.)
• Lompoc_ZoningCode.md

• Official Lompoc code library