My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSP03260
CWCB
>
Water Supply Protection
>
Backfile
>
3001-4000
>
WSP03260
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 12:49:29 PM
Creation date
10/11/2006 11:37:42 PM
Metadata
Fields
Template:
Water Supply Protection
File Number
8276.120.10
Description
Grand Valley Unit-Colorado River Basin Salinity Control Project
State
CO
Basin
Colorado Mainstem
Water Division
5
Date
9/10/1991
Title
Final Environmental Assessment: Alternative Lining Methods for the Government Highline Canal - Grand Valley Unit
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.
/
68
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 />00 <br />C\l <br />~ <br />o <br /> <br />Soecific Comments and Resoonses <br /> <br />~::.: <br /> <br />Specific comments have been summarized below and responses <br />prepared. As indicated previously, all comment letters are <br />available for review at Reclamation's Grand Junction projects <br />Office. <br /> <br />Alternative Preferences <br /> <br />Most of the letters expressed general support for the salinity <br />control program in the Grand Valley, including all of the agencies, <br />legislators, and organizations, and most of the Reach 1 landowners. <br />Individuals opposing the salinity control program generally <br />preferred the No-Action Alternative, at least until alternative <br />ideas could be evaluated. Reach lA landowners generally preferred <br />concrete lining for Reach lA, and Reach lB landowners generally <br />preferred either concrete or membrane lining alternatives which did <br />not result in widening of the canal corridor. No comments were <br />received from Reach 2 landowners indicating a preference between <br />the viable lining alternatives. <br /> <br />Comment 1: I prefer the No-Action Alternative because the salinity <br />control benefits are not worth the cost or are questionable. <br /> <br />Resoonse 1: The cost effectiveness of the salinity control in the <br />Grand valley Unit was analyzed as part of the FEIS for stage Two <br />Development, and is based on extensive planning studies and <br />monitoring results. Measures for the Grand valley unit were <br />authorized and funded because they help meet commitments of the <br />Colorado River Basin Salinity Control Act, and "competed" favorably <br />among the proposed projects within the entire basin. The FEIS <br />estimated that the proposed lining of Reach 1 would remove 23,300 <br />tons/year of salt from the river, and the lining of Reach 2 would <br />remove 13,200 tons/year. <br /> <br />Comment 2: "Better" alternatives should be evaluated and <br />implemented. These include the non-viable pipeline and gabion <br />alternatives discussed in the draft EA, covering the lined canal, <br />implementing on-farm control measures instead of lining the canal, <br />and planting a shelterbelt of trees along the south side of the <br />canal to intercept seepage water and utilize the salts. <br /> <br />Resoonse 2: As discussed in the EA, there were several <br />alternatives which were considered and rejected as non-viable <br />alternatives because they were not feasible or cost effective, <br />especially in relation to the membrane or concrete lining <br />alternatives. Pipelines were considered cost prohibitive. Due to <br />the capacity and the relatively flat grade of the canal corridor, <br />it would take multiple 10-foot diameter pipes to be able to carry <br />the canal flow capacity. A quick estimate for a pipeline <br />alternative indicated that the cost would be many times greater <br />than Alternative MI. Savings due to reduced land purchases, <br /> <br />39 <br />
The URL can be used to link to this page
Your browser does not support the video tag.