10.07.2015 Views

SFPUC 2001 Alameda Watershed Management Plan

SFPUC 2001 Alameda Watershed Management Plan

SFPUC 2001 Alameda Watershed Management 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.

I. SUMMARYlimits and mitigations set forth in <strong>Alameda</strong> County’s conditions of approval for SMP-32, and thatmining under SMP-32 would be consistent with their General <strong>Plan</strong>. In 1997, the findings wereupheld in Superior Court and on appeal by the Court of Appeal, after being challenged by a Sunolcitizens group. Upon re-examination in light of modifications to the timing and sequence ofmining and mining reclamation, and changed circumstances with respect to listed sensitivespecies, this EIR finds that, with additional mitigation measures identified in this EIR, therewould be no unavoidable significant impacts associated with mining north of I-680 beyond thatfound by <strong>Alameda</strong> County in the certified SMP-32 EIR and CEQA Findings (loss of 140 acres ofprime agricultural land). Many Sunol residents are expected to disagree.Another area of controversy involves the appropriate level of public access and use of the<strong>Watershed</strong> for recreational activities. Increased public access and use increases the risk of fire,water quality degradation, natural resource, and other impacts. The <strong>Management</strong> <strong>Plan</strong> attempts tobalance protection of the water supply with some increase in public access and use of the<strong>Watershed</strong>. Some persons will likely feel that the proposed amount of public access should beincreased. Other persons may feel that the proposed amount of public access is too great toensure maximum protection of the water supply and natural resources. This EIR analyzes theimpacts and suggests mitigation measures for the proposed level of public access and use, andanalyzes the impacts of alternatives calling for lesser and greater amounts of public access anduse.This is a program EIR that analyzes, at a general level, the potential environmental impacts of abroad range of policies and management actions proposed by the <strong>Alameda</strong> <strong>Watershed</strong><strong>Management</strong> <strong>Plan</strong>. For implementation of many proposed policies and management actions,their environmental effects are analyzed in sufficient detail to allow this EIR to fully satisfyCEQA. For example, the impacts of day-to-day management activities that implement the<strong>Management</strong> <strong>Plan</strong> are analyzed in this EIR and would generally not be subject to furtherenvironmental review. However, implementation of certain management actions could requirefurther environmental review at the time more specific projects are proposed. The San Francisco<strong>Plan</strong>ning Department would require examination of many specific management actions proposedin the <strong>Management</strong> <strong>Plan</strong> at the time they are proposed for implementation to determine if furtherenvironmental review at a more detailed project-specific and site-specific level were necessary.Generally, further environmental review would be necessary if new significant environmentaleffects beyond those identified in this EIR would occur as a result of changes in the project ornew circumstances or information, or if new mitigation measures or alternatives that wouldreduce one or more significant effects of the project are found to be feasible but <strong>SFPUC</strong> declinesto adopt the measure or alternative (CEQA Guidelines Section 15162). Table II-1 in the ProjectDescription chapter identifies the specific management actions that are likely to require furtherenvironmental review.NOP 96.223E: <strong>Alameda</strong> <strong>Watershed</strong> <strong>Management</strong> <strong>Plan</strong> I-10 ESA / 930385January <strong>2001</strong>

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

Saved successfully!

Ooh no, something went wrong!