09.01.2015 Views

Environmental Impact Statement - Sonoma Land Trust

Environmental Impact Statement - Sonoma Land Trust

Environmental Impact Statement - Sonoma Land Trust

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.

<strong>Sonoma</strong> <strong>Land</strong> <strong>Trust</strong><br />

Chapter 4. Consultation and Other Requirements<br />

Hazardous Substances and Waste<br />

The restoration alternatives would involve excavation of 12,000 cubic yards of<br />

contaminated soil from the sports club to be used as fill material for up to 6,000<br />

linear feet of the core of thenew flood control levee to be located south of the<br />

SMART rail line. As part of this design, a minimum of three feet of clean cover<br />

material is recommendedwould be placed to surround the levee corecontaminated<br />

soil to prevent environmental exposure of the core material. Core<br />

leveecontaminants. Levee construction and periodic post-construction levee<br />

maintenance would adhere to the construction protocols and administrative<br />

controls identified in Chapter 3.9, Hazardous Substances and Waste, and would<br />

therefore decrease the potential for future disturbance of contaminated soil.<br />

The restoration alternatives would not exacerbate or cumulatively contribute to<br />

hazardous materials impacts from other cumulative projects. Prior to<br />

commencement of construction activities, the lead agencies would conduct or<br />

supervise proper cleanup activities of any potential hazardous substances and/or<br />

waste at the project site in compliance with local, state, and federal regulations.<br />

Because these cleanup activities would remediate potentially contaminated media<br />

to levels suitable for wetland use, the project is not expected to contribute<br />

considerably to a cumulative significant impact related to hazardous substances<br />

and waste.<br />

As discussed in Section 3.9, Hazardous Substances and Waste, both of the<br />

restoration alternatives would only use dredged sediment material that is found<br />

suitable by the DMMO for use as cover materialat the project site. Therefore,<br />

neither is expected to contribute considerably to an increased risk of exposure to<br />

potentially contaminated sedimentTherefore, the contribution of the Proposed<br />

Project to potential cumulative impacts from increased risk of exposure to<br />

potentially contaminated sediment would be less than significant.<br />

The Proposed Project requires the demolition of several older buildings, and<br />

some other restoration projects may also require building demolition. Potential<br />

releases of asbestos-containing materials and lead-based paint during demolition<br />

of older structures would be controlled through the use of appropriate demolition<br />

procedures, as required by law. Compliance with legally mandated demolition<br />

procedures would preclude a cumulatively significant contribution to hazards<br />

associated with releases of asbestos-containing materials and lead.<br />

Potential increases in methylation of mercury due to wetland processes was<br />

discussed above under Water Quality.<br />

Traffic and Transportation, Air Quality, and Noise<br />

Construction traffic would represent a short-term minor increase in traffic that<br />

would contribute to traffic congestion on roadways in the project vicinity. As a<br />

worst case, site grading, core levee construction, and building demolition<br />

activities could be implemented simultaneously during the site preparation phase,<br />

Sears Point Wetland and Watershed Restoration<br />

Project Final <strong>Environmental</strong> <strong>Impact</strong><br />

Report/<strong>Environmental</strong> <strong>Impact</strong> <strong>Statement</strong><br />

4-16<br />

April 2012

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

Saved successfully!

Ooh no, something went wrong!