My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Open Space Advisory Board Agenda and Packet 2012 08 08
PORTAL
>
BOARDS COMMISSIONS COMMITTEES RECORDS (20.000)
>
OPEN SPACE ADVISORY BOARD
>
2000-2019 Open Space Advisory Board Agendas and Packets
>
2012 Open Space Advisory Board Agendas and Packets
>
Open Space Advisory Board Agenda and Packet 2012 08 08
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/11/2021 8:21:23 AM
Creation date
8/23/2012 11:03:53 AM
Metadata
Fields
Template:
City Council Records
Doc Type
Boards Commissions Committees Records
Supplemental fields
Test
OSABPKT 2012 08 08
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
122
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
• The native vegetative communities recommended in this plan evolved over <br />thousands of years based on a snowmelt hydroperiod. They should respond <br />well to a plan that creates similar hydrological conditions. <br />• There will be some years that the reservoir will not be able to be filled to its <br />maximum level; our approach using a natural hydroperiod will create <br />vegetation zones that will have the resiliency to withstand such drought <br />years, especially when compared to a vegetation plan that depends on a <br />completely full reservoir. <br />• Once vegetation is well established, larger drawdowns can be made every <br />few years, as necessary, to help manage undesirable invasive species, such as <br />bullfrogs or excessive cattails, or to perform other maintenance activities <br />that may arise. <br />Some important general guidelines are as follows: <br />• These water levels, the recommended vegetation zones, and the <br />recommended grading are all dependent on one another. <br />• Our recommendations are based on the rehabilitated reservoir elevations <br />and size shown in the 80% draft plan set and assume that the reservoir can <br />have water year round. <br />• Water management during the first couple of years after implementation of <br />the plan will likely differ from these water management recommendations. It <br />will be important to maintain relatively steady water levels to allow the <br />plants to become well established. As a result, the City will probably need to <br />avoid the maximum and minimum water levels during this time. <br />• We do recommend some variation in the timing of water levels from year -to- <br />year; it should not be exactly the same every year. <br />• We recommend that the City monitor the site and adaptively manage water <br />levels depending on the response of the vegetation and water quality. It is <br />difficult to predict the vegetative response and water quality impacts to a <br />high degree of accuracy. <br />• During the hot summer months, the City should allow equal amounts of <br />inflow and outflow to improve water quality in the reservoir. The exact <br />amount of inflow /outflow would be determined after observing water <br />quality parameters for a period of time following the commencement of <br />reservoir operation. <br />• Whenever the City adjusts the water level, it should be done slowly. Rapid <br />changes are an unnatural condition and will likely overstress the vegetation. <br />Figure 5 shows a draft conceptual cross section of the proposed water levels, <br />grading of the reservoir side slopes, and corresponding plant communities. The <br />water level management plan is to fill the reservoir to its maximum level of 5340 <br />feet a couple of times in the spring, depending on growing conditions for that <br />particular year. The first flooding, which is optional, would occur around late April <br />to early May, and the second flooding would occur around late May to early June to <br />
The URL can be used to link to this page
Your browser does not support the video tag.