My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Stream: West Fork SF of Slater Creek (Upper Segement) Executive Summary
CWCB
>
Water Supply Protection
>
DayForward
>
6001-7000
>
Stream: West Fork SF of Slater Creek (Upper Segement) Executive Summary
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/5/2012 2:20:18 PM
Creation date
9/5/2012 2:01:32 PM
Metadata
Fields
Template:
Water Supply Protection
Description
Stream: West Fork SF of Slater Creek (Upper Segement) Executive Summary
State
CO
Water Division
6
Title
Stream: West Fork SF of Slater Creek (Upper Segement) Executive Summary
Water Supply Pro - Doc Type
Report/Study
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
10
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
Biological Data <br />In July and September of 2009 TU and CDOW collected stream cross sectional data, natural <br />environment data, and other data needed to quantify instream flow needs. Previously survey data <br />collected by CROW indicated the stream supports healthy populations of Colorado River <br />cutthroat trout. <br />Field Survey Data <br />TU and CROW staff used the R2Cross methodology to quantify the amount of water required to <br />preserve the natural environment to a reasonable degree. The R2Cross method requires that <br />stream discharge and channel profile data be collected in a riffle stream habitat type. Riffles are <br />most easily visualized, as the stream habitat types that would dry up first should streamflow <br />cease. This type of hydraulic data collection consists of setting up a transect, surveying the <br />stream channel geometry, and measuring the stream discharge. <br />Biological Flow Recommendation <br />The CWCB staff relied upon the biological expertise of the cooperating agencies to interpret <br />output from the R2Cross data collected to develop the initial, biologic instream flow <br />recommendation. This initial recommendation is designed to address the unique biologic <br />requirements of each stream without regard to water availability. Three instream flow hydraulic <br />parameters, average depth, percent wetted perimeter, and average velocity are used to develop <br />biologic instream flow recommendations. The CDOW has determined that maintaining these <br />three hydraulic parameters at adequate levels across riffle habitat types, aquatic habitat in pools <br />and runs will also be maintained for most life stages of fish and aquatic invertebrates (Nehring <br />1979; Espegren 1996). <br />For this segment of stream, two data sets were collected with the results shown in Table 1 below. <br />Table 1 shows who collected the data (Party), the date the data was collected (Date), the <br />measured discharge at the time of the survey (Q), the accuracy range of the predicted flows <br />based on Manning's Equation (240% and 40% of Q), the summer flow recommendation based <br />on meeting 3 of 3 hydraulic criteria and the winter flow recommendation based upon 2 of 3 <br />hydraulic criteria. <br />Table 1: Data <br />Party <br />Date <br />Q <br />250 % -40% <br />Summer 3/3 <br />Winter 2/3 <br />CDOW/TU <br />7/7/2009 <br />14.5 <br />36.1 —5.8 <br />6.9 <br />Out of range <br />CDOW/TU <br />9/17/2009 <br />1.0 <br />12.7-2.0 <br />2.9 <br />2.5 <br />The summer flow recommendation, which meets 3 of 3 criteria and is within the accuracy range <br />of the R2CROSS model is 4.9 cfs. This recommendation was derived by averaging the results of <br />the two data sets. The winter flow recommendation, which meets 2 or 3 criteria and is within the <br />accuracy range of the R2Cross model is 2.5 cfs. The late summer recommendation of 3.5 cfs <br />was lowered due to water availability constraints. <br />-3- <br />
The URL can be used to link to this page
Your browser does not support the video tag.