Local zoning · Tehachapi
Tehachapi — Overlay Districts
Overlay Districts under the Tehachapi local zoning and planning code, with the controlling citations.
Last reviewed: July 2, 2026
Overview
Tehachapi’s adopted Zoning Code does not use the phrase “overlay district” as a primary naming convention. Instead, the Code implements area-specific controls through Transect zones (T2–T5), mapped Special Districts (for example SD2.1 — Tehachapi Blvd. West), and project-level tools such as Planned Development (PD). Where you would expect overlays (special rules that layer over an underlying zone), Tehachapi most commonly applies zone-specific standards, mapped Special Districts, and plan/precise plan approvals to achieve the same effect (§ 3.20.020; § 3.20.090; § 3.30.160) .
Note: This page sticks strictly to what appears in the retrieved Tehachapi Zoning Code files. Where the Code does not use the term “overlay,” I state that explicitly and point to the mechanisms the Code uses instead. Verify parcel-specific mapping with the City (see § 3.30.160 mapping) .
How Tehachapi handles “overlay-like” controls (district-by-district)
The Code’s mapped and site-specific tools you will encounter that function similarly to overlays are: Transect zones (T2–T5), Special Districts (SD) such as SD2.1, and Planned Development (PD). Below are district-level breakdowns (purpose, typical uses, key dimensional rules, where it applies) grounded in the Code.
SD2.1 — Tehachapi Boulevard West (Special District)
- Purpose: Applied to parcels along Tehachapi Boulevard between Downtown and Tucker Road to encourage regional and community-oriented lodging, retail and service uses that complement downtown character (§ 3.20.090) .
- Typical permitted uses: Mixed and single commercial uses (lodging, retail, service), with buildings shaping the corridor; refer to the SD2.1 land-use tables for permit types (P, CUP, MUP) in the SD2.1 table (§ 3.20.090) .
- Key dimensional standards: Buildings up to 3 stories; block-form buildings along the boulevard, house-form buildings on side streets; setbacks are those specified in the SD2.1 development standards (see § 3.20.090.C for standards) (§ 3.20.090) .
- Where it applies: Mapped along Tehachapi Boulevard; the district is shown on the Official Regulating Plan and applied to parcels along that corridor (§ 3.10.020; § 3.20.090) .
See the Code’s transect rules for facade, frontage, and parking placement that also apply in SD2.1 (general transect standards) (§ 3.20.010; § 5.10 series) .
Planned Development (PD) Zone
- Purpose: Allows a master/planned approach where departures from standard zoning can be granted when a cohesive master plan demonstrates public benefit and consistency with the General Plan (§ 3.30.160; 18.46.110) .
- Typical permitted uses: Determined by the approved Master Development Plan and precise development plans; PD may mix residential, commercial, civic, and open space as approved (permit types and limits are set in the Master/Precise plans) (§ 3.30.160; 18.46.110) .
- Key dimensional standards: The PD process controls site-specific setbacks, heights, densities and may allow departures from underlying standards when justified in the master plan; precise development plan approval is required before construction in an approved PD unit (§ 18.46.110; § 3.30.160) .
- Where it applies: Only where established by Council action and mapped on the Official Zoning Map (mapping requirement) (§ 3.30.160; 18.46.100) .
Transect Zones (examples) — these are base zones that include detailed form and use rules used across the town
T2 — Rural Edge (Rural)
- Purpose: Maintain low-intensity, rural edge character; supports agricultural and very limited development. See T2 for allowed building types, setbacks and open-space expectations (§ 3.20.030) .
- Uses: Agriculture, low-density residential, limited services (per Table 3.20.030), with many uses subject to permit requirements specified in the zone tables (§ 3.20.030) .
- Key standards: Buildings up to 2.5 stories; large front setbacks and rural placement rules (see Section C of the T2 standards) (§ 3.20.030) .
T3 — Neighborhood Edge; T4 — Neighborhood General; T4.5 — Neighborhood Center; T5 — Downtown
- Purpose & uses: Increasing intensity and urban form moving from T3 (neighborhood edge) to T5 (Downtown). Each transect zone lists permitted uses, building types, maximum stories/feet, facade placement, and parking rules; see the zone tables and the building type rules in Article 5 (§ 3.20.010; §§ 3.20.050–3.20.080; § 5.10 series) .
- Key dimensional examples: Maximum stories/feet vary by building type and transect (examples in the Code: Rowhouse/House forms up to 2–3 stories, facade-layer placement rules, and specific front/side/rear setback rules per building type) (§ 3.20.010; § 5.10.010) .
- Where they apply: Mapped on the Official Regulating Plan; transect allocations also used in master plans for larger sites (TND standards) (§ 3.20.020; Chapter 2.10) .
Decision-relevant summary table (quick reference)
| District / Tool | Typical permitted uses (decision-relevant) | Key dimensional standards (examples) | Code Reference |
|---|---|---|---|
| SD2.1 (Tehachapi Blvd West) | Lodging, regional retail, services; mixed-use allowed | Up to 3 stories; boulevard block-form; frontage/facade rules in SD2.1.C | § 3.20.090 |
| Planned Development (PD) | Site-specific mix determined by master plan; may include residential, commercial, civic | Standards set by Master/Precise plans; precise-plan required before construction | § 3.30.160; § 18.46.110 |
| T2 (Rural Edge) | Agriculture, low-intensity residential, limited services | Max 2.5 stories; large front setbacks and rural placement rules | § 3.20.030 |
| T4 (Neighborhood General) | Mixed residential, small-scale retail/service, townhouses | Building-type-specific heights (2–3 stories); facade placement rules | § 3.20.060; § 5.10 series |
Practical guidance and synthesis (plain-English, code-grounded)
- If you expect a traditional “overlay” (a thin layer of special rules that modifies an underlying zone), look first for a mapped Special District (like SD2.1) or a PD designation on the Official Regulating Plan: those are the Code’s mapped tools that modify or replace base-zone rules (§ 3.20.090; § 3.30.160) .
- For parcel-level exceptions or design-based departures, the Code relies on the Planned Development process and precise development plans rather than a generic “overlay” label; PD approval can allow departures from standard numeric limits when the master plan provides compensating public benefits (§ 18.46.110; § 3.30.160) .
- Use the Code’s building-type and facade rules (Article 5) and the transect tables for form-based controls (setbacks, facade layers, parking placement) — they are the primary way the Code controls “how” buildings sit on the lot rather than calling them overlays (§ 5.10 series; § 3.20.010) .
- Before preparing plans, confirm whether the parcel is mapped as SD2.1, PD, a transect zone, or subject to any other site-specific plan; mapping is decisive because the mapped district’s standards control the property (§ 3.30.160; § 3.10.020) .
Practical links you will want while preparing applications:
- Parking rules: see Tehachapi Parking and Chapter 4.50 references in the Code for parking standards (applies across zones) .
- Development standards and setbacks: see Tehachapi Development Standards and the transect/building-type sections in Article 5 (§ 5.10) .
- Design review / certificates: design and historic review occur under the Code’s certificate and review chapters — see Tehachapi Design Review and Certificates of Appropriateness (§ 9.20) .
- ADU rules are handled separately — see Tehachapi ADUs and statewide ADU law California ADU law for how accessory units interact with zoning.
- For nonconforming status or waivers: see Tehachapi Nonconforming Uses and the variance/exception procedures Tehachapi Variances and Exceptions.
(First occurrence of each of the above topic mentions includes the required internal link.)
Checklist (what an applicant must satisfy to use an “overlay-like” tool)
- Confirm the parcel’s mapped zone or district (Transect T2–T5, SD2.1, PD) on the Official Regulating Plan (§ 3.10.020; § 3.30.160) .
- Demonstrate consistency with the General Plan in the application and any master/precise development plan (required for PD or Master Development Plans) (§ 18.46.110; § 3.30.160) .
- Meet transect/form-based standards for façade placement, frontage, parking location and building type (Article 5 / Chapter 3.20) — or show how a PD/master plan compensates for departures (§ 5.10 series; § 3.20.010) .
- Provide required parking calculations and comply with Chapter 4.50 standards or secure an approved modification (see [Tehachapi Parking]) (§ 4.50; § 3.20 tables) .
- If in a historic or special review area, obtain applicable Certificates of Appropriateness or design-review approvals (Chapter 9.20) .
- Submit Landscape and screening plans complying with Chapter 4.40 and any SD/PD-specific landscape standards (Chapter 4.40) .
- If seeking deviations/waivers (for setbacks, heights, parking), use the PD process or variance processes and provide findings required by the Code (18.46 series; Chapter 9.90 for variances) .
Risks & Ambiguities
| Issue | Why it matters | What to verify |
|---|---|---|
| “Overlay districts” not named in code | The Code does not label “overlay districts”; relying on an assumed overlay may miss the correct mechanism (SD, PD, transect rules) | Verify whether the City has an adopted map or policy that it calls an overlay outside the published Zoning Code. Not found in retrieved materials; verify with City. |
| Parcel mapping (which tool applies?) | Whether a parcel is mapped SD2.1, PD, or a transect zone determines which standards control | Check the Official Regulating Plan / Zoning Map and any PD ordinances applying to the parcel (§ 3.30.160; 18.46.100) |
| Numeric standard conflicts (transect vs. non-transect) | The Code states which article controls in conflicts (Article 3 over Article 4, Article 6 over 3/4) — misreading can lead to wrong setback/height conclusions | When standards conflict, use the Code’s conflict rules and cite controlling section (§ 3.20.020) |
| Design review triggers | Some exterior changes require a Certificate of Appropriateness or Planning Commission review; failing to obtain review can delay projects | Verify whether the work triggers Chapter 9.20 (Certificates of Appropriateness) or other design-review provisions |
| PD/master-plan expectations | A PD can modify numeric standards, but must supply findings and precise plans; incomplete PD submittals will be denied | Confirm submission requirements and the precise plan timeline in § 18.46.110 and § 3.30.160 |
Plain-English Summary
Tehachapi does not have a generic “overlay district” label in the published Zoning Code. Instead, targeted site controls are implemented through mapped Special Districts (for example SD2.1 along Tehachapi Boulevard), transect-based form zones (T2–T5), and project-specific Planned Development approvals; check the Official Regulating Plan to see which of these applies to a parcel (§ 3.20.090; § 3.30.160; § 3.20.020) .
Source References
- Tehachapi Zoning Code — Transect zones, purpose and applicability, and conflict rules: § 3.20.010; § 3.20.020 (§ 3.20 series) .
- SD2.1 — Tehachapi Boulevard West: § 3.20.090 (intent, uses, and standards for SD2.1) .
- Planned Development (PD): § 3.30.160 (PD zone rules) and Precise Plan / Master Plan provisions § 18.46.110 (when required; approvals) .
- Building form and facade standards (Article 5 / building-type rules): § 5.10 series (facade, building-type placement, height) .
- Parking and parking placement references: Chapter 4.50 parking standards and parking tables in zone chapters (§ 4.50; zone tables) .
- Landscape and screening requirements: Chapter 4.40 (landscape standards) § 4.40.010–.050 .
- Certificates of Appropriateness / Design Review: Chapter 9.20 (applicability and review authority) .
- Zoning Code Table of Contents and adoption note (shows structure of zone/article numbering): Tehachapi Zoning Code front matter (Adopted October 2014; Revised September 2021) .
Sources
Retrieved passages
- Tehachapi Zoning Code (Chapter 4.50) High relevance
- Tehachapi Zoning Code (Chapter 3.30) High relevance
- Tehachapi Zoning Code (§ 3E) High relevance
- Tehachapi Zoning Code (§ 3E) High relevance
- Tehachapi Zoning Code (Chapter is) Medium relevance
- Tehachapi Zoning Code (§65597) Medium relevance
- Tehachapi Zoning Code (Chapter shall) Medium relevance
- Tehachapi Zoning Code (Chapter 2.10) Medium relevance
- Tehachapi Zoning Code (Chapter 3.20) Medium relevance
- Tehachapi Zoning Code (Section 3.3.min) Medium relevance
Cited sections
- Tehachapi Zoning Code — Transect zones, purpose and applicability, and conflict rules: § 3.20.010; § 3.20.020 (§ 3.20 series) . (§ 3.20.010)
- **SD2.1 — Tehachapi Boulevard West**: § 3.20.090 (intent, uses, and standards for SD2.1) . (§ 3.20.090)
- **Planned Development (PD)**: § 3.30.160 (PD zone rules) and Precise Plan / Master Plan provisions § 18.46.110 (when required; approvals) . (§ 3.30.160)
- Building form and facade standards (Article 5 / building-type rules): § 5.10 series (facade, building-type placement, height) . (Article 5)
- Parking and parking placement references: Chapter 4.50 parking standards and parking tables in zone chapters (§ 4.50; zone tables) . (Chapter 4.50)
- Landscape and screening requirements: Chapter 4.40 (landscape standards) § 4.40.010–.050 . (Chapter 4.40)
- Certificates of Appropriateness / Design Review: Chapter 9.20 (applicability and review authority) . (Chapter 9.20)
- Zoning Code Table of Contents and adoption note (shows structure of zone/article numbering): Tehachapi Zoning Code front matter (Adopted October 2014; Revised September 2021) . (article numbering)
- Tehachapi_ZoningCode.md
Frequently asked questions
Does Tehachapi have overlay districts?
No — the published Tehachapi Zoning Code does not use “overlay district” as a primary naming convention. The Code achieves overlay-like results through mapped Special Districts (e.g., SD2.1), transect zone form rules, and Planned Development approvals (§ 3.20.090; § 3.30.160; § 3.20.020) .
What is **SD2.1** and where does it apply?
SD2.1 is the Tehachapi Boulevard West Special District applied to parcels along Tehachapi Boulevard between Downtown and Tucker Road; it emphasizes boulevard-form buildings, mixed uses, and heights up to 3 stories per the SD2.1 rules (§ 3.20.090) .
Can a Planned Development change setbacks or heights that the base zone requires?
Yes — a Planned Development (PD) can allow departures from ordinary numeric standards when those departures are justified in the approved Master and Precise Development Plans; precise-plan approval is required before construction in a PD unit (§ 3.30.160; § 18.46.110) .
How do I know whether a parcel is in SD2.1, a transect zone, or a PD?
Check the City’s Official Regulating Plan / Zoning Map; the Code requires mapped PD boundaries and map-based zone designations control which standards apply (§ 3.30.160; § 3.10.020) .
Do transect zones control building form as well as uses?
Yes — Transect zones (T2–T5) specify building types, façade placement, frontage types, parking placement and permitted uses. They are form-based: read Article 5 (building-type standards) together with the zone tables (§ 3.20.010; § 5.10 series) .
If my project needs an exception or waiver, what process does the Code use?
Exceptions to numeric standards are typically handled through PD approvals or the variance procedures; the Code lays out the PD application/precise plan path and refers to variance processes in the appropriate chapters (PD: § 3.30.160 and § 18.46.110; variance rules in the Code’s permit/variance chapters) .
Do SD2.1 or transect rules change parking requirements?
Parking requirements remain tied to Chapter 4.50 and the zone tables, but the placement of parking (on-street vs. on-site, screened vs. visible) is controlled by transect and SD standards; check Chapter 4.50 and the SD/transect tables for the project location (§ 4.50; § 3.20 tables) .
Where are design review triggers described?
Design review and Certificates of Appropriateness are covered in Chapter 9.20; small modifications may be administratively approved while larger changes go to the Commission (§ 9.20.020–.040) .
More in Tehachapi code
Ask about any Tehachapi property
Get a cited, plain-English answer on Tehachapi zoning, setbacks, FAR, ADUs and permits — for any address.
Start Free Trial