My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSP13055
CWCB
>
Water Supply Protection
>
DayForward
>
1001-2000
>
WSP13055
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/29/2009 1:54:18 PM
Creation date
4/18/2008 9:02:17 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8040.200
Description
Energy
State
CO
Date
2/1/1982
Author
Musick and Cope
Title
Briefing Paper on Critical Water Supply Variables for Energy Development in the Upper Colorado River Basin
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.
/
54
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 following tables then compare these 1948 Compact <br />entitlements with the middle scenario for existing and pro- <br />jected deletions which has been compiled by the Colorado <br />Department of Natural Resources (DNR) for its "Draft 13(a) <br />Assessment of Upper Basin Water Availability," Tables 3.1, <br />4.2, and 5.3. (Attached as Appendix 1.) This depletion data <br />supposedly represents all existing water projects on each <br />Colorado River tributary in each Upper Basin state, and those <br />projects which each state desires and expects to develop by <br />the year 2000 on each Colorado tributary. The study subunit <br />numbers used in the Colorado DNR study for each tributary in <br />each Upper Basin state are shown on the following tables for <br />quick reference. These study subunits are also graphically <br />shown on Figure 2. <br /> <br />The tables show that under these assumptions the 1948 <br />Compact entitlements for Colorado and Utah are enough to meet <br />the needs of each Colorado River tributary in these states, <br />but only by a very small margin. The margin for Wyoming is <br />more comfortable. New Mexico's entitlement is a bit short. <br />In all cases the Colorado DNR middle depletion scenario for <br />the year 2000 roughly corresponds to each state's 1948 <br />Compact entitlement. This depletion scenario therefore ser- <br />ves as a rough benchmark of when compact decisions must be <br />made under these assumptions. Quite simply, if these deple- <br />tion levels are exceeded on anyone tributary, there must be <br />a corresponding curtailment of water development expectations <br />on another tributary in the same state, if that state is to <br />stay within its state-wide entitlement. Or, the state-wide <br />compact entitlement of another Upper Basin state must be cur- <br />tailed, if the Upper Basin is to meet its obligations to the <br />Lower Basin. <br /> <br />The use of the Colorado DNR middle depletion scenario <br />for each Colorado River tributary as a compact benchmark may <br />be slightly optimistic because the Colorado DNR depletion <br />data does not include mainstem reservoir evaporation. <br />Accordingly, the following tables attempt to account for this <br />loss as follows: In 1975, .607 MAF evaporated from Flaming <br />Gorge, Blue Mesa, Morrow Point and Lake Powell Reservoirs. <br />("Consumptive Uses and Losses Report." ) The evaporation ~. <br />loss associ~ted with the Colorado DNR middle depletion sce- <br />nario could be somewhat less because increased, off-reservoir <br />depletions by the year 2000 could reduce reservoir inflows <br />and surface areas. The tables therefore reflect mainstem <br />reservoir evaporation charges which are 10% less than the <br />1975 level or .546 MAP. This adjusted evaporation charge is <br />then allocated to each Upper Basin state according to 1948 <br />Compact percentage entitlements, and to each Colorado River <br />tributary within each state according to the Colorado DNR's <br />middle depletion scenario. <br /> <br />-24- <br />
The URL can be used to link to this page
Your browser does not support the video tag.