My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
AgdaPkt 2012-07-09
RedwoodCity
>
City Clerk
>
Agenda Packets
>
2010-2019
>
2012
>
AgdaPkt 2012-07-09
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/10/2012 9:27:35 AM
Creation date
7/5/2012 4:54:48 PM
Metadata
Fields
Template:
CC Index
CC Index - Document Type
Agenda Packet
Meeting Type
Joint
Agency Type
City Council
Date
7/9/2012
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
657
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
8.A. - Page 275 <br /> Finger Ave.Project FEIR Comments <br /> June 15,2012 <br /> Page 4 of 12 <br /> 3. A map showing pervious/impervious surfaces both with and wifhoUt the <br /> praJect, which is essential to determining the adequacy of the runoff calculat3ons <br /> and associated reyuisite stormwater treatment facilities. <br /> 4. A description of the actual proposed Lot 3 erosion protection plan. This is <br /> essential to the�IR being adeyuate for CDFG's review of that plan, as well as far <br /> the public/decision-makers' review af potentiaY project impacts to CordiZleras <br /> Creek. <br /> 5. Figures 2.Q-1 and 2.0-2 should be expanded to show the acijacent residences, so it <br /> is possible to clearly see the relationship of the Project and adjacenf residences. <br /> This is required to understand the projeet's land use, aesthetic, and noise <br /> impacts. Also, these figures should be in Chapter 1, as they pertain to the project <br /> description. <br /> In response, the FEIR includes an unreadable "drainage plan" that fails to show <br /> stormwater treatment, capaciHes, pre- or post- project discharge rates into the creek, <br /> how the project would comply with LID requirements, and fails entire�y to provide <br /> house elevations, a map of surface permeability, the Lot 3 erosion protectian plan, or the <br /> project in the context of fhe adjacent residences. <br /> In response to my comment that the first bullet an p. 22 prohibits impervious surfaces <br /> within 15 feet af the top of bank and that the praposed 15-20 foot "no-build" easements <br /> do not appear to conform to the City's 25-foot sefback requirements the FETR (Response <br /> G-x7)goes off an a tangent and fails to respond to substance of the comment. <br /> TechnicaI Analysis Deficiencies <br /> I previously provided detailec� camrnents regarding technical deficiencies in the DEIIZ. <br /> AIthough some of our comrnents have been adequately addressed, a number of <br /> substantive c�eficiencies identified in our comments rernain. These are generally <br /> discussed belo�v. <br /> Responses G2� and G-22 <br /> These responses purport to address deficiencies in the EIR in describfng and assessing <br /> impacts on water yuality. The �oncern of the comments was t}►at the increased <br /> impervious surEaces, increased developmsnt, and increased traffic wauld increase both <br /> downstream flooding and the discharge of pollutants into the adjacent creek. In essence <br /> these responses claim that the project's stormwater system will 1) direct all potentially <br /> pollutea runoff to a detention and treatment system before discharge into the creek, and <br /> 2) the project won't increase peak runoff or pollution in the creek. The problem with <br /> these responses is that the EIR provides no evidence of the feasibility of adequate <br /> treatment. This is nat merely an academic issue — given the site's very high density of <br /> development, it is unclear that effective treatment of runoff af po�lutants frnm large <br /> areas of impervious surfaces through LID methods is actually feasib�e on the site, <br /> Simply stated, t�ere may not be room for treaiment and the EIR provides no evidence of <br /> its feasibility. <br />
The URL can be used to link to this page
Your browser does not support the video tag.