My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSP05727
CWCB
>
Water Supply Protection
>
Backfile
>
5001-6000
>
WSP05727
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 2:19:39 PM
Creation date
10/12/2006 1:14:14 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8200.766
Description
Gunnison River Basin General Publications - Correspondence - Reports
State
CO
Basin
Gunnison
Water Division
4
Date
7/7/1993
Author
Unkknown
Title
Gunnison Basin Models - Planning Model - 1991-1992 - Information-Data Specs for User Interface and Ops Code
Water Supply Pro - Doc Type
Data
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
37
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 />nnM~3 <br /> <br />Information Related to Demands <br /> <br />July 7, 199:3 <br />Page 2 <br /> <br /> <br />I. Direct-Flow Water Rights. Existing aggregated demands will <br />each have ten distinct priority classes. Existing, individually <br />modeled demands will each have their actual number of direct- <br />flow rights (including the "no-call" right, in the case of the <br />Gunnison Tunnel), plus one completely user-specifiable right for <br />planning scenarios. "Potential" demands, which users may add <br />to create new scenarios, will have one water right each. (The <br />point-of-use "demand sites" along the Cimarron Canal and within <br />the Uncompahgre Valley Water Users Association will not have <br />water rights associated with them individually. See Cimarron <br />Canal and Uncompahgre Valley Project Info Themes.) <br /> <br />2. <br /> <br />a. <br /> <br />Amount. (Users must specify amount of <br />the direct-flow water right for a new <br />demand (may be zero), and may modify <br />the amount for each water right or priority <br />class of an existing demand.) <br /> <br />c"~~,,t- he <br /> <br />.L.t <br />he"~,"\' Ye <br />,-' <br /> <br />b. <br /> <br />Priority. (Users must specify the priority <br />of the water right for a new demand <br />relative to all the other priorities for the <br />current scenarionincluding previously <br />defined new demands. But users cannot <br />modify the priorities of water rights for <br />any existing demands. Exception: ~ /,\,' <br />Right) <br /> <br /> <br />-, ~. <br />:t" <:trp~,.,,,,,,:+;,::,'t.. K.,.. ~. <br /> <br />'- <br /> <br />Type of Demand. (Determines how requirements may be <br />quantified and whether lagged return flows will apply.) <br /> <br />a. Agricultural. (Includes aggregated and <br />individually modeled demands.) <br /> <br />y: <br /> <br />b. <br /> <br />Non-Agricultural. (Includes only <br />individually modeled demands. Return <br />flow may be all-immediate or all-in-single- <br />calendar-month.) <br /> <br />~ <br />:t <br /> <br />3. Water Requirements. <br /> <br />Direct Specification for Non-Agricultural <br />Demands. (Time-series input data, 12 X <br />40 values in AF) <br /> <br />b. Specification by Factors for Agricultural <br />Demands. <br /> <br />a. <br /> <br />1-< <br />, <br /> <br />Crop Consumptive Use Factors. (12 X <br />40 values in acre-feet/acre, data sets have <br />symbolic names and may be shared by <br />many separate demands.) <br /> <br />Efficiency. (12 X 1 val ues in range 1 % to <br />100%, lower end of range must be > 0%) <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.