My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
BOARD02623
CWCB
>
Board Meetings
>
Backfile
>
2001-3000
>
BOARD02623
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/16/2009 3:17:33 PM
Creation date
10/4/2006 7:17:58 AM
Metadata
Fields
Template:
Board Meetings
Board Meeting Date
8/1/1974
Description
Agenda or Table of Contents, Minutes
Board Meetings - Doc Type
Meeting
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
51
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 />The total operational use of water will be ten to twelve cfs or in <br />the neighborhood of 5,000 gallons per minute. Roughly, 3 to 4 <br />barrels of water per barrel of oil. Another figure we have for the <br />Colorado River there is 3,600 cfs. We are using three-tenths of <br />one percent of the average flow of the Colorado River as the next I~ <br />figure shows. You may want to discuss the salinity impact later. I <br />know it is of major concern to everybody in the western states. The <br />impact of one plant will be negligible. Our calculations show it to <br />be about 1/60 of 1 percent increase in salinity down at Hoover Dam, <br />for example. And that is far lower than the fluctuation that you <br />would get at that particular point. The salinity increase is not <br />due to our discharging solids into the river, but is due to using <br />good quality water up in Grand Valley and not allowing that water to <br />flow down the streams to dilute the more salty water down below. <br /> <br />(slide) To illustrate that you have a lot of unusual animal life in <br />this wild area. Even beavers up on top have built a great many ponds. <br /> <br />(slide) And a few down below in Parachute Creek. A few shots of <br />country very close to the water quality problems; namely, the <br />processed shale or the spent shale disposal embankments. Here the <br />embankment from our semi-works facility is shown in the valley. <br /> <br />(slide) Here is an artist's diagram of a commercial embankment and <br />how it would be constructed. It would be constructed layers that <br />would be built up to the final top of the pile. Each layer would be <br />compacted to insure stability and minimal percolation. The top layer <br />would be revegetated. <br /> <br />The lower left surface would be revegetated immediately the first <br />year and we would gradually build up the revegetation from the pile <br />over the first twenty years. The revegetation program then would <br />go on for twenty years. An additional item for water pollution <br />prevention is a catchment dam below that embankment shown here. This <br />dam would catch water runoff or any oil spills from the plant or <br />any other polluted material that could wash off from the plant area. <br />Fortunately, the plant and the embankment would be in the same water- <br />shed so that tbds would be sort of a fail-safe item that would prevent <br />any contamination of surface waters downstream. Fortunately, any <br />kind of water is adequate for moistening processed shale. That <br />would be pumped up to the ongoing shale disposal program and would <br />be utilized in washing the shale as we go along in the operations. <br />Eventually what we are attempting to achieve then is to trap the <br />polluted material into the embankment. <br /> <br />(slide) And here is the selected site for processed shale, Davis <br />Gulch, that we pointed out on the map earlier. The valley floor is <br />about sixty-seven hundred feet below the top of those hills. <br /> <br />(slide) Looking down on the terrain and the vegetation here in Davis <br />Gulch. You can see quite a difference in what it does to the <br /> <br />I <br /> <br />-5- <br />
The URL can be used to link to this page
Your browser does not support the video tag.