My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSPC05170
CWCB
>
Water Supply Protection
>
Backfile
>
18000-18999
>
WSPC05170
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 11:42:37 AM
Creation date
10/9/2006 5:03:02 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8200.700
Description
Colorado River Basin General Publications - Augmentation-Weather Modification
State
CO
Basin
Colorado Mainstem
Water Division
5
Date
8/1/1977
Author
NAIWMC
Title
North American Interstate Weather Modification Council - Cooperative Planning Sessions - Colorado River Weather Modification Demonstration Project 1976-1977
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.
/
170
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 />00273~ <br /> <br />and projected use of the added water? Using the Colorado River Model and an <br /> <br /> <br />estimated water yield of one million acre-feet over the period of time, the <br /> <br /> <br />flow increase showed the printed amounts of storage increase, demands below <br /> <br /> <br />Hoover Dam, power generation, etc. (see Attachments D). These are some <br /> <br /> <br />projected amounts that could be derived from the demonstration program. This <br /> <br /> <br />was just a first pass through the model, using assumed usage by the hydrolo- <br /> <br /> <br />gists in the Bureau. <br /> <br />We will be making other studies to analyze the effects of seeding on the <br /> <br /> <br />San Juans and Uintas for 1978-1995 and all basin mountain ranges after 1995 <br /> <br /> <br />until 2020. The model was primarily developed for the salinity program <br /> <br /> <br />talked about during our last meeting, The model is going through daily re- <br /> <br /> <br />visions, but the results agree very close to the Stanford Research results of <br /> <br /> <br />the past. <br /> <br /> <br />Item III in the notes are some administrative programming hurdles that <br /> <br /> <br />have been directed to resolve before we can initiate the demonstration program: <br /> <br /> <br />(1) Secretary of Commerce's report on the Federal role must be completed, (2) <br /> <br /> <br />Impact Statement must be prepared, (3) Development of a definite plan, (4) Devel- <br /> <br /> <br />opment of alternative options for cost sharing with the basin States (see <br /> <br />Attachments D). The hurdle that requires the most lead time is the Environmental <br /> <br /> <br />Impact Statement, therefore, we intend to get at it first, We had asked for <br /> <br /> <br />$600,000 in the FY 1978 budget to perform some of the parts of the first hurdles, <br /> <br /> <br />but were turned down because we did not have a definite plan. <br /> <br /> <br />The next item in the notes is about a general cooperative agreement for the <br /> <br /> <br />long-range demonstration program. Maybe, it should be modeled after the memor- <br /> <br /> <br />andum of understanding we have on the HIPLEX program (see part of Attachments <br /> <br /> <br />D). Valantine: It may take longer to obtain a memorandum of understanding <br /> <br /> <br />than obtaining the final contracts. <br /> <br /> <br />The possible Bureau functions in the cooperative demonstration program are <br /> <br /> <br />provided in the last part of the notes. We should discuss as many of these <br /> <br /> <br />today that we can. <br /> <br />E. Concerns from Utah - Paul Summers, Utah Department of Water Resources <br /> <br /> <br />I would like for the Bureau to respond to two concerns voiced by the Utah <br /> <br /> <br />Attorney General's Office. <br /> <br />39 <br /> <br /> <br />, <br />i <br />, <br />1- <br />~ <br /> <br />I <br />
The URL can be used to link to this page
Your browser does not support the video tag.