Roaring Fork Stream Flow Survey (2)

Home Browse Search

Roaring Fork Watershed Stream Flow Survey I'rojeet Data Summary Prepared by: S3aaron Clarke, Roaring Fork Conservancy December 13, 2004 The working projection and datum for this project is UTM Zone 13, meters, NADE3. This is consistent with the data standard set forth >:-y Executive Order to the Geographic Information Coordinating Committee for the State of Colorado by then Governor Roy Romer. Data USES and DWR streann gages h(,~t ://waterdata.us~s.gov/co/rnwis/nwis; http //wvv<v.dwr.state.co.us/H~-!drolo~/flow search.as~sl In the Roaring Fork Watershed, stream gages are operated by the USGS and CDWE~. Although there are 76 gages, only 18 are real time gages. See Figure and Table 1 for map and table of all stream ga€;es in the basin. USGS real time, preliminary (past year) and historical gage data are available online. DWR real time and historical data is available on line, however the past year data will be obtained directly :from DWR. In two cases (9080100-FRYINGPAN RLVER AT MEREDITH and 9073005-LINCOLN CRI~EK BELOW GRIZZLY RESERVOIR NEAR ASPEN) gages were operated historically by USGS and now by DWR. So data. for these gages will be combined for analysis. An assessment will be made to determine the length of stream represented by each reporting node and €;age. This will be based on location of major tributary junctions and diversions. Also any ancillz.ry considerations will be evaluated such as with the Crystal River at Carbondale, which is heavily influenced by return flows from Roaring Fork. Thus, the gage may not represent conditions for most of the upstream area. Water diversion and water rights Ln the Colorado Decision Support System's (CDSS) Division Five data set h( ttp://cds:;.state.co.us/ft~/gis.asp downloaded 11/1/2004), there are 1785 stream diversions in the Roaring Fork Basin. They also maintain a water rights data set tt ://cdss.state.co.us/db/viewdata rights.a~) that is linked via a structure id to diversion data. For use with the NHD, they would have to be spatially located manually. The most likely scenario is that we will be using the output from CDSS to do the broad-scale analysis so that not all diversions need to be related to the NHT). This broad-scale analysis will identify critical reaches or areas for finer-scale analysis. Diversion for these priority areas can be spatially referenced to the NHD. In these areas, the most important diversions based on anlount, seniority, and/or location will be the priority. Several decisions will have to be made such as how to best spatially reference diversion data to the stream layer- (i.e. point of diversion, will return flow be used and if so how); if the diversion/water rights data is current; and, if they are no1:, how to meet this need. Additionally, any potential changes to the current reservoir and transbasin diversion infrastruct«re or operations will be acknowlledged and impacts accessed.