27.12.2014 Views

A Management Strategy for Oneida Lake and its ... - CNY RPDB Home

A Management Strategy for Oneida Lake and its ... - CNY RPDB Home

A Management Strategy for Oneida Lake and its ... - CNY RPDB Home

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix A: Flooding <strong>and</strong> Water Level <strong>Management</strong><br />

The Flooding <strong>and</strong> Water Level <strong>Management</strong> Working Group met on a regular basis <strong>for</strong> a twelvemonth<br />

period during 2003 <strong>and</strong> 2004. Special emphasis was placed on research <strong>and</strong> education <strong>and</strong><br />

several guest speakers were invited to present at the meetings. The following in<strong>for</strong>mation was<br />

compiled by the Working Group members <strong>and</strong> most agreed with the contents of these documents.<br />

Full group endorsement was not reached, however, as several people did not agree with<br />

the in<strong>for</strong>mation presented or with the manner in which historical data was interpreted.<br />

Process<br />

Organizations, businesses, <strong>and</strong> homeowners<br />

throughout the watershed have expressed<br />

many differing opinions regarding flooding<br />

<strong>and</strong> water level management. The Flooding<br />

<strong>and</strong> Water Level <strong>Management</strong> (F/WLM)<br />

Working Group was comprised of a diverse<br />

collection of representatives that met on a<br />

monthly basis <strong>for</strong> approximately 12 months<br />

with the assistance of a meeting facilitator<br />

from Cornell University.<br />

Education was identified as an integral<br />

component of the Working Group process <strong>and</strong><br />

a considerable amount of time was there<strong>for</strong>e<br />

spent reviewing documents <strong>and</strong> hearing<br />

presentations from guest speakers. Education<br />

<strong>and</strong> outreach ideas <strong>for</strong> homeowners, elected<br />

officials, <strong>and</strong> other primary stakeholders are<br />

emphasized in the list of recommendations.<br />

Throughout the duration of this period, the<br />

Working Group agreed on several important<br />

points:<br />

- A specific timeline was established <strong>for</strong><br />

compiling the recommendations;<br />

- Several important issues relating to flooding<br />

<strong>and</strong> water level management were determined<br />

to be beyond the scope of the Working Group<br />

because of time restrictions, inadequate<br />

availability of in<strong>for</strong>mation, conflicting opinions,<br />

<strong>and</strong>/or because the appropriate stakeholders<br />

were not participating in the discussions.<br />

This includes the following topics:<br />

downstream (beyond the watershed boundary)<br />

issues, upstream water storage <strong>and</strong> flooding,<br />

dam remnants removal, dredging of the<br />

shoals, interpretation of several technical<br />

reports, rulings from recent law suites, water<br />

level regulation by hydropower companies on<br />

the Oswego River, <strong>and</strong> GIS mapping of flood<br />

prone areas;<br />

- Although upstream <strong>and</strong> downstream impacts<br />

were considered <strong>and</strong> recognized to be potentially<br />

relevant factors, the current priority was<br />

to develop recommendations to address only<br />

flooding <strong>and</strong> water level management along<br />

the <strong>Oneida</strong> <strong>Lake</strong> shoreline;<br />

- Effective surface water management is a<br />

regional issue <strong>and</strong> decisions to alleviate<br />

flooding in the <strong>Oneida</strong> <strong>Lake</strong> watershed require<br />

regional partnerships with lake communities<br />

throughout the Oswego River<br />

Basin.<br />

page 86<br />

Appendices

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

Saved successfully!

Ooh no, something went wrong!