My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
AgdaPkt 2010-06-07 clds, jnt
RedwoodCity
>
City Clerk
>
Agenda Packets
>
2010-2019
>
2010
>
AgdaPkt 2010-06-07 clds, jnt
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/8/2010 4:43:56 PM
Creation date
6/3/2010 3:07:58 PM
Metadata
Fields
Template:
CC Index
CC Index - Document Type
Agenda Packet
Meeting Type
Joint
Agency Type
City Council and Redevelopment Agency
Date
6/7/2010
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
145
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
<br />7A <br />Page 17 <br /> <br />This policy does not contain specific goals or guidelines for reductions in greenhouse gas emissions, <br />but considers cumulative air quality impacts overall. Since the project would conform to the applicable <br />land use General Plan policies and established consistency with past practice and existing <br />development form, the project would not conflict with this policy. Current Bay Area Air Quality <br />Management District (BAAQMD) CECA Guidelines recommend that the evaluation of a project's <br />cumulative impacts should be based on an analysis of the consistency of the project with the applicable <br />general plan, and the applicable general plan's consistency with the regional air quality plan. The City's <br />new 2030 General Plan, currently undergoing environmental review, will be consistent with the <br />BAAQMD Clean Air Plan. The new 2030 General Plan will have a threshold of significance for <br />assessing air quality impacts. <br /> <br />Furthermore, Section 15183 of the CECA Guidelines specifies that projects consistent with the land use <br />and development densities of a City's general plan which an environmental clearance was obtained do <br />not require additional CEQA review unless there are project-specific significant effects that are peculiar <br />to the project or its site. The proposed zoning ordinance amendment meets these criteria because the <br />increase is well within the permitted density for the R-2 district in the current General Plan, and there <br />are no project-specific significant effects that are peculiar to the project because the residential/and <br />uses proposed with the code amendment are already allowed per the existing zoning provisions. The <br />code amendment would permit a slight increase in density in the R-2 district (less than one-half of one <br />percent), which increase would be consistent with the City's existing practice for implementing the R-2 <br />zoning provisions, and any new development permitted by the project would be sUbject to compliance <br />with CEQA requirements. Therefore, any ensuing residential development that would occur with this <br />amendment would not conflict with City or region~wide goals for reducing greenhouse gas emissions. <br />Therefore, the project would not conflict with the provisions of AS 32. <br /> <br />Although the project itself would not result in any new development or construction, the slight increase <br />in residential construction that could ensue pursuant to the proposed R-2 amendment could generate <br />dust, exhaust, and similar particulates and emissions. As noted above, any such construction would be <br />preceded by the issuance of a PD Permit and accompanied by the requisite CECA compliance. In <br />addition, as a condition of any PO PermitJ the City would require the incorporation of standard dust <br />control and emission controls by the BAAQMD to ensure that any temporary air-quality impacts related <br />to additional residential construction will remain at a less-than-significant level. <br /> <br /> <br />Initial Study, R-2 Zoning District Code Amendment <br /> <br />111 <br />
The URL can be used to link to this page
Your browser does not support the video tag.