Full document / COSOC-W-86-002 - the National Sea Grant Library
Full document / COSOC-W-86-002 - the National Sea Grant Library Full document / COSOC-W-86-002 - the National Sea Grant Library
430 The applications expected of the LEO data and the willingness 'if the volunteer observers determine the collection period and frequency of observations* As a minimum, observations should be made four times a weak ovor a period of a year to generate a useable data set. Data Processing and Storage Before being converted to a standard computer-readable format, the LEO data sheets, as they come in from the field, are visually checked for proper coding of date and location and for obvious errors. The forms are then sent for keypunching. During computer processing LEO data are passed through an edit routine that checks for unreasonable values and flags those particular values. The observer Is then contacted and requested to verify or correct questionable data. After these corrections are oade, the LEO data are archived in a data base that is presently stored on magnetic tapes. Data Retrieval The LEO retrieval system is a computer-baaed system that perforins three functions; data retrieval, data analysis, and report generat ing. The system Is designed to be Interactive and self-tutorial. It guides the user through various steps of retrieving a data set for a particular location and time period from the data base and then uses this data set to produce available statistical reports. The reports may be displayed at the user's terminal or directed to a high-speed printer.
- Page 1 and 2: HT 390 .C66 C66 1986 v.2 Thomas EBi
- Page 3 and 4: Copyright® 1987 The Coastal Societ
- Page 5 and 6: "PROPERTY OF NOAA COASTAL K_CE3 CEN
- Page 7 and 8: PLENARY SESSIONS TABLE OF CONTENTS
- Page 9 and 10: CHARACTERIZING A SYSTEM Choir. Char
- Page 11 and 12: TRACKING TOXICS Chair Susan Harvey
- Page 13 and 14: The Use ofthe NationalWater DataExc
- Page 15 and 16: The Site Selection Process foraChes
- Page 17 and 18: MANAGING LIVING RESOURCES Resource
- Page 19 and 20: Estuarine and CoastalManagement - T
- Page 21 and 22: 398 the particular Interests, envir
- Page 23 and 24: 400 data, a developer may discover
- Page 25 and 26: Estuarine and Coastal Management
- Page 27 and 28: fortune to work with several coasta
- Page 29 and 30: growth economics, local feelings ab
- Page 31 and 32: 410 unprotected coastal barriers wi
- Page 33 and 34: 412 caveats. The greatest concerns
- Page 35 and 36: Estuarine and Coastal Management -
- Page 37 and 38: Model of Resort Evolution R. Initia
- Page 39 and 40: Pensacola Beach Like Fort Myers Bea
- Page 41 and 42: had again contributed to serious en
- Page 43 and 44: Estuarine andCoastal Management -To
- Page 45 and 46: High altitude and oblique aerial ph
- Page 47: Estuarineand Coastal Management•
- Page 51 and 52: 2. Table showing days when LEO obse
- Page 53 and 54: d. Sediment transport volume (Figur
- Page 55 and 56: Acknowledgements The success of the
- Page 57 and 58: Estuarine and CoastalManagement •
- Page 59 and 60: Table 1.~Data Dictionary for Select
- Page 61 and 62: Table 2.—Selected SAS Data Manage
- Page 63 and 64: 446 EPA's Office of Policy, Plannin
- Page 65 and 66: 448 NPDES permit number, an outfall
- Page 67: 450 of multi-media and Integrated e
- Page 70 and 71: 454 History ODES was originally dev
- Page 72 and 73: 456 Tool No. Description 1 = PLOT O
- Page 74 and 75: Estuarine and Coastal Management -
- Page 76 and 77: complete National data base, the we
- Page 78 and 79: Brid Sampling- The Operational Phas
- Page 80 and 81: Estuarineand Coastal Management- To
- Page 82 and 83: may serve as a source or data; ana
- Page 84 and 85: o Printed catalogs of water data si
- Page 86 and 87: Estuarine and Coastal Management To
- Page 88 and 89: FIGURE 1. EXAMPLE OF CCRO REQUEST R
- Page 90 and 91: FIGURE 3 ACCESS TO DOC RESOURCES NO
- Page 92 and 93: OPDIN Evolves with its User Communi
- Page 94 and 95: Estuarineand Coastal Management- To
- Page 96 and 97: Estuarine andCoastal Management •
430<br />
The applications expected of <strong>the</strong> LEO data and <strong>the</strong> willingness 'if<br />
<strong>the</strong> volunteer observers determine <strong>the</strong> collection period and frequency<br />
of observations* As a minimum, observations should be made four<br />
times a weak ovor a period of a year to generate a useable data set.<br />
Data Processing and Storage<br />
Before being converted to a standard computer-readable format,<br />
<strong>the</strong> LEO data sheets, as <strong>the</strong>y come in from <strong>the</strong> field, are visually<br />
checked for proper coding of date and location and for obvious<br />
errors. The forms are <strong>the</strong>n sent for keypunching. During computer<br />
processing LEO data are passed through an edit routine that checks<br />
for unreasonable values and flags those particular values. The<br />
observer Is <strong>the</strong>n contacted and requested to verify or correct<br />
questionable data. After <strong>the</strong>se corrections are oade, <strong>the</strong> LEO data are<br />
archived in a data base that is presently stored on magnetic tapes.<br />
Data Retrieval<br />
The LEO retrieval system is a computer-baaed system that perforins<br />
three functions; data retrieval, data analysis, and report generat<br />
ing. The system Is designed to be Interactive and self-tutorial. It<br />
guides <strong>the</strong> user through various steps of retrieving a data set for a<br />
particular location and time period from <strong>the</strong> data base and <strong>the</strong>n uses<br />
this data set to produce available statistical reports. The reports<br />
may be displayed at <strong>the</strong> user's terminal or directed to a high-speed<br />
printer.