My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSP07315
CWCB
>
Water Supply Protection
>
Backfile
>
7001-8000
>
WSP07315
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 2:26:46 PM
Creation date
10/12/2006 2:15:15 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8220.101.09B
Description
Glen Canyon Dam/Lake Powell
State
AZ
Basin
Colorado Mainstem
Date
4/1/1995
Title
Comments re: Operation of Glen Canyon Dam Final Environmental Impact Statement
Water Supply Pro - Doc Type
EIS
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
36
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 />5 <br /> <br />IV. IMPACTS OF THE PREFERRED ALTERNATIVE CHANGES <br /> <br />Only two criteria of the preferred alternative (the upramp rate limit and the <br />maximum flow) were changed between the draft and final EIS. The maximum daily <br />change in flow, minimum flow, and the down ramp rate criteria were not <br />changed. Changes to the maximum flow and upramp rate criteria would have no <br />effect on the monthly release volumes. <br /> <br />Use of the increased upramp is expected to occur almost every day. Use of the <br />increased maximum flow criteria would be infrequent especially during minimum <br />release years because the maximum flow criterion would often be over ridden by <br />the monthly release volume and the maximum allowable daily change criterion. <br /> <br />No linkage was found between upramp limits and negative effects to the <br />physical or biological resources of Glen and Grand Canyons. <br /> <br />Since use of the increased maximum flow criteria would be infrequent, <br />differential impacts were judged to be insignificant based on impact analyses <br />of other EIS alternatives. <br /> <br />It should be noted that in high and medium release volume years the potential <br />for extended periods of 20,000 to 25,000 cfs flows would be quite likely; <br />especially during the summer and winter seasons when release volumes are high. <br />This is unchanged from the draft EIS. <br /> <br />A. Increasinq the Uoramo Rate <br /> <br />A range of research flows was conducted from June 1990 through July 1991 as <br />part of the GCES Phase II program. These included high (3,000 cfs to 19,000 <br />cfs) and low (3,000 cfs to 10,000 cfs) fluctuating flows with fast (about <br />7,000 cfs/hour) and slow (about 3,200 cfs/hour) up and down ramp rates. There <br />were also several approximately steady flow periods during which the ramp <br />rates were less than 1,000 cfs/hour. GCES Phase II identified cause and <br />effect relationships between the range of fluctuations (and downramp rates) <br />and adverse impacts to canyon resources. However, no cause and effect <br />relationships between upramp rates and adverse impacts to canyon resources <br />were identified. The draft EIS (a public document peer reviewed by GCES, the <br />National Research Council, and the EIS Cooperating Agencies) states on page 95 <br />that up ramp rates have not been linked to sandbar erosion. The draft EIS <br />also states on page 190 that "Rapid increases in river stage would have little <br />or no effect on sandbars." <br /> <br />Based on work completed by Budhu and Gobin (1994), C1uer and Dexter (1994) and <br />the U.S. Geological Survey (Carpenter, et. a1., 1995) it was determined that <br />the upramp rate would have no imoact on the erosion of the beaches. This <br />conclusion was based on: <br /> <br />1. The down ramp has been shown to be the primary controlling factor <br />in beach erosion (Budhu and Gobin, 1994). The downramp would <br />remain the same (1,500 cfs/hr) and therefore the upramp should not <br />cause any concern for beach erosion. <br />
The URL can be used to link to this page
Your browser does not support the video tag.