Local zoning · Arvin

Arvin — Landscaping and Screening

Landscaping and Screening under the Arvin local zoning and planning code, with the controlling citations.

Last reviewed: July 3, 2026

Overview

This page extracts and explains what the City of Arvin's zoning ordinance requires for landscaping and screening, including street trees, parking-lot planters, fences/walls, and screening of mechanical equipment and trash enclosures. The controlling rules are in the municipal zoning chapters (not in Title 24/state building code); where Arvin's code uses design-review or overlay rules those also affect landscaping (verify for specific parcels). Key rules live in § 17.70.010, § 17.50.090, and the parking/zone chapters cited below .

Linking note: this page mentions related topics that you will commonly need: see Arvin zoning & planning overview, Arvin Zoning, Arvin Development Standards, Arvin Parking, Arvin Design Review, Arvin Overlay Districts, and the California Building Standards Code for building-code issues that are outside this page.

What the ordinance requires (top-line rules)

  • Minimum landscape area: 10% of the developed area for commercial projects and many multi-family projects (landscape minimum) — § 17.70.010 .
  • Street trees: 1 deciduous canopy tree per 40 ft of street frontage (or fraction thereof); trees may be clustered and can be placed in parkways, tree wells, or front-yard setback where utilities interfere — § 17.70.010 .
  • Parking-edge planting: where parking fronts streets or abuts residential, provide a landscaped strip at least 5 ft wide plus screening at least 3 ft high and ≥50% opaque — see § 17.70.010 and the MUO guidance .
  • Screening where required: minimum 3 ft height; acceptable methods include a decorative fence behind landscaping, a masonry wall behind landscaping, or planted hedges — noted in multiple site-development and MUO provisions (see § 17.70.010 and MUO language) .
  • Fence/wall/hedge height limits in residential zones: rear/side yards up to 6 ft, front yards up to 4 ft, with special rules for reverse-corner lots and prohibition on barbed wire in R/E zones — § 17.50.090 .
  • Parking-lot planters: perimeter landscaping and planters for every 5th or 6th parking space; planters must include automatic irrigation and live plants; hardscape may be up to 10% of required planter area — § 17.70.010 .
  • Trash enclosures and mechanical equipment must be screened from public view and integrated with building design; trash enclosures may not be in required setbacks — § references in site development and multi-family standards .
  • Where commercial/industrial parking abuts R or E zones, a solid masonry wall 6 ft high is required for separation (with lower height near the front property line) — § 17.48.080 .
  • Separating walls: the code expressly permits the city to require a separating wall to attenuate noise and screen conflicting uses — see site development provisions .

All of the standards above are taken from Arvin Municipal Code chapters on site development, parking, fences/walls, and overlay districts; see the Source References at the end for the controlling sections and file citations.

District-by-district breakdown

Below are the Arvin zoning districts that matter for landscaping/screening. Each subsection summarizes the district purpose, typical uses relevant to landscaping, any specific landscaping/screening directions in the ordinance, and where the rules apply.

Note: the municipal code establishes the list of zones in § 17.06.010; use that as the baseline for district names and to find an individual parcel's zone on the official zoning map .

R-1 — Single‑family dwelling zone

  • Purpose & typical uses: single-family homes, accessory uses; administered under the R chapters (see R-1 rules) .
  • Landscaping/screening specifics: front-yard fence/wall/hedge height caps (4 ft front; 6 ft side/rear) apply to R‑1 as listed in § 17.50.090 (so homeowners and developers must design fences to those maxima) .
  • Where it applies: all R‑1 parcels citywide per the zoning map; tree/planter requirements in the site development standards still apply to projects requiring permits (see § 17.70.010) .

R-2 / R-3 / R-4 — Two‑family / limited multi‑family / multiple‑family zones

  • Purpose & typical uses: duplexes, garden apartments, apartment houses; R-2/R-3/R-4 have their own setback/height rules (for example, R‑2 front yard 15 ft in § 17.10.040, R‑4 front yard 10 ft in § 17.14.040) that affect landscaping placement and screening of outdoor areas .
  • Landscaping/screening specifics: multi‑family and mixed‑use projects are subject to objective multiple-family design review rules; landscaped area minimums, planter spacing, street trees, and irrigation requirements are enforced (minimum 10% landscaped area and planter/tree spacing; planters every sixth parking space; trees every 30 ft along interior property lines abutting residential lots where applicable) — see § 17.70.010 and the multiple-family design review chapters § 17.72 and ministerial review § 17.055 .
  • Where it applies: R-2/3/4 parcels and mixed-use projects; projects that trigger the objective design review must submit a precise landscaping and irrigation plan (see specific submittal requirements under the design review chapters) .

N‑C / C‑O / C‑1 / C‑2 — Neighborhood & professional commercial zones

  • Purpose & typical uses: neighborhood shops, professional offices, general commercial activity (see the C‑O and N‑C chapters for permitted uses) .
  • Landscaping/screening specifics: commercial projects must meet site development landscape standards (minimum 10% landscaped area; street trees; parking-lot planters and perimeter landscaping; irrigation) — § 17.70.010. In certain downtown or central-business areas, central‑business chapter rules may adjust landscaping/parking requirements; verify if a parcel is inside the Bear Mountain central business district (these local overrides are in Chapter 17.68) .
  • Where it applies: all commercially zoned parcels, except where a specialized chapter (e.g., central business district) modifies the requirement — check the zoning map and Chapter 17.68 for downtown exceptions .

M‑1 / M‑2 / M‑3 — Manufacturing / industrial zones

  • Purpose & typical uses: light manufacturing, processing, industrial uses (see Chapter listings) .
  • Landscaping/screening specifics: where industrial or commercial parking abuts residential zones the code requires a solid masonry wall 6 ft high (see § 17.48.080(A–B)) and the general site-development standards and screening rules apply to buffers, landscaping, and trash/mechanical screening; oil/gas sites have additional landscaping/wall rules under the oil/gas chapter § 17.46 (e.g., 6 ft wall and 25 ft setback for oil/gas sites) .
  • Where it applies: industrial campuses and manufacturing parcels; CUPs for industrial uses commonly require detailed screening/landscaping plans.

PF — Public Facility zone

  • Purpose & typical uses: civic buildings, libraries, public utilities, parking, corporation yards (see § 17.38.010–.040) .
  • Landscaping/screening specifics: PF developments are subject to site-development and design-review findings that require "ample landscaping and screening" as a finding for approval; follow § 17.38.070 and § 17.70.010 for plant/irrigation rules .
  • Where it applies: publicly owned parcels and facilities.

SZ — School zone

  • Purpose & typical uses: schools, student housing, athletic facilities; specifics in § 17.42.010–.050 .
  • Landscaping/screening specifics: development standards and findings require "ample landscaping and screening" to preserve compatibility with surrounding development; design and frontage improvements may include street trees and landscape strips per § 17.70.010 .
  • Where it applies: school-owned parcels and adjacent lands as mapped.

PUD and MUO (overlay) — Planned Unit Development & Mixed‑Use Overlay

  • PUD (Chapter 17.45): PUD approvals typically require a master development plan that must include a precise landscaping, planting and irrigation plan; the planning commission may set higher open-space/landscape standards than base zones (see § 17.45.150 and § 17.45.030(D–E)) .
  • MUO (Chapter 17.43): The pedestrian‑oriented Mixed‑Use Overlay applies additional site/layout and landscaping guidance in target areas (Jewett Square, South Arvin, etc.); the overlay calls out landscaping/screening measures for parking, sidewalks, and street trees in overlay target areas and defers to the underlying zone where silent — see § 17.43.010 and the overlay text for the MUO target-area standards .
  • Where it applies: PUD and MUO apply only where mapped on the official zoning map; PUD requires master and specific development plans with full landscape plans; MUO adds overlay requirements to the underlying zone.

Quick reference table — most decision‑relevant standards

Topic Requirement (Arvin) Code reference
Minimum landscaped area (commercial/projects) 10% of developed area § 17.70.010
Street trees 1 canopy tree / 40 ft of frontage (or fraction) § 17.70.010
Parking-edge landscaping 5 ft landscaped strip + 3 ft screening, ≥50% opaque § 17.70.010
Parking-lot planters One planter every 5th/6th parking space; irrigation required § 17.70.010
Fence/wall heights (residential zones) Front 4 ft; Side/Rear 6 ft (R & E zones) § 17.50.090
Industrial/Commercial adj. to R/E Masonry wall 6 ft required where parking abuts R/E § 17.48.080
Screening of mechanical & trash Must be screened/architecturally integrated; trash enclosures not in setbacks Site development standards, multiple-family design review § 17.70.010, § 17.055

Practical guidance (plain-English application tips)

  • Always submit a full landscape/irrigation plan when you file for site development, multi‑family design review, PUD, or a CUP; the code requires a precise landscaping and irrigation plan for specific development approvals (see § 17.45.150 and chapter 17.055 design-review submittal lists) .
  • Use the city’s approved plant list for species selection and design planters as living, irrigated areas (automatic irrigation required) — § 17.70.010 .
  • If you plan street trees but utilities conflict, Arvin explicitly allows planting in the front-yard setback adjacent to the sidewalk instead of the right-of-way — § 17.70.010 .
  • If your project’s parking lot sits beside residential zoning, expect a masonry wall and/or dense planting; design the wall behind a planted strip where possible to meet both the masonry and the screening/landscaping intent — § 17.48.080 and site standards .
  • For multi‑family or mixed‑use projects, the planning staff will check plant spacing (trees every 30 ft along interior lines where applicable) and planter frequency during plan review — § 17.72.030 and § 17.70.010 .

Checklist — what an applicant must submit / satisfy (site-level)

  • Provide a scaled landscape plan showing planted areas, street trees, planters, and irrigation (required in PUD/specific development and multiple‑family submittals) — § 17.45.150, § 17.055.020 .
  • Show that ≥10% of developed area is landscaped where applicable (commercial and many multi‑family projects) — § 17.70.010 .
  • Street-tree plan: show 1 tree per 40 ft of frontage (or equivalent) and proposed location relative to utilities/curb — § 17.70.010 .
  • Parking-lot landscaping: planters at required frequency (5th/6th stall), 5 ft planter strips along streets, screening 3 ft high and ≥50% opaque where parking fronts streets or abuts residential — § 17.70.010 .
  • Fences/walls: show height and materials; conform to 4 ft front / 6 ft side & rear rules in R/E zones or document requested modifications — § 17.50.090 .
  • Trash enclosures and mechanical equipment: show screening, location outside required setbacks, and architectural integration — site-development and multi‑family rules § 17.70.010, § 17.055 .
  • Plant palette: reference to City’s approved plant list maintained by Planning & Building; irrigation details for automatic irrigation systems — § 17.70.010 .
  • For projects abutting residential zones, show tree spacing along interior property lines (trees at least every 30 ft in individual planters where required) — § 17.70.010 and multiple-family standards .

Risks & Ambiguities

Issue Why it matters What to verify
Fence/wall heights on corner or reverse‑corner lots Reverse‑corner rules adjust allowed fence height within 25 ft of the rear line — can affect visibility and compliance Confirm the lot type and apply § 17.50.090(C) limits; verify with the City planner (parcel-specific)
Whether a separating wall is required Code allows the City to require walls for noise attenuation/screening (discretionary) Check site‑specific findings and permit conditions (site development/PUD/CUP); see site-development language about separating walls
Street tree placement vs. utilities Utilities in the ROW may prevent tree planting there Code allows trees in the front-yard setback adjacent to sidewalk where utilities block right‑of‑way planting — confirm with Public Works/Utilities and cite § 17.70.010
Which chapter governs (overlay vs underlying zone) For overlay areas (MUO), overlay rules may override the underlying zone Check if the property is in MUO; overlay § 17.43.010 explains the relationship — verify mapped overlays on the zoning map
Plant species approval / drought rules The code requires use of an approved plant list; water‑use and irrigation design affect approval Use the Planning & Building approved list and show automatic irrigation; if not found in submitted docs, Planning can reject — § 17.70.010
Oil & gas site special walls Oil/gas operations have 6 ft wall and 25 ft setbacks and special landscaping requirements that exceed usual rules For oil/gas sites refer to § 17.46.025.2 and related CUP requirements; verify with Planning and CUP conditions

Plain‑English Summary

Arvin requires most commercial, multi‑family, and many redevelopment projects to provide thoughtfully sized planted areas (commonly 10% of developed area), street trees (1 per 40 ft), parking‑lot planters and a landscaped 5‑ft edge where parking fronts streets, and screening (minimum 3 ft) for parking, trash, and mechanical equipment; residential fence heights are capped at 4 ft (front) and 6 ft (side/rear). These rules are enforced through site development review, design review, PUD/CUPs and the zone chapters — verify parcel overlays and the Planning Department’s approved plant list when you prepare plans .

Source References

  • § 17.70.010 — Site development standards; Landscape standards (10% minimum, street trees, planters, irrigation, screening).
  • § 17.50.090 — Fence, wall and hedge regulations (height limits in R and E zones).
  • § 17.48.080 — Parking/parking‑area fence requirements (masonry wall 6 ft where parking abuts R/E).
  • § 17.06.010 — Zones established (list of Arvin zone names: R‑1, R‑2, R‑3, R‑4, N‑C, C‑O, C‑1, C‑2, M‑1, M‑2, M‑3, A‑1, A‑2, OS, PF, SZ, PUD, MUO, etc.)
  • § 17.43.010 — MUO (pedestrian‑oriented mixed‑use overlay) applicability and additional landscaping/screening guidance for MUO target areas.
  • § 17.45.150 — PUD specific development plan must include a precise landscaping, planting and irrigation plan.
  • Chapter 17.055 / § 17.055.020 — Multiple‑family residential design review ministerial submittal requirements (landscape plans required for multi‑family projects).
  • § 17.46.025.2 — Oil and gas site walls/landscaping requirements (6 ft walls; 25 ft setback).

Sources

Retrieved passages

  • Arvin Zoning Code High relevance
  • Arvin Zoning Code (Chapter 17.48) High relevance
  • CWUIC § 65850.6 (Title 24) High relevance
  • Arvin Zoning Code (§ 10) High relevance
  • Arvin Zoning Code High relevance
  • CFC § 17.70.010 (section 17.70.010) High relevance
  • Arvin Zoning Code (chapter for) High relevance
  • Arvin Zoning Code (§ 11) High relevance
  • CBC § 2917 (section 17.50.040) Medium relevance
  • Arvin Zoning Code (§ 11) Medium relevance
  • Arvin Zoning Code (Chapter 17.44) Medium relevance
  • CBC § 6 (§ 6) Medium relevance
  • Arvin Zoning Code (§ 15) Medium relevance
  • Arvin Zoning Code (§2) Medium relevance
  • Arvin Zoning Code (Chapter 17.48) Medium relevance
  • Arvin Zoning Code (section 17.70.010) High relevance
  • Arvin Zoning Code (section 17.05.080) High relevance
  • Arvin Zoning Code (Chapter 13.08) High relevance
  • CFC § 3 (§ 3) Medium relevance
  • Arvin Zoning Code (§2) Medium relevance
  • Arvin Zoning Code (§2918) Medium relevance
  • Arvin Zoning Code (Title 17) Medium relevance
  • Arvin Zoning Code (chapter 17.70) Medium relevance
  • Arvin Zoning Code Medium relevance
  • Arvin Zoning Code (Section 17.46.32.1) Medium relevance
  • California Residential Code Medium relevance
  • California Residential Code Medium relevance
  • California Residential Code Medium relevance
  • California Residential Code Medium relevance

Cited sections

Frequently asked questions

What landscaping rules apply to a small retail lot in Arvin?

Small commercial development must follow the site development landscape standards: show 10% landscape area, street trees at 1 per 40 ft frontage, perimeter planting where parking fronts a street (5 ft strip) and planters in parking per § 17.70.010; downtown central‑business exceptions may change requirements — verify Chapter 17.70.010 and Chapter 17.68 for downtown parcels .

How tall can my backyard fence be in an Arvin R‑1 zone?

In R‑1 (and other R/E zones) a fence or wall in the rear or side yard may be up to 6 ft, while fences located in the required front yard may not exceed 4 ft; there are special rules for reverse‑corner lots — see § 17.50.090 .

Do I have to plant street trees for a new subdivision or frontage improvement?

Yes — the code requires one deciduous canopy street tree per 40 ft of street frontage (or fraction thereof) for projects adjacent to designated streets and allows cluster planting or placement in front-yard setback if utilities prevent ROW planting; show trees on the landscape plan — § 17.70.010 .

What screening is required between a commercial parking lot and adjacent homes?

When parking fronts public streets or abuts residential uses you must provide a landscaped area at least 5 ft wide and screening at least 3 ft high and at least 50% opaque; where parking abuts R/E zones a masonry wall 6 ft high may be required — see § 17.70.010 and § 17.48.080 .

Must trash enclosures be screened and where can they be located?

Yes. Trash enclosures must be screened and architecturally integrated with the primary building, and they may not be located in required setbacks or open space; show location and screening method on plans for review — site development and multiple‑family review detail this requirement § 17.70.010 and related chapters .

If my parcel is in the MUO overlay, which landscaping rules control?

The MUO overlay adds requirements to the underlying zone and may itself include specific landscaping/screening standards for MUO target areas; in a conflict the MUO provisions prevail — check § 17.43.010 and the MUO chapter text plus the underlying zone rules (and the site development standards) to compile applicable requirements .

Can I use artificial turf or rock in required planters?

Ornamental rock, artificial turf and other artificial materials count as hardscape; the code limits hard surface area inside required planters to 10% of the required planter area — show calculations on the landscape plan per § 17.70.010 .

Will the city require a masonry wall between an industrial site and homes?

Yes — where industrial or commercial parking areas abut property classified R or E, the code requires separation by a solid masonry wall 6 ft high (with adjustments near frontage) — see § 17.48.080 .

For multi‑family projects, how often must I show trees along interior property lines adjacent to residential lots?

For multi‑family and many larger developments the code requires trees planted at least every 30 ft in individual planters along any interior property line abutting residentially zoned lots; planters must be large enough to prevent parked cars from intruding into the planting area — § 17.70.010 and multiple‑family design review sections .

Who enforces the approved plant list and irrigation requirements?

The Department of Planning & Building enforces plant selection and irrigation design at plan check and prior to issuance of building permits and certificates of occupancy; the code requires landscaping materials to be selected from the approved plant list and automatic irrigation in planters — § 17.70.010 .

More in Arvin code

Ask about any Arvin property

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

Start Free Trial

More Arvin zoning topics