A
SYSTEM
 AND
 FOR
STORAGE
RETRIEVAL  OF
WATER   USE
      INVENTORY
              DATA
                        U. S. DEPARTMENT OF THE INTERIOR
                     FEDERAL WATER POLLUTION CONTROL ADMINISTRATION
                             NORTHWEST REGION
                      COLUMBIA RIVER BASIN COMPREHENSIVE PROJECT
                            WORKING PAPER N
                              DECEMBER 1966

-------
DATE: December 1966
Prepared by DL?
Reviewed by FIN
Approved by WWT
DISTRIBUTION:
Project Staff X
Cooperating Agencies X
Generat X
This working paper contains preliminary data and information primarily for internal use
by the Columbia River Basin Project staff and cooperating agencies. The material pre—
sented in this paper should not be considered as final.

-------
                       WORKING PAPER  NO. 59
A
SYSTEM   FOR     STORAGE
 AND     RETRIEVAL   OF
WATER   USE   INVENTORY
                          DATA
by DANIEL L. PETKE, SA Sanitary Engineer
                        U.S. DEPARTMENT OF THE INTERIOR
                 FEDERAL WATER POLLUTION CONTROL ADMINISTRATION
                                NORTHWEST REGION
                   COLUMBIA RIVER BASIN COMPREHENSIVE PROJECT
                                  DECEMBER 1966

-------
CONTENTS
Introduction i
Background i
System Description 2
Data Storage Procedures 3
Deleting and Changing Data B
Data Retrieval 9
Possible Future System Development and Use 10
ii

-------
INTRODUCTION
Water resource planning and development
must inescapably be informed and directed
by consideration of water use patterns.
Existing configurations of water use shape
the conditions that determine resource
utilization possibilities; while the poten-
tialities of use must be reflected in and
governed by resource development.
in particular, water quality levels exer-
cise a limiting effect on water use capa-
bilities; in turn, the nature and intensity
of water use directly affect water quality.
Water quality planning, then, must include
a realistic consideration of water utiliza-
tion if it. is to result in optimal water
quality measures and expenditures. Cer-
tainly there can be no realistic water
quality objectives or standards without a
reference to water uses.
Much information concerning water use has
1 velopment of a comprehensive data stor-
age and retrieval systeni for use by water
pollution control personnel was initiated
in 1961. The first two elements of this
system, known as STOBET Subsystems I and
II, have since been placed in operation.
These systems provide a means for efficient
storage and retrieval of the huge quanti-
ties of water quality data generated by
activities of the many groups interested in
defining and measuring the water pollution
problem. Also operational are a series of
auxiliary computer programs designed to aid
iii the computation and summarization pro-
cedures required to discern meaning from
the many individual facts available.
With the transfer of water pollution con-
trol functions to the Department of the
Interior, the use of the USPHS honeywell
Model 400 canputer will be phased out. in
its place will be an IRd 360 Model 65 com-
puter, a much larger, faster and more flex-
ible machine. However, the complex job of
reprogramming existing systems for this new
been collected in connection with compre-
hensive water pollution control projects
now underway in many parts of the country.
Numerous other local, State and Federal
agencies also have data of this type. Un-
fortunately, however, these data are not
necessarily in a readily usable or consis-
tent form.
Because of the definite and immediate
need for a detailed inventory of present
and potential water uses, in addition to
the lack of an operating system for compil-
ing such information, personnel of the
F MO Columbia River Basin Project have de-
veloped a simple, but workable, system for
the storage and retrieval of water use in-
ventory data. it is hoped that this system
will serve as a tool for both State and
F1NPCA personnel in the development of water
quality standards in the Northwest Region,
as well as serve the needs of those involv-
ed in long-range planning.
BACKGROUND
machine and its associated ternjnal facil-
ities will undoubtedly necessitate some
delays in the development of additional
systems to provide storage and retrieval of
such information as water and waste treat-
ment facility inventories (STOBET III and
IV), biological data (STORET V and VI),
economic and demographic data and, pos-
sibly, water use inventory data.
The Northwest Regional Office has easy
access to the computer center at Oregon
State University in Corvallis, Oregon, and
has close working relationships with per-
sonnel at the computer center. Therefore
the system described in this paper was
programmed for the Control Data Corporation
Model 3300 computer. With some revision
and additional programming, the system
could be used by others throughout the na-
tion. Certain technical programming diffi-
culties associated with conversion of sys-
tem programs for use on other computers may
be anticipated; however, these difficulties
are not expected to be insurmountable.
1

-------
SYSTEM DESCRIPTION
Basic elements of the system for storage
and retrieval of water use inventory data
consist of: (1) procedures to identify and
store data concerning the location of
various stream reaches under consideration;
(2) procedures to record and store water
use data including such parameters as use
category, intensity of use, and tme of
use; (3) methods of updating and revising
existing data as better and more reliable
information become available; and (4) meth-
ods of retrieving the data in any one of
several ways to best fit the needs of
users.
Beach Location Code - The reach location
code is based on and compatible with the
S1t1 ET Subsystem I location code concept,
which utilizes a stream mileage and index-
ing method of locating any point on any
stream in the United States. (Those
readers unfamiliar with STU ET Subsystem I
are referred to the publication entitled,
“The Storage and Retrieval of Data for
Water Quality Control” by Richard S.
Green.) Thus, any reach of any stream may
be described by defining the downstream end
point of the reach with the proper S1XJ ET
Subsystem I location code and providing an
additional number which represents the
reach length to the upstream end point of
the reach.
The boundaries of stream reaches should
be defined to allow for the inclusion of
enough data to adequately describe the
water uses of the stream system under con-
sideration. System users may find any or
all of the following reach boundary cri-
teria of value in defining stream reaches:
1. Confluence of major tributary
streams
2. State lines
3. Existing dams
4. Probable future dams
5. Gaging stations
6. Prominent physical features
The reach location code is not, at pre-
sent, completely adapted to reaches in
estuarial waters where interlocking chan-
nels or large open water bodies cannot
easily be fitted into the Subsystem I joca-
tion code scheme. If, at. a later date, it
becomes desirable to define such reaches,
it is conceivable that the system could be
adapted to the coordinate location codiug
scheme utilized in STOBET ubsystem .11,
described in the publication entitled,
“Storage and Retrieval of Data for Open
\Vater and Land Areas” by Donald P. Dubois.
Use Parameter Code - Water use inventory
data varies significantly from other forms
of information - such as water quality
data - in that many times the information
may be based on opinion and professional
judgment rather than on measurable quan-
titative fact. Indeed, the problem of
quantifying various water use data, par-
ticularly in such use categories as “envi-
ronmental aesthetics”, will require major
refinements of descriptive techniques. For
this reason, it was decided to develop the
system in rather general terms for the pre-
sent, and to leave the system somewhat
“open ended” so that quantitative data,
possibly including economic evaluation,
might be incorporated at a later date.
Separate categories for present uses as
well as potential uses have been provided
for, however.
The various water use parameters and
associated codes for which the system was
originally programmed are listed and ex-
plained in Table 1. The use parameter
coding is flexible and will accomodate the
addition of other use paralqeters if it is
later deemed desirable. It should also be
noted that in some cases, for example the
water supply category, uses are broken down
into as many as three levels of detail.
Thus, it is possible to describe separately
a use such as industrial cooling water, or
process water, if such detail is available,
or to describe the use merely as industrial
water supply if detailed information is
lacking.
In order to describe the relative mag-
nitude of water use, a simple ‘light-moder-
ate-heavy’ use intensity triad was incor-
porated into the system. It is recognized
that a general evaluation of this type has
many drwwbacks; however, it was felt that
an attempt to provide a more detailed
quantification concept would create more
problems than it would solve at this time.
2

-------
The intensity of use category should be
considered as a magnitude indicator for a
water use within a specific reach of a
stream, not merely as an indicator of the
magnitude of the specific water use. For
example, an irrigation diversion of 100 cfs
from a stream reach carrying 10,000 cfs
might be considered as a ‘light’ use, while
the same diversion from a stream reach
carrying 150 cfs might be considered as a
TABLE 1
‘heavy’ use.
Finally, because of the importance of
seasonal factors associated with many water
uses, a summer-fall-winter-spring time of
use category was provided for in the sys-
tem. While it might be possible to go into
further detail concerning time of use, such
as listing the months in which a use
occurs, it is doubtful that such detail
would add much value to the system.
WATER USE PARAMETER CODES
000 Fisheries
010 Salmonid (salmon
Oil Migr.ation
012 Rearing
013 Spawning
020 Warm—water game fish
021 Reating
022 Spawning
030 Shellfish
040 Other fish (e.g.,
100 Wildlife
110 Waterfowl
120 Game
130 Other wildlife
200 Recreation
210 Water-contact
720 Barrkside
230 Boating
300 Water Supply
310 Domestic
Industrial
Boiler feed
Cooling water
Transportation water
Process water incorporated in product
Other process water
Stock watering
400 Environmental Aesthetics
Recreational
Parks
Wild areas (not restricted to
officially designated wild areas)
Non- recreational
Hornesites (including summer homes)
Viewpoints
Civic features (water part of
environmental planning)
500 Irrigation
600 Waste Assimilation (existence of signifi-
cant waste loads)
100 Navigation (commercial navigation and/or locks)
600 Hydropower ( 5,000 kw generating capacity)
420
421
422
423
DATA STORAGE PROCEDURES
The techniques of data storage for this
system involve the identification of data
relating to: (1) the location and descrip-
tion of stream reaches in which water use
data are to be described; and (2) the water
use parameters, use intensity, and time of
use associated with each stream reach des-
cribed. These data are coded into punched
cards, which are then used to store the
data on magnetic tape so that the water use
inventory may either be revised or Fe-
trieved by system users.
Cards 01, 02 and 03 are used to store
location and identifying information foir a
particular stream reach. The card series
20 through 29 are used to store present
water use data and the card series 30—39
are used to store ptential water use data.
Detailed instructions for coding each of
these cards follow.
and trout species)
shad, sturgeon)
320
321
322
323
324
325
330
410
411
412
3

-------
1. Serial Beach Code (Columns 1—6)—The
purpose of this field is to record a unique
number which serves as a descriptive label
fora particular stream reach. This six-
digit readi code appears on all other cards
associated with that particular stream
reach and is used in the revision or up-
dating and retrieval of data. The first
two digits of this number represent a State
code which is compatible with State codes
developed in SItUEI’ Subsystem I as follows:
Utah
Washington
Wyoming
The following four digits represent a num-
ber assigned serially to define a unique
stream reach.
2. SItUEf Location Code (Columns 7—76)--
This field is used to define the downstream
end point of a stream reach. The code is
based on the location concept developed for
S1tUET Subsystem I and may be broken down
into the follcwing sub-fields:
Card Ol--Storet Location Code: Figure 1
Idaho
Montana
Nevada
Oregon
15
29
31
40
Col. 7—8 -
9—10 —
11—13 —
14—19 -
20—25 —
26—31 -
32—36 -
31—41 -
42—45 -
46—50 -
51—54 -
55—59 -
60—63 -
64—68 -
69—12 -
13—16 —
49
54
51
TernlEnaI Major Basin
Terminal Minor Basin
Terminal Stream Number
Level I Mileage
Level II Index
Level II Mileage
Level Ill Index
Level III Mileage
Level IV Index
Level IV Mileage
Level V Index
Level V Mileage
Level VI Index
Level VI Mileage
Level VII Index
Level VII Mileage
3. Unused Field (Columns 77—78).
4. Card Number (Columns 79.-80)’--Always
punch “01” toindicate card 01.
SECOND
LEVEL
RIVER
SYSTEM
AS h
I I Ii
liii 1141
1 1 11
MU LES
O I l
bASE
I I VER
till,’
114*1 *1
‘ill’
THIRD
LEVEL
FOURTH
LEVEL
‘S ’S ’S ’
I14 l 141
11111
F I FTH
LEVEL
INDEX MILES
INDEX MILES NOEX
MILES
NOEX
MILES
INDEX
I OEX
‘I ’
1 1 41 1
ill
SIXTH
LEVEL
PS
14’
11
/‘SERiaL
CODE
5,..’ ’
1134 1j
lii 111
Sills,
‘ ‘‘‘‘ I
1 1 4 1 I
22222 2222
Sill
1143 *4
hil l
SEVENTH
LEVEL
‘S
.4
I i
Sill
id *1
1111
227222 2 7
0
—
a a
I ’S ’
I 1 i;1 ii
Si
U
II
22
p2222 122
11 iii 1
I I
I ’
ii
I’
II
Ii
‘ I,
‘a.
Ill
Si III I II
171 1 7114 II 141
111111 111
22
a
I-
a,
z
a,
I-
I ,
I’
I V I
‘‘‘55’
14* 1(1414
11111
7222 22
I I I ‘1’’
llll ll
in a *1411
$
I
I
$
I
1
‘ii’
Ill
Is—n
22 2222 222 2222 22222222 222 222
I ’S’
Ii
I’
SI
a l s S I
$1 I
‘1111 i
ii ’
Ill
1141
I,
11
11
I
I
ills
5 111
1S Ii
Is
I ,
11
I’
EN
S
12
IS
I ,
S.
‘lii ’
I 1 l1
I —’ —’
Iii
I I I
*1
Is’s’
14* 1
‘‘lii
II , ,’
a v i
I’’’
t a1
Is’
II I
a.
Ii
11
vu
IS
II
‘a
Figure 1
$$
I,
I n
I
S
II
11
i a
4

-------
Card 02--Reach Description: Figure 2
1. Serial Reach Code (Columns 1—6)- -Pre-
viously described under section entitled
‘Card 01- -STORET Location Code”.
2. Reach Description (Columns 7—78)--
This field is used to provide a literal
description of the reach for those users
unfamiliar with the Sf€lEf Subsystem I lo-
cation code scheme. For example, a reach
might be described as “SNAKE RIVER FROM
M(I JTH OF BURNT RIVER TO M(JJTh OF WEISEB
RIVER”.
3. Card Number (Columns 79—80)- -Always
punch “02” to indicate card 02.
REACH DESCRIPTION
ooooooeeoonoooo iii oooooooooooa 000000000000000000ooo000oeo000o000ooouoooo
7 W I ?
11111111i11I11111111111I11111111111’111 1111 111’ 111’11’11111’’11’11’’
222222222222Z22222222222222222222222222222222222222222222222222222222222222222
SSI$$I$IIS S$$IlS$S&88$ S 11188 5581$S Sllll8SliI$S 5 5 5$ S ISSSS$$S IS IS II II IS IS I $55551
9999999999999999999999999999999999999 999999999993999999999993999999999999999

Card 03--Reach Length, Description and Re-
vision Date: Figure 3
Figure 2
1. Serial Reach Code (Columns 1—6)--
Previously described under section en-
titled “Card 01- -STORET Location Code”.
2. Secondary State Code (Columns 7-8)--
If the stream reach forms the boundary
between two states, the state code not
used in the first two digits of the serial
reach code should be placed in this field.
If the stream reach lies within a given
state, this field should be coded as “00”.
3. Reach Length (Columns 9-12)- -The
reach length to the nearest one-tenth mile
should be entered in this field.
4. Revision Date (Columns 13-18)--If any
present or potential water use data are
revised or updated in a particular reach,
this field should also be revised to indi-
cate the date of revision. The date should
be entered in this six digit field in the
month-day- year form.
5. Unused Field (Columns 19-78).
6. Card Number (Columns 79-80)- -Always
punch “03” to indicate card 03.
/SERIAL
REACH
CODE
000000
I 234k
111111
I0
‘N
21
5

-------
1. Serial Reach Code (Columns 1-6)--
Previously described under section entitled
‘Card 01 - SIlJ{ET Location Code”.
2. Present Water Use Data (Columns
7-78)--Each water use parameter, with the
associated use, intensity and time of use is
coded into an eight-digit field as follows:
a. Water Use Parameter Code (Columns
7-9, 15-17, etc. )--The three-digit code
of the parameter in question is entered.
(See Table 1 for a list of water use
parameter codes.)
b. Intensity of Use Code (Columns
10, 18, etc.)--A one-digit use intensity
code for the use in question is entered.
This code is in the following form:
Heavy 1
Moderate
I gh t
c. Time of Use Code (Columns 11-14,
19-22, etc. )--The four-digit time of use
code is entered in the field for the use
in question. If a use occurs during the
summer season, a “1” is coded into the
first column of this field. If a use
does not occur during the summer season,
a “0” is coded into the first column of
this field. The second through fourth
columns of the field represent the fall,
winter, and spring seasons, respectively.
For example, a use occurring during the
fall and spring seasonswould be coded
‘ ll01” in this field, while a year-round
use would be coded as “1111”.
3. Card Number (Columns 79-80)--Code
serially beginning with “20”.
/
SERIAL
REACH
CODE
siossi
I7342
Ill’’’
222222
‘lisle
is’s’’
12) 4 $
I’
7•
ii
22
U i.
a
a
‘3
U i
I-
I-
1.,
a
z
a
C,
I i ’
C,
‘ I
‘ 5
7 ,
REACH 1EVISION
ENgI) BATE
0 s Os O’s ’DsasnDoUoeeo ’sseooooeuoe ’eeo ’easesssooeoleooasooooooeooaoIo
• II2 1 I II 71 I Nb*V S! $ I7 eI57 M . Mr U.a 1t12777 ,7,J ,77J l
1111 11111 1111I1111111I111111 1111I1I11I11111I11I111l11111I111I1Jt11111
222 2 2 2 22222 222222222222222222222222222 222222222222222222222 22222222
33333331
I-
z .-
a w
— a
liii sills $isllS$$Il$slil$Si$Sil$SSsss$$s$s$i$iss$s iSlsslsss$issll$illl
, ,g , gg :ssIgssgIssgggggssgss 5 ,gg 5gss , 5gsggg5gggg g gs ,sg g ,sg ,g , gg ,
• II I JM UU1M WNN771nfl7a J7 ) I.,
Figure 3
Cards 20—29- -Present eater Use Data:
Figure 4
2
3
6

-------
The potential water use data are coded
in precisely the same manner as the present
water use data with the exception that the
card number (Columns 79—80) is coded ser—
ally beginning with “30”.
PRESENT WATER USE DATA
1
2
3
4
5
6
7
8
9
CODE
000000
7 2345 1
011111
222222
‘‘so’!
9 ,9 ’ ,,
123 45$
Th
000
7104
Ill
222
000
70 5
111
222
L.a
I-
L.a
1
Vt
‘Is
I ,,
pig
0000
112 131
111
222
1 0 1
(41
U-
I-
I-
‘I ’S
I ,’’
11213
0
2
I
S
000
251117
111
222
5$’
999
*17
‘Dec
$321
‘ill
222
5’’
999’
000
2311 :
111
222
l’s
999
13242
0
2
I
0000
7252$ ”
1111
2222
‘I’’
‘‘‘9
73311
000
2 23
111
222
$1’
‘99
2325
0000
2113711
1111
222
‘‘Is
9999
1 1 137*
000
I 104’
111
22
$ 5
PS I
0000
‘4443$
Ill’
2222
‘Is’
9999
144101
00000000
752537
11111111
11*1
02222222
151 5 1185
09999999
213112
51157
1000
101111
ill
222
‘‘ 5’
9 ,9
lull’
0
2
8
9
000
“413
Ill
Is’
‘99
NI
0000
101021
1111
2222
Is’s
‘99’
7 0 1 13
0
2
S
‘0 .
fl
01
22
I II
PS ’
17212
0000
““nil
liii
222
l’s’
‘9’’
“ “fl it
Figure 4
Cards 30—39--Potential Water Use Data:
Figure 5
POTENTIAL WATER USE DATA
2
3
4
5
6
7
8
9
/
SER I AL
REACH
CODE
000000
123451
111111
222222
‘I’’’ ’
‘9’,,’
223 410
00
‘I ,
Ill
22
Is.
I.-
‘ SI
U I
‘41
l’s
990
It,
0
I I
2
I
9
I
000
222 13 II
111
222
U ”
Vt
I-
U I
I-
sll
‘9,’
11113 14
‘00
IS II I
Ill
‘22
‘Is
999
liii
0000
111121 Z
1111
2222
soil
9999
*2223
I
II
2
I
S
000
23 74
ill
222
Ill
999
3242
0
2
I
9
00 000
i2lit3.’1133
00
111111111111
00 000
11343771
222222222222
‘l 5 5 50 18ssss
783*
999999999991
22333
11271
000
391042
111
222
l ’s
991
• 1041
0000
44410
lilt
2222
l’s’
9991
I 4410$
000
71041
Ill
222
‘Ii
999
10$
0000
1 2 2 S3
liii
2222
l’s’
99,9
2 1 3 1 35
I
11
2
I
9
000
Ii i
22
I’’
999
111
0000
I 11422
liii
2220
5’’’
9991
• eu
000
124413
Iii
222
‘‘I
9 9’ 9
20413
0000
1111141
1111
2222
l’s ’
9’’’
111113
000
I 7271
Ill
22
I’’
‘99
2722 2
eon
3 1 5 77 7$
liii
‘222
333
‘I8
9 99
37,773
Figure 5
7

-------
An actual deck of input cards containing
all necessary data for the description of
present and potential water uses in an
example reach is shown in Figure 6. These
particular data were stored on magnetic
tape and then retrieved to provide the
example retrieval format, which is later
discussed and shown in Figure 7.
r 1 1111 3ecp112 33c 1 11UI142
I 1 513 1 .111 1 11 6*.4 31313
Ii 10 110 IlL —
- : • I . __________________ UI
4OO0O 12 l1 1 Il 0O( 4c Ull!lIc ill 9 2isjl1I1l3c 1l12Ic 1co. ’’ ••
Rt IfliTh OF B& T RIVER TO MOUTH OF ILISER RI 02 444
iii.. iii II 111 111 1
— - 7 , 7 ; 33
3j t3 43 74W3 77 01
• • 2 22
33i
— - — - - I I —— I I 4
S ...S • II . 56 5 liii 58 ’ I I I S S S ‘ IS I S 4 •ss • ii ,i s s • • • • 2121 “ 54 1$
•2 ,4* a u aal al a a . p. . fla , HI. ,u a it a. $ s
111111 I I 1111111 IllilItIllI Itl7llI lIIIt ltIIlItlIItt liiIIlltit lItIltIiIIll .
Ill
212)3 21 2 3)1222 2$2 32$ 22 322223 2 222 2332. 231 22212 3 22222112122 3 22
21177
133333 3 3 213313 1333 1 3 ,) 13 3 SIll 1 3 3 33 3 3I 3 $113 3 1 33: 313: 71 II I 3 3 1: 11
$15 5 .__ L_ -’
•44444 4 4444 14444414444444444444 1 4 4 4 I 4 44 4,4 4 4 4 444 5155 1
111121 1 1 111511 13 5 11 6_S I I1 1 I 11 $ 1 1 I$IJ$ 5 5 $1$ 1 5 55 ! )1 11 lIJI $ I I 717
588875 Ii S 4 1S$U 81 SI 551 155 $ SI 5$ S S S ,SU 5 5 8 5$ 5 5 5 5 5 5i II I 5 14548 S 55
111111 12 1 137117 1 II11T ITII 1 7 1711. 1 I 11711 177 17711 1T111 77 7717471171 7 17
I$ 1 1 17 5 : 5 IISSSS IStI: lSI $S • 5291 II 5 *595 19$ 159$ *95 55 5; * SI $
115161 1 I $1 5Il 5 15111$ lI$ $$ $ $1 I 5 I I 5 I 5 II1* *ili 15 ,52 11 111 1 lI I I I
iItIt•! S N**flUfl a. . .; .. aI a as.. I a p a ala , I ; i... .4fl 1 - a a
_______________________________________________ I . . . . . . ..‘ Figure 8
DELETING AND CHANGING DATA
In any procedure for storing and retriev-
ing data, it is important to be able to
delete and change data already stored if
errors are discovered or if outdated
descriptive information must be replaced.
No attempt has been made in the development
of this system to provide any more than the
simplest form (in terms of system program-
ming) of deleting and changing the water
use data.
The method of deleting and changing data
in storage has been tied to the original
input data. If at any time a revision of
any data on a given card is desired, a
complete new card containing the revisions
must. be submitted for storage. Thus, if an
error is discovered in Column 17 of
Card 20, for example, the procedure for
correcting this error is to submit a new,
complete and correct (in Column 17) Card 20
8
for storage. The computer operator will
then insert the card for storage, which
will automatically erase the original data
and store the new correct data in its place
on the magnetic tape. Likewise, if one
desires to delete data for a particular
water use in a given reach, he should pre-
pare and submit for storage a card which
contains all of the original data except
that data which is to be deleted.
If and when any data are deleted or
changed for a particular reach, a new card
03 should also be submitted to reflect the
latest revision date. It should be noted
here that the revision date applies only to
a particular stream reach--not to an entire
stream system.
To facilitate the use of this rather
limited method of deleting and changing
II
‘I
I
51
I ;
Al
a,
I
22
13
44
1 )
SI
11
SI
I I
at
—

-------
data, an updated listing of the input data
submitted for storage should be kept on
file in the office of those responsible for
After the information contained on the
location, description and use data cards
has been stored on magnetic tape, a re-
trieval routine is used to obtain print-
outs in the output format indicated in
Figure 7. Again, no attempt has been made
in the development of this system to pro-
vide any more than the simplest forms (in
terms of system programming) of water use
data retrieval.
All of the data in storage for a given
stream reach is obtained when a data
retrieval is run for that reach. The sys-
tem user may request retrieval of data
from any reach or any series of reaches and
obtain the output in any reach sequence.
To do this, the user must submit to the
ccznputer operator a deck of retrieval cards
data storage. An updated file of the key-
punched input cards might be used in place
of the listing mentioned above.
DATA RETRIEVAL
consisting of a separate retrieval card for
each reach from which output data are
desired. The data retrieved will be print-
ed out in the same sequence in which the
retrieval cards are submitted; thus, the
user may obtain his output data in any
sequence desired. The retrieval cards used
in this manner have the applicable serial
reach code entered in Columns 1-6, with
Columns 7-80 unused.
In addition, it is possible to retrieve
all of the water use data within a given
state in numeric serial reach code
sequence by submitting to the computer
operator a single retrieval card carrying
the applicable state code in Columns 1-2,
with Columns 3-80 unused.
WATER USE INVENTORY
SERIAL REACH CODE 15 400002
STOREr LOCATION COJI
11OT24G274C’ 327 IC
RETRIEVAL DATE 11/27/66
AGE ii
REACh DESCRIPTION
SNAFE RIVER FROR -I JTK OF bURNT RIVER TO .K UTr , OF w ISER RIVER
REACH LFNGTr 024.1 t 1LT5 OREGGNIOAHU OOAOLR
USES SERVED
• PRESENT WATER USES
REVISION DATE 11/23/66
TIF;E OF USE
F I SlIER ITS
SALMON ID
REARING
SPAWN I so
WARM—WATER GAME FISH
REARING
SPAWNI ND
OTHER FISH
4 IL DL Ir s
WATERFOWL
GAME
OTHER WILDLIFE
RETREAT ION
WATER CONTACT
BANKS IDE
BOAT INC
WATER SUPPLY
INCtISYR IAL
STOCK WATERING
IRRIGATION
WASTE ASSIMILATION
LIGHT
LIGHT
MODERATE
MODERATE
MODERATE
MODERATE
ROOF NAT E
MOO F NA I C
LIGHT
LIGHT
LIGHT
LI GIlT
LIGHT
LIGHT
HEAVY
S F . S
S
SFWS
S
SEWS
EN
SEWS
SEWS
SF N S
SF .5
SF S
SFWS
INTENSITY 01 USE
S
S
S
Figure 1
9

-------
WATER USE INVENTORY
SERIAL REACH COOL IS 400002
5TORET LOCATION COUE
I N10C01032430032740C3277T
NETRILVAL GATE 11/27/66
REACH D SCR1P1ION •
** SNAKE RIVEN FRUM EGUTH OF BUNNY RIVER TO MOUTI OF WEISER RIVER
USES TO BE SEAVEG
F ISIIERI 15
SALMON ID
MIGRAT ION
REAR DIG
SPAWNING
WARM—WATER GAME FISH
REARING
SPAWNING
OTHER FISH
WILDLIFE
WATERFOWL
GAME
OTHER WILDLIFE
RECREATION
WATER CONTACT
BANESIDE
bOATING
WATER SUPPLY
DOME ST IC
INDUSTRIAL
STOCK W*TERINu
ENVIRONMENTAL AESTHETICS
lION—RECREATIONAL
lONE SITES
IRRIGATION
• POTENTIAL WAT€R USES
HEAVY
HEAVY
HEAVY
MOGERA TE
IOOLMAIE
LIGHT
MODE NA YE
ROGERATE
MODERATE
MODERATE
MODERATE
MODERATE
LIGHT
MOUERATE
MOUEHATE
LIGHT
MODERATE
SEWS
SEWS
S
SE..S
5
5F.S
SEWS
S
S
S.
SEW S
SEWS
SE S
SEW S
SE S
WASTE ASSIMILATION
POSSIBLE FUTURE SYSTEM DEVELOPMENT AND USE
This system for storage and retrieval of
water use inventory data was developed to
meet the immediate needs of the F!NP A
Northwest Regional Office. System program-
ming and development efforts were purposely
held to a minimum, with the primary goal
being that of producing a simple, workable
system which could, be available for use
within a rather short span of time. At
present, display of output data from the
system is limited to the format previously
shown in Figure 7. It is possible, how-
ever, to ccnvert these output data into a
meaningful graphical form by developing a
plot of various water uses versus river
miles for the stream under consideration.
Consideration of possible future devel-
opment and use of the system has led to
some interesting ideas, however. It
might be worthwhile to document some of
these thoughts here.
Future development of the system might
logically be directed toward more complete
10
compatibility with the existing STORET
system. Certainly the methods of data
storage, revision and retrieval could be
improved with additional programming
effort. Further expansion of the system
might lead to the incorporation of the much
needed, previously mentioned, quantifica-
tion of water use data. As methods for
economic evaluation of the worth of water
in its various use forms become more
sophisticated, it would seem logical that
data of this type might also be included
as part of the system.
In many aspects of water pollution con-
trol, the interval between the time when
raw facts are at hand and decisions based
on these facts must be made has become very
short. In such cases, it is vital that
there be a way to assemble very quickly all
f cts bearing on the problem, to perform
any mathematical manipulations needed on
these data, and present the analyzed
findings to the decision-making body. To
meet this need, a fully integrated approach
INTENSITY OF USE
T1P L UF USC

-------
to the entire field of data collection,
processing, analysis, reporting, and use is
presently under development at the head-
quarters level.
Certainly, the water use inventory has a
place in such an integrated scheme. For
example, the water use inventory could be
tied to an inventory consisting of water
quality criteria required to support vari-
ous water uses, with the result being a
determination of the limiting, or even the
most economically desirable set of water
quality parameters for a given stream
reach, during a given time period. Pres-
ent water quality data for that particular
stream reach might then be submitted to the
system in order to compare the present
quality with the necessary or desirable
quality condition determined previously.
If the present quality condition were below
that determined to be necessary or desir-
able, the system night conceivably be pro-
grammed to determine why such a condition
exists--and, possibly, what to do to best
rectify such a situation.
11

-------