My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSP08430
CWCB
>
Water Supply Protection
>
Backfile
>
8001-9000
>
WSP08430
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 2:48:09 PM
Creation date
10/12/2006 2:58:50 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8200.760
Description
Yampa River General
State
CO
Basin
Yampa/White
Water Division
6
Date
1/1/3000
Author
Unknown
Title
Executive Summary - Task 4 Technical Memorandum on Hydrology Water Rights and Development of Basin Model - Yampa River Basin Alternatives Feasibility Study - Draft
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.
/
44
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
<br />The model represents the basin as a network of approximately 200 arcs and 113 nodes and <br />solves this, netwark monthly in three steps. In -the fi~st solution step, water is allocated among diver. <br />sians, storage, and streamflows largely on the basis of water rights priorities; reservoirs bypass inflows ta <br />satisfy senior demands and senior demands are permitted to draw water from storage if such bypasses <br />are insufficient. In the second solution step, reservoirs 'are forced to release water to meet future <br />municipal and industrial demands up to the amounts of those demands or the contract limits of those <br />releases. In the third step, reservoirs arc forced to makesimilar releases to mect future thermal. electric <br />and, in some scenarios, coal.gasification demands. The reason for separating the model solution into <br />steps is to more accurately repr~sent the contract accounting of reservoir releases. <br /> <br />~ <br /> <br />~'1 <br />.:lfi <br />~, <br />~,';.;,', <br />[' <br />;,~~ <br />"", <br />~.c <br /> <br />j~ <br />~;:) <br />~.< <br /> <br />s <br /> <br />001135 <br /> <br />Executive Summary <br /> <br />" <br /> <br />, <br />~~'., <br />~{; <br />~:\': <br /> <br />Certain demands (e.g" municipal demands) are represented as being less than 100% consump- <br />tive, Allocations of water to these demands generates return flows which are represented as inflows at <br />some downstream point in the model. The temporal pattern of consumptive use and return Oow for <br />such demands reflects the nature o.f the specific water use. For example, snowmaking demands are con- <br />sidered 5% ,:=onsumptive and generate return flows which occur in May and June. <br /> <br />~ .; <br />~~: <br />~:;~: <br />~;'- <br />~iX <br />,~ <br />t-' <br />f\ <br />fl~ <br />~i,{ <br />'. <br />V <br /> <br />The model is configured to represent three demand levels and three modes of water delivery. <br />The three demand levels correspond to current (1989), year 2015. and year 2040 demand projections. <br />The 'three delivery modes are direct flow only (no reservoir releases for any purpose), direct flow plus <br />subordination of the Juniper rights to future demands, and direct flow plus reservoir releases. The rea. <br />son for structuring the model to accommodate these delivery modes is to allow evaluation of the two <br />transfer mechanisms for the Juniper rights to instream flow. <br /> <br />The model was calibrated (verified would be a better term) by turning off all reservoir opera. <br />tions, historical demand adjustments, and future demands and insuring that it reproduced historical <br />gage flow at the Steamboat Springs and Maybell gages, <br /> <br />~:':: <br />, <br />~:"~ <br /> <br />;~" <br /> <br /> <br />~\. <br /> <br />.\' <br />~". <br />f:': <br /> <br />:i;;:~ <br />~~~ <br />~ <br />'; <br />~: <br />" <br />,c, <br />" <br />~ <br />~' <br />~ <br /> <br />;~~ <br /> <br />',,,'; <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.