My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
WSP09889
CWCB
>
Water Supply Protection
>
Backfile
>
9001-10000
>
WSP09889
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 2:56:23 PM
Creation date
10/12/2006 4:00:11 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8271.300
Description
Colorado River Basin Salinity Control Program - General Information and Publications-Reports
Basin
Colorado Mainstem
Water Division
5
Date
8/4/1982
Author
Roger Eldridge
Title
Questions Facing Water Users in the Colorado River Basin and Effects on Arizona's Growth - presented at Arizona's Growth to the Year 2000 conference - August 4-6 1982
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.
/
8
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 />N <br />~ <br />0') <br />C:) <br /> <br />Arizona's Growth - Eldridge p. 2 <br /> <br />magnesium and sodium, and the negative atoms like sulfate, chloride and bi- <br />carbonate. I pointed out that most water chanists prefer to call it SMC, or <br />soluble mineral content, but it means the same thing as TDS. I explained that <br />ppm, parts per million, and mg/L, milligrams per liter, mean the same thing too, <br />at least up to concentrations of 7,000 mg/L. .I said that the threshhold for <br />acceptable drinking water is 500 ppm, and for irrigation water 800-1,000 ppm, <br />and that sea water averages 35,000 ppm. That led me to describe the pre- <br />historic sea that covered mid-America and that left behind salty shale deposits <br />as it evaporated and retreated when the mountains we know as the Rockies rose <br />into place. Davi d fi na lly cut me off and s ai d, "You mean it's sa 1t in the water <br />that makes it taste yucky and hurts plants ," and ran out to play. Si nce then, <br />questions I get around the dinner table are quickly fol1C1i1ed with, "Give the <br />short answer, Dad!" So here are the short answers to the question of what we <br />don't know about what li es ahead for water managers and users in the Colorado <br />River Basin that we share. <br /> <br />1. We don't know how the 1944 Treaty with Mexico will work out when we have <br />a drought. The treaty establishes Mexico's share of the river flow at 1,500,000 <br />acre-feet per year, but in the event of "extraordinary drought or serious acci- <br />dent" in the United States, the amount flowing into Mexico may be reduced in <br />the same proportion as are consumptive uses in the U.S. The treaty does not tell <br />us how to distinguish between a run of the mi 11 drought and an "extraordinary" <br />one, nor whether the drought must affect the entire basin or just one of the <br />sub-basins. How do we factor in U.S. storage reservoirs that can cushion the <br />local effects of drought for two or three yea~s? Do we count transportation <br />and evaporation 'losses on what the up-stream states "deliver" to the Mexican <br />claim at the border? We not only do not have answers to these basic questions, <br />we have no system in place to administer the answers. Who manages drought re- <br />sponses in the Basin? Let's hope that we don't have another 'drought like the <br />one that drove out the Anasazi in the 1300's. <br /> <br />2. We don't know how long the federal government will continue to pay for <br />salinity control projects in the Colorado River Basin. Both Upper and Lower <br />Basin states are united in expecting total federal subsidies for salinity con- <br />trol, despite the contemporary evidence that federal subsidies for water pro- <br />jects are becoming a thing of the past, or at best only available on a cost- <br />sharing basis. It is very significant that the larger portion of the present <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.