My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSP08666
CWCB
>
Water Supply Protection
>
Backfile
>
8001-9000
>
WSP08666
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 2:49:10 PM
Creation date
10/12/2006 3:09:11 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8221.112.I
Description
Central Arizona Project
State
AZ
Basin
Colorado Mainstem
Date
3/19/1982
Title
Final Environmental Impact Statement: Water Allocations & Water Service Contracting - Central Arizona Project
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.
/
24
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 />(.:...' <br />c;o <br />C',l <br />(~:- <br />c Two M&I entities are estimated to have population effects in the <br />year 2034 under the allocation schemes. Under the No Action allocation <br />alternative, Apache Junction is estimated to experience a population decrease <br />of 22,747 below official population estimates. Palm Springs, under the same <br />a lternat i ve will not be able to support any of the popu1 ati on projected for <br />2034, and faces lesser population decreases under Allocation 3 and <br />Allocation 5. <br /> <br />Alternative allocation schemes for CAP deliveries were studied <br />for their effects upon the copper mining industry. Only the Kennecott <br />operation and the Phelps-Dodge operations will not have sufficient alternative <br />water supplies to avoid reducing production in 2005 and 2034 under Allocation <br />alternatives 1 and 5. However, based upon commuting data for workers from the <br />Kennecott operation, an insignificant number of workers reside in <br />potentially-affected communities. <br /> <br />3. Non-Indian Agricultural Users <br /> <br />In 1981 the DWR recommended CAP water allocations for 23 <br />irrigation districts or individual farmers. The No Action alternative, based <br />on developed lands having a recent history of irrigation (1958-1968) would <br />provi de water to 11 other users. In January 1982, the DWR made revi sed <br />agricultural recommendations and the U. S. Forest Service was added, making a <br />total of 35 entities considered in this EIS, ranging in size from 90 acres to <br />over 150,000 acres. <br /> <br />The alternative allocations (other than No Action) are expressed <br />as percentages of water available to non-Indian agriculture, which vary with <br />the Indian and M&I allocations. In addition there would be differences in <br />water deliveries because of the different priorities and water sharing formulas <br />during times of declared water supply shortage. <br /> <br />Since CAP water would be used as a substitute for ground water, <br />no changes in land use or other impacts are expected as a direct result of the <br />non-Indian agricultural allocations. However, differences in allocations to <br />M&I users can lead to farmland retirement within agricultural districts (see <br />Table 2 and Appendix F.). There will also be some impacts on fish and <br />wildlife, as well as land use, as irrigation delivery facilities such as canals <br />and laterals are constructed to deliver CAP water to these entities. <br /> <br />To deliver CAP water to the 23 current non-Indian agricultural <br />app 1 i cants probably only ei ght new canal systems wi 11 need to be constructed. <br />Therefore, significant loss of fish and wildlife habitat is not expected. <br /> <br />Basically the same holds true for the non-current app1 icants. <br />Of II non-current applicants, at most only two will have to construct <br />additional pipelines for CAP deliveries. This means only a minor loss of <br />wildlife habitat. <br /> <br />,;~~~ <br />~t6' <br /> <br />16 <br />
The URL can be used to link to this page
Your browser does not support the video tag.