04.08.2013 Views

Fountaingrove Environmental Impact Report - City of Santa Rosa ...

Fountaingrove Environmental Impact Report - City of Santa Rosa ...

Fountaingrove Environmental Impact Report - City of Santa Rosa ...

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.

ES082008001BAO_<strong>Fountaingrove</strong>_publicComments_v3.indd_090408_lho<br />

MARGASON – 7<br />

MARGASON – 8<br />

MARGASON – 9<br />

MARGASON – 10<br />

Written Comments on Draft <strong>Environmental</strong> <strong>Impact</strong> report for the Lodge Project,<br />

page 3-92 but the extent <strong>of</strong> such soils is not yet defined hence the impact <strong>of</strong> such grading has not<br />

and cannot be addressed in the DEIR. This is unacceptable because the final extent <strong>of</strong> disturbance<br />

to the site topography hence environmental impact has not yet been determined. The EIR cannot<br />

defer the evaluation <strong>of</strong> such impacts until the design phase; they must be determined now by<br />

further on-site soils studies before a final EIR is completed.<br />

Section 3.6, pages 3-67 to 3-93, addresses geology and faulting and this section is one <strong>of</strong> the<br />

more extensive and responsive parts <strong>of</strong> the DEIR. Our 2A-1 thru 17 scoping comments in volume<br />

II apply as follows. Scope comments 2A1 thru 4 are addressed by the DEIR and according to<br />

Giblin and Associates no active fault was found by them on the lodge site, the nearest active trace<br />

<strong>of</strong> the Rogers Creek fault being across the street <strong>of</strong> TLH in the visible sag pond about 70 feet to<br />

the west. Bedrock faults were found on the site but Giblin dated them as pre-holocene hence they<br />

were rated as inactive. One would hope that no active faults were missed in non-trenched areas<br />

and Giblin should have to certify as to this in the final EIR..<br />

Page Three<br />

The DEIR does not appear to contain a map showing the locations <strong>of</strong> the Giblin fault trenches;<br />

this map is missing from his December 7, 2007 study, appendix K <strong>of</strong> vol. II, which curiously lists<br />

two plate 2’s. This seems to be an error and should be corrected in the EIR.<br />

Scope item 2A-5 was addressed as to very strong shaking from nearby 7+ magnitude<br />

earthquakes. The DEIR states that such hazards are significant and require mitigation. Mitigation<br />

impact 3.6-2 includes site-specific seismic analyses during design but does not specify if such<br />

analyses will include such details as response spectra, computer simulations and finite-element<br />

modeling all <strong>of</strong> which are needed in this near-fault setting. The EIR is not clear that its<br />

recommended mitigation <strong>of</strong> “site-specific seismic analyses in project design” goes well beyond<br />

normal building code seismic design. The EIR must indicate that code design alone is not<br />

sufficient for public safety at this site which is in the State <strong>of</strong> California’s designated Alquist-<br />

Priolo active fault zone. CEQA law does not allow this consideration to be deferred but must be<br />

included in the EIR.<br />

Site and soil stability during earthquakes has not been evaluated in the DEIR but instead is<br />

deferred to the design phase; also the seismic stability <strong>of</strong> the <strong>City</strong>-owned earth dams impounding<br />

<strong>Fountaingrove</strong> Lake has not been evaluated. Scoping items 2A6 thru 11 asked that these items be<br />

addressed in the DEIR but they are not. It is not clear that scoping items 2A14 and 15 were<br />

file:///C|/Documents%20and%20Settings/mgerut/My%20Documents/Fountain%20Grove/Comment_Letters/Margason.htm (3 <strong>of</strong> 4)8/1/2008 2:10:09 PM

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

Saved successfully!

Ooh no, something went wrong!