My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Yampa River Basin Water Resources Planning Model Final Report
CWCB
>
Water Supply Protection
>
DayForward
>
5001-6000
>
Yampa River Basin Water Resources Planning Model Final Report
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/7/2010 1:04:19 PM
Creation date
7/6/2010 11:25:54 AM
Metadata
Fields
Template:
Water Supply Protection
Description
Yampa River Basin
State
CO
UT
WY
Basin
Yampa/White/Green
Water Division
6
Date
2/1/1997
Author
Boyle Engineering Coporation, Riverside Technology, Inc.
Title
Yampa River Basin Water Resources Planning Model Final Report
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.
/
113
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
ASY_002, and ASY_003) in the basin that were not modeled explicitly. The geographical areas <br />represented by each structure are shown in Table 4.3.1b. <br />TABLE 4.3.1B <br />Areas Represented by Aggregated Reservoirs <br />ARY 001 <br />Water Districts <br />57&58 <br />ARY 002 <br />Water District <br />44 <br />ARY 003 <br />Water Districts <br />54 & 55 <br />ASY 001 <br />Hydrologic Unit <br />14050001 <br />ASY 002 <br />Hydrologic Unit <br />14050002 <br />ASY 003 <br />Hydrologic Unit <br />14050003 <br />Parameters related to the physical capacity of the reservoirs included dead storage, where applicable, <br />total active storage, and area - capacity tables. For the explicitly modeled reservoirs, these data were <br />obtained from either the Division Engineer or the reservoir owners. For the aggregated reservoirs, <br />the data were estimated based on storage decrees and Task Memo 2:09 -12, "Consumptive Use Model <br />Non - Irrigation Consumptive Use and Losses in the Yampa River Basin, as described in Appendix <br />D.11. <br />The initial yampaT.res file was modified manually to reflect the operational ownerships within each <br />reservoir. The reservoir account ownership information was obtained from interviews with the <br />division engineer, the assistant division engineer, the local water commissioners, and in most cases <br />the owner /operator of the subject reservoirs. A more detailed discussion of the operations of these <br />reservoirs is presented in Appendix C, Section 10. <br />Each account in the explicitly modeled reservoir was tied to a diversion structure that had rights to <br />reservoir water. For situations in which the owner of storage water irrigates land under more than one <br />ditch system, an assumption was made that the storage account will be allocated equally to each ditch <br />system. Although this procedure may not accurately reflect actual use of reservoir storage water from <br />year to year, it was considered adequate for purposes of the Yampa Model, particularly since the <br />amounts of storage water so allocated were relatively small (typically less than 300 acre - feet). For <br />' each diversion structure having storage rights, the cumulative storage water available from each <br />individual ownership is summarized in Appendix C, Section 10. All data required to construct the <br />yampaT.res file were obtained from either the Division engineer or directly from the Owners. <br />The One Fill Rule Administration date was set to April 1 for all explicitly modeled reservoirs, and <br />October 1 for the aggregated reservoirs. <br />Phase IIIa enhancements that impacted the reservoir station file include adding three aggregated <br />reservoirs and three aggregated stockponds. Appendix D.11 describes these Phase IIIa <br />enhancements. <br />4.3.2 Net Evaporation File - yampaT.eva <br />The evaporation file (yampaT.eva) contains annual evaporation data (12 average values for every <br />year). <br />I Reservoirs 4 -12 <br />
The URL can be used to link to this page
Your browser does not support the video tag.