22.02.2013 Views

Yuba County Airport Land Use Compatibility Plan

Yuba County Airport Land Use Compatibility Plan

Yuba County Airport Land Use Compatibility Plan

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

CHAPTER 2 POLICIES<br />

(a) For projects that are solely residential, the acreage evaluated equals the project site size<br />

which may include multiple parcels. See Policy 3.2.9 with regard to mixed-use development.<br />

(b) The maximum allowable residential densities indicated in Table 2 are intended to include<br />

density bonuses and any other bonuses or allowances that local agencies may<br />

provide for affordable housing developed in accordance with the provisions of state<br />

and/or local law or regulation. The overall density of a development project, including<br />

any bonuses or allowances, must comply with the allowable density criteria in Table<br />

2.<br />

(c) Secondary units, as defined by state law, shall be excluded from density calculations.<br />

(d) See Policy 4.1.4 regarding residential development by right on existing legal lots of<br />

record.<br />

(e) In accordance with state law, a family day care home serving 14 or fewer children may<br />

be established in any existing dwelling or in any new dwelling permitted by the policies<br />

of this <strong>Compatibility</strong> <strong>Plan</strong>.<br />

(f) See Policy 3.2.10(a) for limitations on clustering of development within a single acre<br />

and Policy 4.1.1 for infill criteria.<br />

3.2.7. Nonresidential Development Criteria: The usage intensity (people per acre) limit indicated in<br />

Table 2 for each safety zone is the fundamental criterion against which the safety compatibility<br />

of most nonresidential land uses shall be measured. Other criteria may be applicable<br />

to uses of special concern (see Policy 3.2.8).<br />

(a) For the purposes of assessing compliance with the usage intensity criteria:<br />

(1) ―Normally compatible‖ means that the land use is presumed to comply with the<br />

indicated limits for the zone. However, atypical examples of a use may require<br />

review to ensure compliance with the criteria.<br />

(2) ―Conditional‖ means that proposed development involving the land use must<br />

comply with the conditions listed in the table.<br />

(3) ―Incompatible‖ means that proposed development involving the land use should<br />

not be permitted under any circumstances within the indicated safety zone.<br />

(b) Local agencies may make exceptions for ―conditional‖ or ―incompatible‖ land uses associated<br />

with rare special events (e.g., an air show at the airport) for which a facility is<br />

not designed and normally not used and for which extra safety precautions can be taken<br />

as appropriate.<br />

(c) Where a floor area ratio (FAR) limit is cited in Table 2 as the condition to be met, the<br />

indicated numbers should be treated as a tool by which compliance with the usage intensity<br />

criteria can be evaluated. The limit listed for each use is based upon a typical<br />

occupancy load factor (floor area square footage per person) for that use. The allowable<br />

FAR in a particular safety zone thus varies from one land use to another. The assumed<br />

occupancy levels are shown in the table. If a higher or lower occupancy load<br />

factor can be documented for a particular project (see Paragraph (4) below), then the<br />

allowable FAR would be correspondingly higher or lower, but in all cases the basic usage<br />

intensity criterion must be met. The following factors shall be taken into account<br />

when calculating the FAR of a proposed development:<br />

2–20 <strong>Yuba</strong> <strong>County</strong> <strong>Airport</strong> <strong>Land</strong> <strong>Use</strong> <strong>Compatibility</strong> <strong>Plan</strong> (September 2010 Draft)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!