Policy and Procedures for the Management and Archival Storage of Data Collected for Basic Data and Hydrologic Investigations in the U.S. Geological Survey, Maryland-Delaware-District of Columbia District

ABSTRACT

This report describes the policy and procedures used by the Maryland-Delaware-District of Columbia (MD-DE-DC) District to manage and store data collected during basic data operations and hydrologic investigations. It is the policy of the MD-DE-DC District that data collected to meet the objectives of projects for hydrologic investigations be documented, organized, stored, and archived in a manner that (1) facilitates retrieval, evaluation, and use by District personnel and others; and (2) enables verification of data contained in all reports and computer databases. Changes will be made to the document as new technology evolves and as new methods are developed.

This report includes appendixes and Data Management Procedures (DMPs) to assist District personnel in managing hydrologic data. Appendix A lists the duties of the Database Administrators (DBAs) and Data Managers. Guidance on the proper management of project files and site files is provided in DMP 1. All data collected or used in a report needs to be stored in the National Water Information System (NWIS) databases. NWIS programs are summarized in DMP 2 (includes link to documentation). Data not entered to NWIS must be stored in an alternative permanent database that is maintained at the District level.

For new sites, or sites that are not currently in NWIS, refer to DMP 3 and Appendixes B, C, D, and E to learn how to properly establish, name, and plot the site on State-County-Master Site-File 1:24,000 USGS topographic maps (paper or digital). Instructions for entering data into GWSI are provided in DMP 4. When duplicate data or sites exist, DMP 5 describes how to merge the data or how to decide when to request that the site be deleted. Instructions for logging in field data for water-quality samples from the USGS lab are presented in DMP 6 and from non-USGS labs in DMP 7. (See also Appendixes F, G, and H.)

Requirements for surface-water sites are listed in DMP 8. Complete and clear field notes are to be taken during each site visit; DMP 9 presents instructions for recording field notes, and DMP 10 provides the requirements for calibration and performance records for measurement equipment. For non-standard digital data, see DMP 11. For stream sediment data, see DMP 12, or for geophysical data, DMP 13. At the end of the project, paper files for each data-collection site and important project files are archived in the District library (DMP 14).

The USGS has the reputation for having a high quality database. In order to preserve this reputation, data management must take a high priority. All data needs to be collected according to guidelines set forth by the USGS, and checked or compared to (and verified in) field notes, laboratory sheets, databases, and all reports. Discrepancies need to be resolved and noted in the paper files and in archived copies of all reports.

INTRODUCTION

Scientific data collected by the U.S. Geological Survey (USGS) is a valuable National resource that must be managed properly (Biesecker, 1991). Data-collection activities in the Water Resources Division (WRD) of the USGS commonly are divided into two principal programs:

• basic-data collection, and

• hydrologic investigations.

Basic-data programs provide routine, ongoing data from a nationwide system of stream-gaging stations, ground-water observation wells, and surface- and ground-water-quality sampling sites. These data usually are obtained to assess long-term trends and to establish base-line conditions for the Nation’s water resources (USGS, 1984a). Basic-data programs of the USGS are recognized widely for their excellent data management. This excellence has resulted from the use of long-established procedures, training, and careful review.

Hydrologic investigations are often done in response to a recognized problem or an anticipated potential problem (USGS, 1984b). Data-collection activities of hydrologic investigations include a wide variety of procedures and usually are more site-specific, more problem-oriented, and of shorter duration than those of basic-data programs; there often is a greater emphasis on understanding hydrologic systems than on data management and record keeping.

The MD-DE-DC District has developed a policy and procedures to improve data management for both basic data and investigative programs. This report is an adaptation of the report, “Policy and Procedures for the Management and Archival Storage of Data Collected for Hydrologic Investigations, U.S. Geological Survey, Indiana District,” Open-File Report 94-61, by Jeffrey D. Martin and David A. Cohen, and the policy report by the data management workgroup in the Massachusetts-Rhode Island District. The policies establish standards for the management and storage of all data collected. The procedures describe the specific activities required to achieve those standards.

Purpose and Scope

The purpose of this report is to describe the policy and procedures used by the MD-DE-DC District and the Maryland Geological Survey (MGS) Hydrologic studies to manage and store data collected as part of USGS hydrologic investigations. The policy and procedures that follow apply to data collected from active hydrologic investigations beginning in Fiscal Year 2000 and beyond. In general, all data (published and unpublished) used in analysis and information related to data analysis or interpretations are covered by this policy and procedures.

This report also provides Data-Management Procedures (DMPs) for reference and a list of personnel assigned to administer the district databases and their duties. [Appendix A. Database Administrators (DBAs) and Manager’s Duties].

Benefits of Proper Data Management

Data collected for hydrologic investigations usually are processed, documented, organized, and archived to meet the short-term needs of each project. Thought should also be given to the needs of future projects, District-wide uses of the data, future National synthesis projects and the needs of other users. The problems of meeting only current project needs are readily apparent:

• lost data;

• greater effort required to retrieve data;

• incorrect well numbers and well names;

• duplicate Site-File or water-quality entries;

• “lost” information (knowledge) when project personnel leave the District;

• difficulty in responding to information requests; and

• the inability to verify data stored in computer databases or published in reports.

Incomplete data in computer databases and paper files limit the usefulness of the data.

Proper data management will eliminate many of the problems described in the preceding paragraph. Properly managed data will facilitate and improve the retrieval, evaluation, quality assurance, use, and storage of data. Also, proper data management throughout the life of a project will greatly facilitate the production of data reports and final reports at the end of the project life cycle when time and money are short. As a result, data users can increase their productivity, and the public can have a higher degree of confidence in USGS data and reports.

DATA-MANAGEMENT POLICY

It is the policy of the MD-DE-DC District that all personnel involved in the collection or compilation of hydrologic and related data shall use and adhere to the Data Management Procedures (DMPs) contained within this document. Data collected to meet the objectives of projects must be documented, quality assured, organized, stored, and archived in a manner that:

(1) facilitates retrieval, evaluation, and use by District personnel and others, and

(2) enables independent verification of data contained in all reports and computer databases.

IMPLEMENTING AND ENFORCING THE DATA-MANAGEMENT
POLICY AND PROCEDURES

It is the responsibility of all personnel involved in the collection or compilation of hydrologic and related data to follow the District DMPs. District Quality-Assurance Plans have been written for Water Quality, Ground Water, and Surface Water and should be used at all stages of the project. Projects must also document their individual sampling and quality-assurance plans.

It is the responsibility of the Section Chief(s) to ensure that Project Chiefs follow the procedures described in these documents. Compliance with these procedures will be reviewed by the Section Chief(s) during project reviews and before the final project report is submitted for Director’s approval. Section Chiefs should consult with DBAs and the Discipline Specialists during the review of the employee’s Performance Standards to help determine the degree to which an employee has complied with the District DMPs.

It is the responsibility of the DBAs to ensure that data added to the database are complete and meet the requirements described in this document. It is the responsibility of the GWSI DBA to ensure that new data-collection sites are established according to the procedures described in this document.

It is the responsibility of the Discipline Specialists to review and approve field forms, assess the need for additional types of information that must be documented and stored, and—in consultation with the DBAs—periodically review and revise the procedures in this document.

It is the responsibility of the Project Chief to ensure that all data have been plotted correctly on Master Site-File topographic maps, correctly recorded on laboratory sheets, and correctly entered into site folders, databases, and reports. Every report, whether published and in the public domain or administratively released, will contain the site ID’s for all data-collection sites used in that report. Tables of water data must include WATSTORE parameter codes.

Authors are required to publish their data—not just summary statistics. Senior authors of reports must ensure that the data in their reports are correct and can be verified by data in Site-File folders and NWIS databases. The senior author is responsible for compiling an errata sheet with corrections for all errors contained in a report.

DATA-MANAGEMENT PROCEDURES SUMMARY

Data Management Procedures (DMPs) have been established to meet the objectives of the District data-management policy and provide specific data-handling procedures. The DMPs will evolve with changes in technology and as new methods are developed.

The DMPs descriptions are given below. Click on the title to link to the DMP. For additional policy information and guidelines, refer to WRD Memorandums: http://water.usgs.gov/admin/memo/

DMP 1: Maintenance and Organization of Project and Site Files

DMP 1 specifies procedures to properly maintain and organize the project files for each data-collection site while a project is active. Each site has a Site-File folder, which includes all the information (list provided) necessary to verify data in a report or NWIS (DMP 2) or other databases.

DMP 2: National Water Information System (NWIS) Databases

Describes the NWIS databases and includes the URLs for the online documentation for: GWSI, QWDATA, ADAPS, SWUDS, and AWUDS. Also includes references to the data required listed in the Appendixes.

DMP 3: Establishing a New Ground-Water, Surface-Water, or Water-Quality Data-Collection Site

Steps involved in establishing a new site are provided in DMP 3. The DMP includes instructions for plotting the site on a District State-County Master Site-File topographic map; determining the site ID, site names, and latitude and longitude; and checking for duplicate sites and errors.

DMP 4: Ground-Water Site Inventory (GWSI) Data Entry and Checking Instructions

This DMP includes instructions on the three methods for entering data to GWSI: (1) Query Entry, (2) Full-Screen Entry, and (3) Modifying a template. Instructions are also given for checking the input file, copying the file to the WATIN directory, and retrieving and checking the data once it is in GWSI.

DMP 5: Data Merge and Data or Site Deletion

This DMP explains how to verify if duplicate sites exist and how to either merge or delete the data, and decide if the site should be deleted.

DMP 6: Maintenance of Water-Quality (QW) Files

Procedures for entering water-quality data to QWDATA are provided in this DMP. The steps include logging in the sample, checking the login information, tracking the data as it comes in from the lab, reviewing the data, and handling “badqw”.

DMP 7: Maintenance of Water-Quality Files from Non-USGS Analytical Laboratories

Provides guidelines and instructions on how to input data from other labs into QWDATA using QWSwitchyard.

DMP 8: ADAPs and Surface-Water Sites

Lists data required by the ADAPS DBA for entry of surface-water data.

DMP 9: Recording Field Notes

Policy of using standardized field forms and requirements for non-standard field forms are presented in this DMP.

DMP 10: Calibration and Performance Records for Measurement Equipment

This DMP gives guidelines for recording equipment calibration and performance records.

DMP 11: Management of Non-Standard Digital Data

Non-standard digital data includes all digital data that cannot be stored in NWIS, such as geophysical logs, Global Positioning System (GPS) data, and data logger records. This DMP provides guidelines to properly maintain and organize this data.

DMP 12: Management of Stream Sediment Data

Guidelines for managing stream sediment data are presented in this DMP.

DMP 13: Management of Geophysical Data

Guidelines for managing geophysical data are provided in this DMP.

DMP 14: Archiving Paper Files and Project Files in the District Library

Instructions for archiving site file data and project files at the end of a project are provided in DMP 14.

DATA-MANAGEMENT FLOW CHART

Coming soon…
DMP 1: Maintenance and Organization of Site-File Folders

This DMP specifies procedures to properly maintain and organize the project site-file folders for each data-collection site while a project is active. Each site has a Site-File folder, which includes all the information (list follows) necessary to verify data in a report, or database. The files for each data-collection site are maintained in folders in the office of the project staff while the project is active. Each project will keep an explanation of the project filing system (what data is being stored and where it is physically located in the office). Any changes in data (for example, water-quality reruns, incorrectly located sites, math errors in levels or other calculations) are explained, dated, and initialed in the site-file folders, and appropriate updates are made to NWIS databases (DMP 2). After a project report has been approved, or if no report is to be published after the project has been completed, the site folders will be archived in the District library (DMP 14).

Project Chiefs and staff are responsible for properly maintaining and archiving Site-File folders in the District library at the end of the project, and for initiating appropriate changes to NWIS databases. The GWSI DBA is responsible for resolving any filing or site-information problems and ensuring that Site-File folders have been archived properly. The Project Site-File folders will be examined by the Database Manager prior to, and as part of, the Project technical reviews.

The following data (if applicable) is the minimum information to be stored in Site-File folders for each data-collection site. The table below lists the discipline that applies to the information required: surface water (SW), ground water (GW), water quality (WQ), and all. This checklist can be copied or printed, checked off, and included in the Site Folder.

Included in folder	Discipline	Description of Component
	All	Site description including how to access site, copy of a topographic map showing site location and topographic map name.
	All	Safety information including site safety plan (if applicable).
	All	Permission and permits to sample, install wells, gages, or other monitoring equipment (Dig safe, property owner permission, building permit and access).
	All	Original field notes.
	All	Dated printout of GWSI Site-File information. Name and date must be recorded.
	All	Photographs of relevant features of the site. May include surrounding land use, equipment, benchmarks, and measuring points.
	GW	Driller’s log, geophysical logs, and well-construction information.
	GW	Aquifer test, slug test, and other hydraulic data.
	SW	Station analysis.
	SW	Water-level and discharge-measurement notes.
	SW, GW	Level notes and computations, including information on the altitude of the land surface and a description of the measuring point, reference points and benchmarks.
	SW, GW	Dated printouts of primary computations for recording instruments.
	SW, GW	Copies of all rating tables, datum corrections, and shift information.
	WQ	Quality-assurance reports for non-USGS labs used.
	WQ	Copies of analytical services request forms (laboratory login sheets).
	WQ	Water-quality analytical laboratory related forms (such as: field alkalinity, bacteria, biological oxygen demand).
	WQ	Printouts of water-quality data from all labs used on project (in chronological order).
	WQ	Water-quality sample rerun and verification (requests, results, and interpretations).

ö
DMP 2: National Water Information Systems (NWIS) Databases

The NWIS databases are the official databases maintained by the USGS to store information about the occurrence, quantity, quality, distribution, and movement of surface and ground water. All data collected or used and reported by the Water Resources Division (WRD) of the USGS must be stored in NWIS, or an alternative database approved by the District. This includes data from outside sources that are used in support of WRD published conclusions and are not archived or published elsewhere (WRD Memorandum 92.59).

NWIS documentation and WRD policy memorandums can be accessed from the following sources:

District Homepage: http://md.water.usgs.gov/usgs/nwis_doc/

NWIS Homepage: http://nwis.usgs.gov/forms/gwforms.html

WRD Memorandums: http://water.usgs.gov/admin/memo/

NWIS is Unix-based and composed of four subsystems: Ground-Water Site Inventory System (GWSI), Water-Quality System (QWDATA), Automated Data-Processing System (ADAPS), and Water-Use Data Systems (SWUDS and AWUDS). These systems are described below with links to documentation for each system.

GWSI: Ground-Water-Site Inventory

The Ground-Water Site-Inventory (GWSI) System contains and provides access to inventory information about sites at stream reaches, wells, test holes, springs, tunnels, drains, lakes, reservoirs, ponds, excavations, and water-use facilities.

The descriptive elements or components for a ground-water, surface-water, or water-quality sample collection site of GWSI are stored in one general data file called the site file, which contains site information common to all subsystems of NWIS. State and County codes are listed in Appendix B. The other data files in GWSI contain well-construction, ground-water level, ground-water well or spring discharge, geohydrologic characteristics, observation-well report header, aquifer hydraulic, State ground-water use, and miscellaneous data.

Information required to be entered in the site file is listed in Mathey, 1989, and Appendixes C and D. Mandatory information is identified by Site-File component numbers in bold type. Required fields for GWSI ground-water data files for all ground-water sites are listed in Appendix E. Each person requesting the establishment of a ground-water site or storing data under an existing ground-water site must become familiar with these components in GWSI. Site ID, location and name for all data-collection sites are to be entered in GWSI within one week after the header file information is approved by the GWSI DBA. All remaining site information will be entered into GWSI within 30 days.

It is the responsibility of the Project Chief or the project staff to input and edit these data. It is the responsibility of the GWSI DBA to review and update these data. All entries to the Site File and GWSI ground-water data files are coded on form 9-1904-A, revised March 1999, (available on the GWSI Homepage) prior to entry into GWSI.

Chapter 1: GWSI

Mathey, S.B, ed., 1989, User’s manual for the National Water Information System of the U.S. Geological Survey, Chapter 1, Version 3_2, Ground-Water Site Inventory system: USGS Open-File Report 89-587, 242 p.

http://nwiqqvarsa.er.usgs.gov/conversion/nwisdocs3_2/gw/GW.user.book.html.

GWSI/Site File/SW Station Coding Forms

/conversion/nwisdocs3_2/gw/gwforms.html Forms

QWDATA: Water Quality Data

The Water Quality (WQ) System contains field data and results of water samples that describe the chemical, physical, biological, and radiochemical characteristics of both surface and ground water. Types of chemical data include filtered and/or unfiltered concentrations of major ions, trace elements, nutrients, pesticides, base-neutral organics, acid organics, and radiochemical compounds. Physical characteristics data include pH, specific conductance, water and air temperature, dissolved oxygen, barometric pressure, and percent dissolved oxygen saturation.

QWDATA also stores sediment and biological data. Sediment data includes suspended-sediment concentrations in water, sediment-size distributions, and chemical concentrations of suspended sediments and bottom sediments. Biological data in the system includes population densities and diversity indexes or periphyton, phytoplankton, and benthic invertebrates.

Each person submitting a water-quality sample must become familiar with the required information and WATSTORE parameter codes (Appendix H) for storing data in QWDATA (see Garcia and others, 1997 and DMP 6 and 7). Mandatory information required to be entered into QWDATA for all water-quality samples is listed in Appendix G. These data can also be obtained from a completed Analytical Service Request form (ASR) from the USGS’s National Water-Quality Laboratory (NWQL). WATSTORE parameter codes required to be entered in QWDATA for all water-quality samples are listed in Appendix H. WATSTORE parameter codes required to be entered in QWDATA for all field alkalinity measurements are listed in Appendix I.

It is the responsibility of the Project Chief to complete the USGS ASR form and to login each water-quality sample to QWDATA (DMP 6). It is the responsibility of the QWDATA DBA to review this data during or soon after sample login.

Under special circumstances, these data may be entered after a sample is logged in the computer. These circumstances include time needed to analyze geologic and hydrologic data in order to determine geologic unit and aquifer type. The Project Chief or staff may not have access to the analytical results until all pertinent information has been entered in the computer. Project staff should be reminded of the need for prompt review of chemical analyses (especially nutrients). Any delay may compromise the validity and/or quality of the data.

Chapter 2: QWDATA

Garcia, K. T., and others, 1997, User’s manual for the National Water Information System of the U.S. Geological Survey, Chapter 2, Version 3_2, Water-Quality System: USGS Open-File Report 97-634, 253 p.

http://nwiqqvarsa.er.usgs.gov/conversion/nwisdocs3_2/qw/qw-user.doc.book.html

ADAPS: Automated Data Processing System (Surface Water)

ADAPS stores time-series data that describe stream-water levels, streamflow (discharge), reservoir water levels, surface-water quality, ground-water levels, and rainfall. Data is collected by automated recorders (transmit data through telephone line or satellites) and by observations and manual measurements at field installations, and processed using ADAPS procedures.

For processing surface-water data, refer to DMP 8. Information required or recommended to be entered in the Site-File for surface-water sites with data to be entered in ADAPS is listed in Appendix K (mandatory information is identified in bold type). Staff will consult with the ADAPS DBA to establish Site-File components for entering and storing data in NWIS databases. Each person storing data in ADAPS must become familiar with the Site-File components. Drainage areas for all surface water sites will be determined and entered into GWSI within 30 days after the site is established.

It is the responsibility of the Project Chief to provide the requisite data (DMP 8) to the ADAPS DBA. It is the responsibility of the ADAPS DBA to review and input these data into ADAPS.

Chapter 3: ADAPs

Bartholma, Scott D., compiler, 1997, User’s manual for the National Water Information System of the U.S. Geological Survey, Chapter 3,Version 3_2, Automated Data Processing System: USGS Open-File Report 97-635, 219 p.

http://nwiqqvarsa.er.usgs.gov/conversion/nwisdocs3_2/adaps/adaps.book.html

SWUDS and AWUDS: Water-Use Site-Specific and Aggregated Water-Use Data System

The Water-Use Data System stores summary data on water use throughout the Nation and includes two database systems; the Site-Specific Water-Use Data System (SWUDS), and the Aggregate Water-Use Data System (AWUDS). The District Water-Use program is an ongoing effort to make MD-DE-DC water-use data available to water managers at the Federal, State, and local levels. Each person collecting data to be stored in the Water-Use Data System (SWUDS) is referred to the water use web page, which describes procedures for the compilation and storage of data in SWUDS. (See Augestine, 1997 and Perlman, 1998):

http://vs03dmdtws.er.usgs.gov/usgs/database/swuds/index.html,

If water-use data is collected, the information should be forwarded to the District Water-Use Specialist, who will process and store the data in the Water-Use data system (SWUDS).

At a minimum, the data should contain:

• quantity of water (in million gallons per day)

• location (town or county and hydrologic unit)

• source (surface water or ground water)

• how the data was acquired (direct data collection or by indirect method).

Chapter 4, part 1: SWUD

Augenstein, T.W., compiler, 1997, User’s manual for the National Water Information System of the U.S. Geological Survey, Chapter 4, Part 1, Water-Use Data System, Site-Specific Water-Use Data System: USGS Open-File Report 97-636, 398 p.

http://nwiqqvarsa.er.usgs.gov/conversion/nwisdocs3_2/swuds/wu.book.html

Chapter 4, part 2: AWUDS

Perlman, Howard A., 1998, User’s manual for the National Water Information System of the U.S. Geological

Survey, Chapter 4, Water-Use Data System, Part 2, Aggregate Water-Use Data System: USGS Open-File Report 98-575, 33 p.

http://nwiqqvarsa.er.usgs.gov/conversion/nwisdocs3_2/awuds/awuds_user.html

ö

DMP 3: Establishing a New Ground-Water, Surface-Water, or Water-Quality Data-Collection Site

Introduction

For a new site to be established, the project staff must be able to:

¨ Locate a site in the field using the USGS Office of Ground Water Ground Water Procedure Document (GWPD) 5.

¨ Use a computer-based digitizer, a Global Positioning System (GPS) unit, or a latitude-longitude scale to determine the latitude and longitude of a point,

¨ Be familiar with coding Ground-Water Site Inventory System (GWSI) forms, entering data, and retrieving data in GWSI, and

¨ Follow District policy and procedures for data management.

Instructions

To establish a new site, the following steps must be taken:

1. Plot the site on a map.

2. Determine the Site ID and the latitude and longitude.

3. Check for duplicate sites.

4. Have a station name assigned for the site.

5. Code and enter data into the NWIS databases.

6. Check for errors.

7. Plot the site on the Master Site-File map.

8. File the original field sheets (DMP 1).

1. Plot the site:

¨ Each new site should be located in the field using the procedure described by the USGS, Office of Ground Water Ground Water Procedural Document 5 (see Open-File Report 97-11, A Quality-Assurance Plan for District Ground-Water Activities of the USGS). Although GWPD 5 describes how to locate a ground-water well site, it can also be used to locate a surface-water stream site.

¨ Transfer the location of the site from either the detailed sketch map or aerial photograph to a USGS 7.5-minute topographic quadrangle (1:24,000 scale) project work map.

¨ Mark or plot the exact location of the site using the symbols listed in the table below. Open symbols (about 1/8 inch in size) are used.

	Wells are plotted with circles.
	Springs are plotted with a circle having a tilde indicating direction of flow.
	Lakes are plotted with squares.
	Stream and river sites are plotted with triangles.
	Meteorological sites are plotted with X’s.

2. Determine the Site ID and/or the latitude and longitude

After the new site is plotted on a USGS 7.5-minute topographic map, if the latitude and longitude were not already derived using a GPS unit, use a digitizer* to determine the latitude and longitude to the nearest second. Latitudes and longitudes may be obtained from the computer using GIS software in the future, but this method is not as efficient at this time. Maps used to determine latitude and longitude should be kept flat and not folded. It is the responsibility of the Project Chief or staff to ensure that new sites have been field checked and are accurately plotted on topographic maps.

* Using the digitizer to determine latitude and longitude.

Setup:

1. Turn the digitizer on by pressing the toggle switch on the black box on the right side, towards the back. On the left side, there are switches that raise and lower and tilt the table. The table is also a light table.

2. Secure the topographic map with non-sticky tape to the digitizing table at least 3 inches from the lower edge (the red light will light when it is out of range).

Keypad:

3. Using the keypad, select 3-point orientation (the P key).

• Generally, accept the defaults for setting up the digitizer:

4. Set or Reset (1, 2)? 1 (press enter to accept)

5. Lat/long data (1-YES, 2-NO)? 1

6. N(1) OR S(2)? 1 (this refers to Northern or Southern Hemisphere.)

7. W(1) OR E(2)? 1 (this refers to Western or Eastern Hemisphere.)

Registering the Map:

8. In a counter-clockwise manner, enter 3 sets of lat/longs of the quadrangle or a rectangle that encloses the point. It is easiest to start in the lower left corner. It is not necessary to include preceding zeros, and if the value is zero, you can just hit enter. Do a brief check to see that the numbers you entered are correct and the latitude and longitude are increasing as you move the wand towards the northwest (up and left).

9. Move the wand (notice the cross hairs) over the exact lat/long point and press the rectangular button or any of the number buttons.

Latitude and Longitude:

10. Place the wand crosshairs over the point where you want the lat/long and record the number. The value reads to the hundreth place, but because of the variability of the paper topographic map (size varies with humidity), the number should be rounded to the nearest second.

Finish:

11. Place the wand in the holder.

12. Turn off the digitizer.

13. Remove your map.

2a. Ground water (well or spring)

For ground-water sites, the Site ID is composed of a 5-character agency code followed by a 15-digit site number which represents the latitude and longitude (preceded by a zero if less than 100) and a 2-digit sequence number. The first site at a given latitude and longitude has a sequence number of 01, and the 100th site with the same latitude and longitude has a sequence number of 00.

Example: 390737076374401

2b. Surface water (stream or lake)

Surface water or lake sites to be included in the Automated Data Processing System (ADAPS), are assigned an 8-15 digit downstream order number by the Data Section Chief.

Example: 01586000

3. Duplicate checking

Checking data is an essential step in quality-assuring our data. The database is more useful and efficient if there are no duplicate or incomplete Site File entries. To eliminate the creation of duplicate Site Files, and improve the usability of the NWIS databases in the MD-DE-DC District, when a new site is established, the person requesting the new site needs to inventory all project and NWIS databases to identify potential duplicate sites or data. Data are checked and compared or verified with the field notes, laboratory sheets, NWIS databases, and reports. NWIS-Web may be an effective tool for checking for duplicate sites. Consult the District Database Manager for the latest duplicate checking method.

The person requesting the new site runs computer programs (GWSI tables and/or GIS) that retrieve nearby sites within a given radius (1-5 miles) of the proposed new site. For help with the GWSI retrieval, contact the District database homepage or the GWSI DBA for instructions. All data in NWIS databases for nearby sites are reviewed to determine if the proposed new site should be added to the Site File or if an appropriate (duplicate) site already exists. Check the table for similar owner’s name or well numbers. If a duplicate site is identified or suspected, the instructions given in DMP 5 (Data merges and deletions) will be performed by the staff in coordination with the GWSI DBA.

4. Naming the Site

4a. Ground water (well or spring)

In Maryland and Washington D.C., ground-water wells are assigned well numbers by the GWSI DBA based on County name and 5-minute quadrangle. Well names in Delaware are further defined by 1-minute quads and are assigned by the Delaware Geological Survey.

4b. Surface Water (stream or lake)

Surface-water sites or station names are typed in capital letters and consist of a unique identifier based on location. The name must include the name of the stream or water body and include the words “AT” or “NEAR” and the name of the nearest named community on a topographic map (scale 1:24,000).

• Use “AT” when the site is within 1 mile of the named community.

• Use “NEAR” when the site is more than 1 mile from the named community.

• The two-letter postal abbreviation code for the State of the named community is the last part of the site/station name.

Example of a correct site name:

01578310 SUSQUEHANNA RIVER AT CONOWINGO, MD

Notes:

• For sites located near the Maryland-Delaware-D.C. State or District border, the nearest named community may be in a neighboring state.

• Special quality-assurance/quality-control sites may deviate from this naming convention.

• Latitude, longitude, aquifer type, or well depth should not be used in the site name. This information is stored elsewhere in the Site File.

• For unnamed tributaries (no name shown on any maps), name the site by first identifying the stream, lake, bay, or ocean to which it flows, then add the word “tributary,” then reference the site to the nearest town. Using this method will provide immediate reference to the major water body to which the unnamed tributary flows. Example: UNNAMED TRIB TO PATUXENT R NR HOLLYWOOD, MD

• For more than one unnamed tributary to a body of water, further identify the site with a sequence number in the order the sites were established: UNNAMED TRIB 2 TO PATUXENT R NR HOLLYWOOD, MD

The preliminary site name determined by the project staff will be approved by the GWSI DBA or Data Section Chief before entry into the GWSI site file, and before transferring the site location to the master surface-water site-location map.

5. Coding and entering data to GWSI (see also DMP 4 for data entry options)

Essential information about the location, identity, data accuracy, and characteristics of a well, surface-water station, or water-quality sampling site are stored in the GWSI Site File. Each site should have a complete GWSI coding form 9-1904-A, which includes the date and name of the person coding the form, checking the data, and entering the data. Required fields are listed in Appendixes C and D.

The person requesting the establishment of the new site uses GWSI to enter all necessary Site-File data into NWIS under the supervision of the GWSI DBA. All pertinent information available such as comments to aid future users of the data should be included in GWSI. Incomplete records make the data difficult to use for GIS and modeling. For help in completing the GWSI coding form or in using GWSI, consult the instruction manual or the GWSI DBA. Instructions and coding forms for GWSI are available on the web on the District Database homepage or at the following URLs:

Ground-Water Site Inventory User’s Manual

http://nwiqqvarsa.er.usgs.gov/conversion/nwisdocs3_2/gw/GW.user.book.html.

GWSI/Site File/SW Station Coding Forms

/conversion/nwisdocs3_2/gw/gwforms.html Forms

After the form is coded and the data entered into GWSI (DMP 4), the EDIT GWDATA program (MAIN MENU OPTION 3 of GWSI) should be run to check for errors that are stored in the ‘errfile’ (ex. errfile.db01.a ) and correct any identified errors. If the error cannot be resolved, consult the GWSI DBA. If there are no errors, the input file should be copied to the WATIN directory (OPTION 9 on the main GWSI menu). The GWSI DBA updates or writes the data to the GWSI database (OPTION 4) and files a paper copy of the input file and records the date and originator of the file.

6. Error checking (see DMPs 3 and 5 for checking for duplicate sites and data)

Retrieve the data from GWSI after it has been entered (DMP 4), print the table, and check it against the original GWSI coding form. The input file can also be checked, but checking the retrieval is more accurate. Write your name and date on the printed copy and include this with the original coding form to show the data has been checked.

7. Plot the site on the Master Site-File Map

Once the site ID and station name have been established for a new site, the location of the new site will be transferred from the project work map to the master site-location map (this may be done digitally; check with the GWSI DBA). The well name is plotted at the upper right of the symbol, or in the closest available space with a connecting line.

The following information will either be recorded in the GIS coverage or printed neatly in the margin of the master map:

1. Well name.

2. Site ID (5-character agency code followed by 8- or 15-digit site number).

3. Station name (exactly as it appears in the Site File).

4. Site type (with the following abbreviations: GW, ground water other than spring; SP, spring; LK, lake; SW, stream; SS, specific source; or ME, meteorological).

5. Project number (9-digit number: 4424 followed by the 5-digit project number).

6. The date the site was plotted on the Master Site-File topographic map (format: MM-DD-YYYY).

7. The initials of the person plotting the site.

8. Filing or storing originals

Original field notes, a copy of the site plotted on a topographic map, and the GWSI coding forms are stored in the fireproof file cabinets in the District library or in the Data Section according to site or station name (DMP 3).

References

U.S. Geological Survey, 1997, Office of Ground Water, A Quality-Assurance Plan for District Ground-water Activities of the USGS, Open File Report 97-11, GWPD 5.

U.S. Geological Survey, 1985, WRD Data Reports Preparation Guide, by Charles E. Novak. ö

DMP 4: Ground-Water Site Inventory Data Entry and Checking Instructions

Ground Water Site Inventory (GWSI) is the NWIS (Unix based) program that stores site information for ground water, surface water, and water-quality sites. GWSI also stores well data, including well-construction information and water level information.

This document explains three ways to enter data into GWSI:

1. Query Entry (GWSI Code/Option 1),

2. Full-Screen Entry (GWSI Code/Option 2), and

3. Modify a template using an editor.

Query Entry and Full-Screen Entry do not directly update the database; they generate the input file that needs to be processed through GWSI options 3 and 4 (below) to update GWSI. The input files created will be in the directory where you start GWSI. If you are using a control file or a prompt file, it is easiest to be in the directory where these files reside. The third method requires that an input file has already been created or needs to be generated. Below is a table comparing the advantages and disadvantages of the three methods.

Data Entry Method	Requirements	Advantages	Disadvantages
Query Entry	Prompt file	Quick, less keystrokes (and wrist pain). You are only asked for the fields you specified in the prompt file.	Need to know the Site ID and prompt file name and location.
Full Screen Entry	Strong wrist	Simple. Choose from menus.	Need to hit the ‘return/enter’ button repeatedly and switch between menus often. Therefore, slower.
Template	Template file Know how to use an editor	Fairly quick, depends on the editing program used. Don’t need to remember the Site ID, only the well name.	Need to know how to use an editor. Errors may go unnoticed; for example you could put the water level with the wrong site or date.

Note: Ctrl C or P usually let you escape GWSI if you are stuck. ---The type in Courier is directly from GWSI. Type 'GWSI' at the Unix prompt and the following command line appears:

Enter UNIX Command or Select Program Code: ‘Enter’ activates the Main Menu

Code Program Description Code Program Description

---- ------------------- ---- -------------------

1 : Query Entry (gwinput)

2 : Screen Entry (hdrinp)

3 : Edit GW Data (from 1-2) 7 : Edit GW Data in Batch

4 : Update GW Data (from 3) 8 : Update GW Data in Batch

5 : Update Sitefile Only (runs 2,3,4)

6 : Retrieval/Tables (gwtable)

9 : Copy File (from 1-2) to Directory watin

10 : Plot Hydrographs (gwhgraph)

95 : Utilities Menu

96 : Documentation Menu

97 : Local Menu

98 : Exit to Previous Menu

99 : Exit to UNIX

Method 1: Query Entry

Choose Code/Option 1 from the GWSI Main Menu.

PROGRAM GWINPUT REVISION NWIS_3_2+19991101

***** Loading Edit Tables *****

***** Please Wait *****

ENTER AGENCY CODE FOR THIS SESSION [?]? Type in USGS (case does not matter).

FOR CARDS GENERATED BY THIS PROGRAM,

(DO NOT ADD ON WITH A DIFFERENT AGENCY CODE)

ENTER OUTPUT FILE (Terminal=*)? Type the name of the data file you will be creating.

ENABLE TRANSACTION CODE "BEEP" (Y/N) [?]? Usually ‘N’; Your neighbors will appreciate the silence.

DO YOU WANT PROMPTS FOR EVERY COMPONENT (Y/N) [?]?

Type ‘N’ if you want to create or use an existing prompt file.

USE PREVIOUSLY SAVED COMPONENT LIST (Y/N) [?]?

‘Y’ If you have already created the prompt file.

‘N’ If you have not already created the prompt file (instructions follow).

ENTER INPUT FILE? wl_prompt The name of your prompt file. Make the filename meaningful.

GWSI editing commands:

"Q" OR "QUIT" TERMINATES PROGRAM WHEN ENTERED FOR SITE-ID,

"=" DUPLICATES PREVIOUSLY ENTERED SITE-ID,

"END" COMPLETES SITE EARLY AND PROMPTS FOR NEXT SITE-ID,

"OOPS" OR "OOPS C#" CHANGES PROMPT ORDER,

AN "UP ARROW", OR "CURSOR UP" KEY MAY BE USED IN PLACE OF THE WORD "OOPS",

WARNING: MISUSE OF "OOPS" OR "END" CAN SKIP MANDATORY FIELDS,

"?" MAY PROVIDE CODING LISTS OR ADDITIONAL INFORMATION,

"DEL" DELETES AN EXISTING FIELD IN AN EXISTING SITE,

"ABT" DISCARDS ALL DATA FOR CURRENT SITE,

"CARRIAGE-RETURN" SKIPS A REPEATING GROUP OR NONMANDATORY ENTRY.

PROMPTS FOR MANDATORY FIELDS ARE IN UPPER CASE.

WARNING MESSAGES ARE ENCLOSED IN DASHES, AND

FATAL MESSAGES ARE ENCLOSED IN ASTERISKS.

1) SITE ID (C1)(CHAR X(15))? _______________

This is the point where you begin entering data. For ground water sites, the site ID is usually the latitude/longitude with a sequence number. If the latitude or longitude is ever modified, the site ID will remain unchanged because it may have been published. You will now be prompted for the fields requested in the prompt file you created. If there is something you want to change, you can try to edit the prompt file with an editor, but it is probably easier to either recreate the prompt file, or use full screen entry to add the additional data.
Creating a prompt file:

It takes only a few minutes to create the prompt file, and it can save you (and your wrist) time and pain in the long run. Enter Y for the fields you want, and N for the fields you want to skip. For a field such as construction data that has several subcategories, if you say Y, you will then be asked for the subcategories, such as HOLE, CSNG (casing), and OPEN (opening).

Type the following to create a prompt file:

ENTER AGENCY CODE FOR THIS SESSION [?]? usgs_

FOR CARDS GENERATED BY THIS PROGRAM,

(DO NOT ADD ON WITH A DIFFERENT AGENCY CODE)

ENTER OUTPUT FILE (Terminal=*)? datafile

ENABLE TRANSACTION CODE "BEEP" (Y/N) [?]? n

DO YOU WANT PROMPTS FOR EVERY COMPONENT (Y/N) [?]? n

USE PREVIOUSLY SAVED COMPONENT LIST (Y/N) [?]? n

SAVE COMPONENT LIST FOR FUTURE USE (Y/N) [?]? y

FOR COMPONENT LIST TO SAVE ON DISK,

ENTER OUTPUT FILE? my-promptfile (name the file something meaningful for future use)

5) Project No. (C5)(CHAR X(12))

DO YOU WANT A PROMPT FOR THIS COMPONENT (Y/N)?

After the prompt file is created, you will be prompted to input data. The data will be stored in the file you named on line 4 above. You may have several prompt files for different uses.

Method 2: Full Screen Entry

Type ‘2’ at the GWSI main menu. The file created will be named “d.userid.001” (sequential numbers). You may change the filename at this point.

Below is an example of the first screen of site information that appears after you type in the site ID. If mandatory fields have not been completed, GWSI will not let you proceed to the data fields before the site information is complete. Notice the GWSI editing commands at the bottom. A ‘?’ will list the available options for that field.

First screen of GWSI site file:

***** General Site Data *****

Agency Code USGS Site ID 392721076150301 Project No. 1=4424-08700__

Station Name 2=HA Dd 91

Latitude 3= 392721 Longitude 4= 0761503 Seq. No. 5=01

Lat-Lon Accuracy 6=S Lat-Lon Method 7=M Lat-Lon Datum 8=NAD27

District 9=24 State 10=24 County 11=025 Land Net 12=

Map Name 13=EDGEWOOD, MD Map Scale 14= 24000

Altitude 15= 19.73 Accuracy 16= 10 Method 17=L Datum 18=NGVD29

Hydrologic Unit Code 19=02060003 Drainage Basin Code 20=

Topographic Setting 21=F Agency Use 22=A Date Inventoried 23=02-01-1988

Station Type 24= Y Data Type 25= A

1234567890ABC 1234567890ABCDEF

Instruments 26= National Water Use Code 27=

1234567890ABCDEF

Remarks 28=Well is located at SW corner of building.

Mean Greenwich Time Offset 29=-05 Local Standard Time Flag 30=Y

Web-ready Flag 31=Y

Optns S.Fld N.Fld L.Fld Repnt In:Ed Abort End Blank Ins.C Del.C No.Ctrl Ys.Ctrl

? $ > < % and ! * # _ \ " ^

Second screen of data fields for a ground-water site:

***** Ground-Water Site Data *****

Agency Code USGS Site ID 392721076150301 Project No. (1)=4424-08700

Data Reliability 38=C Site Type 39=W

Date of Construction 40=02-01-1988

Use of Site 41=O Secondary Use of Site 42= Tertiary Use of Site 43=

Use of Water 44=U Secondary Use of Water 45= Tertiary Use of Water 46=

Aquifer Type 47= Primary Aquifer 48=112TLBT

Hole Depth 49= 154 Well Depth 50= 78 Source of Depth Data 51=D

Second screen of data fields for a surface-water site:

***** Surface-Water Site Data *****

Agency Code USGS Site ID 01578310 Project No. (1)=442400300

Base Discharge 32=_____.__

Drainage Area 33=27100.00 Contributing Drainage Area 34=

Crest-Stage Upstream Elev 35= Crest-Stage Downstream Elev 36=

Gage Height at Zero Flow 37=

Water-level entry screen in full screen entry.

***** Water Level Record Selection *****

Agency Code USGS Site ID 392721076150301

Measurement Date MM-DD-YYYY Time Water Level Measured

>>>>> "00-00-0000"=No More Water Levels

Are these Items Correct? Y

Notice that you type 00-00-0000 if you have no more water levels to enter and you want to return to the GWSI menu. You do not need to type the dashes, only 8 zeros.

After you put in a date, it will come back with the following screen.

Agency Code USGS Site ID 392721076150301

Measurement Date 01-01-1999 Time Water Level Measured

Water Level (from Land Surface) 1=____.__ Status 2=

Method of Measurement 3= Reference 4= Accuracy 5=

Source 6= Party ID 7=

Web-ready Flag 9=

Edit Which Item (0 = Store)? 0_

If you need to go back to change an entry, type in the number associated with that field. For example, ‘7’ for Party ID; ‘0’ if you are finished.

To enter other types of data:

· If you have other data to enter for this site, choose a number from 3-10.

· If you want to select a new site, choose option 2. The data will be appended to the current file.

· If you want to exit the database, choose option 1.

1 Exit HDRINP Program

2 Select New Site

3 General Site Data Record

4 Construction Data Record

5 Miscellaneous Data Record

6 Discharge Data Record

7 Geohydrologic Data Record

8 Hydraulic Data Record

9 Water Level Data Record

10 Observation Data Record

Select Record Type (I): 1_

Method 3: Modifying a Template:

Below is the GWSI input file “d.wsmcpher.003”. The number preceded by a = or # sign is the GWSI computer code for that field. Using an editor, modify the water-level information (C235 and C237). You may be able to do a global change (find/replace) on the date. You may also use a template that has been generated by another user.

XXXXX

USGS 392721076150301 R=234* T=A* 235#19990101* 243=L* 237= 20* 239=T*

USGS 392721076150301 246=WSM*

Checking the Input File:

Once the datafile is created, choose code/option 3 (Edit GW Data (from 1-2)) from the GWSI Main Menu.

Enter UNIX Command or Select Program Code: 3

Your current GW data base is number 01

NWIS EDIT PROGRAM

RELEASE VERSION NWIS_3_2+19991101

DATA BASE NUMBER: 1

INPUT FILE NAME IS d.wsmcpher.003 Type in the data file name.

ENTER BATCH ID, VALID OPTIONS ARE 0-9, A-Z x

Use any number or letter. It will be used as a suffix on the files created for error checking/input to GWSI. The files may be removed if there are no errors after the file is copied to the WATIN directory or written to the database. Beware if you do a wildcard delete that one of your files doesn’t end in that same letter or number. It is usually safe to call it ‘x’ and ‘rm .x’.

Deleting existing Batch files

***** Loading Edit Tables *****

***** Please Wait *****

Processing data - please be patient

END OF INPUT FILE--CHECK errfile.db01.x

Press <Enter> for Menu or Enter UNIX Command:

Check the error file (more errfile.db01.x)at the GWSI or Unix prompt.

If there is an error, WARNING or FATAL will appear.

This is how the next screen should appear:

Error messages for input file d.wsmcpher.003

Line Error

Num Num First line of input for record being processed

This is what you want to see! There are no errors.

If there are errors, you can edit the input file using an editor, or re-enter the information. It is possible to change the data after it is input or written to the database, but this step may be forgotten. If there are no errors, you are ready to copy the file to the WATIN directory. Choose Code/Option 9 from the GWSI Main Menu.

Copy data file to the WATIN directory:

If you are working from a remote office, you may need to telnet to the computer where the NWIS programs are stored.

Enter UNIX Command or Select Program Code: 9 Choose option 9

Enter file name to be copied: d.wsmcpher.001

You will be asked if you want to delete your copy of the input or data file. It is suggested that you keep a copy of this file, especially if it is large, until at least the next day so that the file can be backed up in case something happens before the data is written to the database. The GWSI DBA removes the file from the WATIN directory once the data has been written to the database, which is usually the same day, and therefore this file is not backed up digitally, although it is printed.

Data Retrieval and Checking:

The data needs to be checked after it is entered. You can print the input file and check the data before sending the file to WATIN, and/or do a GWSI retrieval (preferred) and check the data. This way, you are checking what is actually in the database. For the GWSI retrieval (Code/Option 6), you will need the code number for the field you want to retrieve, such as C237 (water level). You can either look at the input file for these codes, look at the numbers on the coding form, or refer to the GWSI documentation for the codes. A control file (xx.ctrl) is created when you do a retrieval and can be used for later retrievals using ‘TC’ for terse control.

Press <Enter> for Menu or Enter UNIX Command: 6

Your current GW data base is number 01

GWSI RETRIEVAL/TABLING - NWIS_3_2+19991101 ENTER SET-UP PARAMETERS --

Enter "?" if you need help to respond to queries:

Enter set-up parameters (T/V,I/C/R,<CR>=TI): ?

GWSI RETRIEVAL/TABLING - NWIS_3_2+19991101 ENTER SET-UP PARAMETERS --

You must specify one of two options for level of detail you require:

(T) Terse, minimum explanation will be provided.

(V) Verbose, detailed explanation will be provided.

You must also specify one of three options for generating

the parameters required for this program:

(I) Interactive, you will be prompted to provide all necessary data.

(C) Control file, required data will be read from a control file

which was created in a previous run of this program. You will be allowed to over-ride any data obtained from the control file.

(R) Resume after phantom/batch, no processing required, but use this program to display/print output from previously processed phantom/batch job.

For example, if you want detailed explanations (verbose) and were processing interactive you would enter "VI".

Type a ‘?’ at the prompt to display definitions of the options.

Your current GW data base is number 01

GWSI RETRIEVAL/TABLING - NWIS_3_2+19991101 ENTER SET-UP PARAMETERS --
Enter "?" if you need help to respond to queries:
Enter set-up parameters (T/V,I/C/R,<CR>=TI):

Enter root path name (<CR>=gw): This is the suffix for the files created.

GWSI RETRIEVAL/TABLING - NWIS_3_2+19991101 GROSS SITE SELECTION --

Which field do you wish to use for gross selection of sites (1-11)? ?

You must choose one of the following site file fields
to be used for gross selection of sites --
(1) Agency with site ID (C4andC1)

(2) State-County (C7andC8)

(3) Primary Aquifer (C714)

(4) Hydrologic Unit (C20)

(5) Water Use (C24)

(6) Project Number (C5)

(7) Drainage Basin (C801)

(8) Use of Site (C23)

(9) Station Name (C12)

(10) Latitude range (C9)

(11) Longitude range (C10)

You will later be given an opportunity to further qualify your selection by specifying a latitude-longitude boundary and/or by specifying tests to be performed on any GWSI fields.

To retrieve all the data for one site, select either option 1 (Agency with site ID (C4 and C1)) or option 9 (station name (C12)).

Which field do you wish to use for gross selection of sites (1-11)? 9

GWSI RETRIEVAL/TABLING - NWIS_3_2+19991101 GROSS SITE SELECTION --

SELECTION BY STATION NAME --

Do you wish to load gross select keys from a file (Y/N,<CR>=N)?

Enter Station Name (up to 24 chars, case-sensitive): BA Dc 444

Enter Station Name (up to 24 chars, case-sensitive): Press enter if no more sites are to be retrieved.

Defining the retrieval

GWSI RETRIEVAL/TABLING - NWIS_3_2+19991101 QUALIFY SITE SELECTION

Current limitations to site selection --

(1) Polygon: Sites are not restricted by latitude-longitude polygon

(2) Detail tests: Sites are not restricted by detail testing

(3) Site types to be included: (SP) Spring

(GW) Ground water other than spring

(4) Maximum number of sites to retrieve by gross select (0=no limit):0

(5) Max no sites to pass polygon, detail and type tests (0=no limit): 0

(6) Maximum number of records to output for tabling (0=no limit): 0

Enter item number to change, R to re-list items or <CR> to continue:

This retrieval is set for Spring and Ground-Water sites. This will need to be changed for another type of site, such as a Surface Water (SW) site.

Specify format (1=Std, 2=Dump 3=Subfile, 4=Special (<CR>=1): 2

See Appendix F for examples of table formats.

Which field set do you wish to use (1=Default, 2=Select, 3=All)? 3

If the site has historical water levels, you may want to limit the retrieval in the output.

Enter field (or !field) to exclude or <CR> to continue:

Loading fields ...

Do you wish to print empty fields (Y/N,<CR>=N)?

Do you wish to restrict output of related files (Y/N,<CR>=N)?

The output can be restricted using option 14. Example: C235 GT 20001105 (water levels after Nov. 5, 2000).

Review Tabling Options

GWSI RETRIEVAL/TABLING - NWIS_3_2+19991101 REVIEW FORMAT OF OUTPUT --

Current output format specifications --

(01) Table type: 2 (Dump) If “All” was chosen, all the fields will be listed.

(02) File name: gw.table

(03) Title:

(04) Print destination:

(05) Forms page length: 58

(06) Round numeric values on output? Y

(07) Rounding exceptions: (none)

(08) Rounding for component C016: from data dictionary

(09) Rounding for component C237: by component C276

(10) Force upper case? N

(11) Print empty fields? N

(12) Page break on site change? N

(14) Output of related files is not restricted.

(15) Output will not be sorted

Enter item number to change, R to re-list items or <CR> to continue:

If you need to change any of the specifications you can use the following options. Otherwise, press enter to continue.

Enter review/modify parameters (C/R/M,GPDLFSTA,<CR>=C): ?

At this time you may specify one of three options:

(R) Review current specifications

(M) Modify selected specifications

(C) Continue (set-up is complete)

If you specify R or M you must also specify one or more of the following:

(G) Gross site selection

(P) Polygon site selection

(D) Detail site selection

(L) Limit retrieval by site type, number sites/records

(F) Format of output

(S) Sorting specifications

(T) Temporary fields (review only)

(A) All

For example, if you wished to review gross site selection and sorting

specifications, you would enter "RGS".

GWSI RETRIEVAL/TABLING - NWIS_3_2+19991101 SPECIFICATIONS COMPLETE.

Enter name of program control file (<CR>=gw.ctrl):

Enter processing parameters (I/P/B/R/Q,S,@..,<CR>=I): ?

Screen showing GWSI retrieving data from NWIS. Shows number of sites and records output.

Enter processing parameters (I/P/B/R/Q,S,@..,<CR>=I):

PROCESSING GWSI FILES ...

SORTING THE WORK FILE ...

FORMATTING TABLE/FILE ...

TABLE IS READY IN THE FILE: gw.table

NUMBER SITES RETRIEVED BY GROSS SELECTION: 1

NUMBER SITES PASSING SITE TYPE, POLYGON AND DETAIL TESTS: 1

NUMBER RECORDS OUTPUT FOR TABLING: 1479

To examine the output on the screen, print the file from the GWSI or Unix command for checking the data.

Enter file disposition parameters (C/R/S/X,D/E,<CR>=C): r (shows the file on the screen)

GWSI RETRIEVAL/TABLING - NWIS_3_2+19991101 gw.table

DATE: 07/07/00 1

C001 Site ID (station number) 392931076410301

C002 Type of site W

C003 Record classification C

C004 Source agency code USGS

C005 Project number 442400200

C006 District code 24

C007 State code 24

C008 County code 005

C009 Latitude 392931

C010 Longitude 0764103

C011 Lat-long accuracy code S

C012 Local well number BA Dc 444

C014 Name of location map COCKEYSVILLE

C015 Scale of location map 24000

C016 Altitude of land surface 390

C017 Method altitude determined M

C018 Altitude accuracy 10

C019 Topographic setting S

More (Y/N,<CR>=Y)? n

IMPORTANT: Check the data and include your name and date on the printout to verify the data has been checked. File this “signed” sheet with the data. It is important to check the data promptly since the data is readily available on the World Wide Web (NWIS-Web). ö

DMP 5: Data Merge and Data or Site Deletion

Duplicate sites and duplicate data in a database can reduce its usefulness and credibility. To effectively manage the databases, a systematic method for merging data and deleting sites is required when duplicate sites or erroneous data exist.

When establishing a new site, the person requesting the new site needs to inventory all project and NWIS databases to identify potential duplicate sites or data, by retrieving a table from GWSI showing all sites within an appropriate range (1-5 miles). Check the table for similar owner’s names or well numbers. NWIS-Web may be an effective tool for checking for duplicate sites; consult the District Database Manager for the latest duplicate checking method.

Duplicate Sites

If a duplicate site is suspected, the person requesting establishment of the new site and the GWSI DBA must attempt to verify the location of the old site and associated data by checking all USGS reports, old project paper files, ground-water-quality records in the District library, and County ground-water reports prepared by other agencies.

If the old site and data cannot be verified and if a new site must be established, the value of retaining the old site and data needs to be determined; older sites may be poorly located and the data may be incomplete or unreliable. Factors to consider include the amount, age, source agency, types, and quality of the data.

The GWSI DBA, the person requesting establishment of the new site, the Project Chief, and the Discipline Specialists (DS) must decide together if:

1. The existing site should be used, and the new data included with this site,

2. A new site should be established,

3. The old site should be deleted, and

4. Any existing data contained in NWIS should be merged into the new site.

Reminder: New sites must be plotted on the Master Site-File topographic maps, and a copy of the site location, including the quad name, should be made and placed in the site folder. This is the responsibility of the person establishing the site and the location will be checked by the GWSI DBA.

Data Merge

If two or more sites are co-located, the data needs to be merged. Data merges should occur only when different data exist at duplicate sites. If the old site can be verified from reports, District library paper files, or any other means previously discussed, the Site File of the old site must be updated to the maximum extent possible. The source of the verification and the name of the person who made the verification should be entered in the Remarks Record of the MISCELLANEOUS FILE in GWSI. This is the responsibility of the GWSI DBA.

The person requesting the site ID or site name change will provide the following information to the DBA for the SITEFILE.CHANGES.LOG:

1. The old site ID,

2. The new site ID,

3. The reason and date of the change,

4. The person requesting the change, and

5. What, if any, data were merged (sample dates, record numbers).

Changes and/or deletions of an existing site ID or site name will only be made by the GWSI or ADAPs DBA. Data merges and deletions will be made by the DBA for the specified discipline (SW, GW, QW). Data are merged by changing the old site ID to a new site ID (all data stored under the old site ID will be stored under the new site ID) or by moving the data and deleting the less accurate site. If data are moved to a new site or merged with an existing site, the original site ID will be identified in the remarks field (C806) of the General Site Data Record and annotations will be made to current project files (station folders, discharge measurement forms, inspection forms, GWSI forms, etc.). This is the responsibility of the project staff and GWSI DBA.

Water-quality records that can be verified should be updated to the maximum extent possible. Updating must include the Water Data Storage and Retrieval System (WATSTORE) parameter code 00029 with the correct 5-digit project number. Water-quality data moved to a new site or otherwise combined should state the original site ID, the source of the verification, and the initials of the person who made the verification in the remarks field of the WATER QUALITY RECORD HEADER. Annotations should also be made to the paper files. This is the responsibility of the Water-Quality (QWDATA) DBA.

Data Deletion

Data deletions should occur only when there are duplicate or erroneous data at an individual site. If a site or data are deleted because of a lack of confidence in or an inability to verify the data, paper copies of the Site-File information and related NWIS data will be printed and filed under the old site ID in the District library. This is the responsibility of the GWSI DBA and the person requesting establishment of the new site.

Site Deletion

A site will only be deleted when:

1. A site header exists with no data in any database and is not referenced in a USGS report.

2. A duplicate site exists with duplicate data and the data has been merged.

Reference

U.S. Geological Survey, 1997, Office of Ground Water, A Quality-Assurance Plan for District Ground-water Activities of the USGS, Open File Report 97-11, GWPD 5. ö

DMP 6: Maintenance of Water Quality (QW) Files

While a project or network is active, the water quality files for each data-collection site are maintained in folders in the office of the project or network staff. The folders will contain all the information necessary to verify data in a report or the QWDATA database within the National Water Information Systems (NWIS). Data are recorded on field sheets, National Water-Quality Laboratory (NWQL) lab printouts, Analytical Service Requests (ASRs), and in NWIS. This DMP specifies procedures for managing and maintaining water-quality files from the NWQL. DMP 7 gives guidelines for processing data from non-USGS labs. Consult the District Archiving Policy Document and DMP 14 for archiving of water-quality files.

Each sample sent to the NWQL will include a properly completed USGS NWQL ASR. A copy of the ASR shall be retained for data management purposes. Additional information concerning the ASR is contained in various NWQL Technical Memorandums (e.g. 95-02, 95-04, and Appendixes G and H). Appendix J lists codes needed to complete the ASR.

Samples must be logged into QWDATA as soon as possible to prevent data from going into “badqw”--preferably within 24 hours. Log in sample by entering information from ASR and field sheets into the NWIS QWDATA Menu program prior to shipment (instructions below).

Under special circumstances, these data may be entered after a sample is logged into the computer. These circumstances include time needed to analyze geologic and hydrologic data in order to determine geologic unit and aquifer type. The Project Chief or staff will not be allowed access to the analytical results until all pertinent information has been entered in the computer.

Project staff should review the chemical analysis (especially nutrients) promptly so that requests for reruns or verification of laboratory analyses can be performed. For example, nutrients must be rerun within a month from the date of collection. Discrepancies must be resolved, corrected if possible, and all actions documented in the Site-File folders and NWIS databases. Any delay may compromise the validity and/or quality of the data.

Instructions

1. Log Samples into QWDATA

• Separate the ASRs into: Database 01 (environmental samples), Database 02 (proprietary), and Database 33 (Quality Assurance (QA) samples). Log all Database 01 (DB 01) samples in at one time before entering the QA samples because you will need to switch databases in order to log in your QA samples. Specific information from the ASR forms will be needed for each sample you log in.

• At the Unix prompt, type "qwdata 01" to enter the QWDATA SYSTEM, database 1.

(Type in Courier font is directly from QWDATA.)

QWDATA Main Menu

QW DATA PROCESSING ROUTINE REV NWIS_3_2+19991101

YOU ARE USING WATER-QUALITY DATABASE NUMBER 01

QW SYSTEM OPTIONS

1 -- LOGIN SAMPLES 4 -- CHECK SUPPORT FILES INCLUDING

List Sites, Access Parameter,

Code Dictionary, Access Geologic

Unit Code and State/County Files.

2 -- ADD / CHANGE / DELETE 95 -- WATER QUALITY UTILITIES OPTIONS

Enter field or

miscellaneous data

Edit or flag samples,

Count QW records, or

Update Sitefile.

3 -- RETRIEVE SAMPLES 99 -- EXIT TO SYSTEM

Check entry or make

loglist, Locate samples,

Provide cation/anion

balance, Make tables or

PSTAT data set.

Please enter a number from the above list or a Unix command: 1

Choose Option 1 - "Login Samples"

Login Sample

(Use the information from the ASR for the next 18 steps)

(1) AGENCY CODE: USGS_ (2) STATION NUMBER: 392357076183601

(3) BEGIN DATE: 20000309 (4) BEGIN TIME: 1315

(5) END DATE: ________ (6) END TIME: ____ (7) MEDIUM CODE: 6

(8) HYDROLOGIC CONDITION: 9 (9) SAMPLE TYPE: 9 (10) HYDROLOGIC EVENT: 9

(11) PROJECT NUMBER: 442419400 (12) ANALYSIS TYPES: ch_____________

(13) GEOLOGIC UNIT CODE: ________ (14) DATA CATEGORY: QW

(15) COLLECTING AGENCY (00027): _1028 (16) ANALYZING AGENCY (00028): _1028

(17) REMARKS: __________________________________________________

(18) ANALYSIS STATUS: H(19) ANALYSIS SOURCE: 9 (20) LAB NUMBER: 9

ENTER WITH NO INTERVENING BLANKS

TO CHANGE ITEMS ABOVE, PLEASE ENTER ITEM NUMBER (99 TO CONTINUE) :

The following instructions refer to the numbers on the screen above.

Component Number	Component	Remarks
1	AGENCY CODE	Usually USGS (press return/enter key).
2	STATION NUMBER	Enter the Site ID (8 or 15 digit number).
3	BEGIN DATE	4-digit year, month, and day.
4	BEGIN TIME	Eastern Standard Time.
5	END DATE	Press return/enter key unless it is a composite sample.
6	END TIME	Press return/enter key unless it is a composite sample.
7	MEDIUM CODE	Found on ASR form.
8	HYDROLOGIC CONDITION	Found on ASR form.
9	SAMPLE TYPE	Found on ASR form.
10	HYDROLOGIC EVENT	Found on ASR form.
11	PROJECT NUMBER	9 digit project code (ex. 442411900).
12	ANALYSIS TYPES	Make choices based on schedules requested Valid analysis-type codes are: CH -- chemical ME -- metals BI -- biological NU -- nutrients PE -- pesticides RA -- radiochemical SE -- sediment BE -- bed material
13	GEOLOGIC UNIT CODE	For ground-water samples, same as aquifer code (see GWSI DBA for list).
14	DATA CATEGORY	Usually QW (default).
15	COLLECTING AGENCY (00027)	Usually USGS (1028).
16	ANALYZING AGENCY (00028)	Usually USGS (1028).
17	REMARKS	Copy the "remarks" from the ASR.
18	ANALYSIS STATUS	Usually the default value unless otherwise shown on the ASR.
19	ANALYSIS SOURCE	Leave as 9.
20	LAB NUMBER	Press return/enter.

Enter Field Data

DO YOU WANT TO ENTER FIELD DATA FOR THIS RECORD (YES OR NO)? Yes

DO YOU WANT PRECISION CODES TO BE

1 -- DETERMINED BY THE PARAMETER CODE DICTIONARY (PCD) Usually 1

2 -- SET TO THE PRECISION OF THE VALUES YOU ENTER

PLEASE ENTER 1 OR 2 (OPTION 1 IS GENERALLY CORRECT) 1

PLEASE ENTER NUMBER OF FIELD FORM:70 The field form below is for ground water

Select a field form from the choices below the first time through:
70 =Ground water samples,
71 =Surface water samples, or
72 =Quality Assurance (QA) samples.

00029 PROJECT NUMBER ________71999 SAMPLE PURPOSE _______

50280 PURPOSE OF SITE VISIT _______ 99111 QC SAMP ASO W/ENV SAMP _______

84164 SAMPLER TYPE _______ 82398 SAMPLER METHOD _______

72019 STATIC WTR LVL (FT BLS) _______ 72004 MIN. PUMP BEF. SAMPLE _______

00059 YIELD WHEN SAMPL, GPM _______ 72015 DEPTH, TOP SAMPLE INT _______

72016 DEPTH BOT SAMPLE INT _______ 00010 WATER TEMPERATURE (C) _______

00020 AIR TEMPERATURE (C) _______ 00025 BAROMETRIC PRESSURE _______

00095 SPECIFIC CONDUCTANCE _______ 00300 DISSOLVED OXYGEN _______

00400 pH _______ 00419 ANC, IT (RAW) _______

00450 ANC BICARB. IT _______ 39086 ALKALINITY, FILTERED _______

00453 BICARB, FILTERED _______ 00076 TURBIDITY _______

Press return/enter several times for each parameter (allows you to enter a set of codes for each parameter) to complete the form and only insert values where you have data. If you make a mistake you can re-select the parameter number after you have stepped your way through the entire list.

PLEASE ENTER PARAMETER CODE TO CHANGE OR ADD (99 TO END) 00029

After you have entered all field values/parameters, choose 99 to end and the program will assign an 8 digit "Record Number" to the sample you just logged in.

RECORD ENTERED - RECORD NUMBER = 00000571

IMPORTANT: Write the record number on the ASR form in the box at the top labeled "NWIS RECORD NUMBER" and on the field sheet. Make copies of the ASR and give the original to the QWDATA Database manager.

ANOTHER RECORD (YES OR NO)? Yes

DO YOU WANT TO EDIT THE SAME HEADER (YES OR NO) ?

When all environmental samples for DB 01 are finished, type 99 to exit QWDATA and then type "qwdata 33" to log samples into the QA database. Check the top of the screen to be sure you are in Database 33. Follow the LOGIN instructions as listed above.

Note: It is very important to log samples into the correct database. If you make a mistake, please inform your QWDATA DBA immediately.

2. Check your Log-In Information.

Using “check QWDATA,” print out a copy of your login information, check your login entries, staple this to your original ASR forms and your original field forms and alkalinity sheets, etc. and give them to the QWDATA DBA. Keep copies for your records in your project site files.

1. Enter QWDATA main menu (type "qwdata 01 or 33" depending on field data or QA).
2. Choose Option 3 - "RETRIEVE SAMPLES".

QW DATA PROCESSING ROUTINE REV NWIS_3_2+19991101

YOU ARE USING WATER-QUALITY DATABASE NUMBER 01

RETRIEVE SAMPLES OPTIONS

1 -- CHECK QW DATA ENTRY 7 -- RUN QWVALID TO EDIT DATA

2 -- MAKE LOG LIST OF QW 8 -- LOCATE DATA FROM MULTIPLE

RECORD HEADER INFORMATION DATABASES

3 -- LOCATE SITES AND/OR 9 -- MAKE WATER-QUALITY TABLES

SAMPLES FROM MULTIPLE DATABASES

4 -- PROVIDE CATION-ANION 98 -- EXIT TO MAIN MENU

BALANCE

5 -- MAKE A PSTAT DATA SET 99 -- EXIT TO SYSTEM

6 -- MAKE WATER-QUALITY TABLES

(File of Record NOS. needed, usually obtained with option 3)

Please enter a number from the above list or a Unix command: 1

3. Choose Option 1 - "CHECK QW DATA ENTRY"

Check QW Data Entry

QW DATA BASE PATHNAME IS : /usr/opt/nwis/data/midas/db01/qwfile

THIS PROGRAM LISTS THE DATA FOR A RECORD

DO YOU WANT TO ENTER RECORD ID'S FROM THE TERMINAL (YES OR NO) ? Yes

DO YOU WANT THE OUTPUT

TO YOUR TERMINAL(T) OR TO A FILE(F)?

PLEASE ENTER T -- FOR TERMINAL

OR F -- FOR FILE.

If you choose T, you can look at the file on the screen, then copy and paste it to an editor to print it.

If you choose F, you assign a filename, then print using lp –dprintername filename.

DO YOU WANT TO IDENTIFY RECORDS BY

1 -- RECORD NUMBER, OR

2 -- AGENCY CODE, STATION NUMBER, DATE, TIME, AND MEDIUM

PLEASE ENTER 1 OR 2. 1

PLEASE ENTER RECORD NUMBER (QUIT TO END): 00000571 (From Login)

Example output

RECORD NUMBER: 00000571 AGENCY: USGS STATION NUMBER: 392357076183601

STATION NAME: WB38A

BEGIN: 03-09-2000 1315 END: - -

SAMPLE MEDIUM: 6 ANALYSIS STATUS: H ANALYSIS SOURCE: 9

HYD. COND.: SAMPLE TYPE: 9 HYDROLOGIC EVENT:

PROJECT: 442419400 LAB NUMBER: UPDATED: MAY 22 2000

DATA CATEGORY: QW DATA TYPES: CH

GEOLOGIC UNIT: NO. PARAMETERS: 002

REMARKS:

OTHER:

DISTRICT PROCESSING STATUS: R -- READY TO TRANSFER

R M S R M S

E Q E I E Q E I

PARAMETER VALUE M A T G PARAMETER VALUE M A T G

00027 1028. I 5 00028 1028. I 5

PLEASE ENTER RECORD NUMBER (QUIT TO END):

4. You can quit after entering record number and print the file (ex "lp -dprintername filename" or from the editor screen)
5. Compare the new printout to the ASR form and make sure they agree.
6. If everything looks good: sign, date, and staple the printout behind the ASR.

7. If you have mistakes, choose option 98 to get back to main menu and continue.

QWDATA Main Menu

QW DATA PROCESSING ROUTINE REV NWIS_3_2+19991101

YOU ARE USING WATER-QUALITY DATABASE NUMBER 01

QW SYSTEM OPTIONS

1 -- LOGIN SAMPLES 4 -- CHECK SUPPORT FILES INCLUDING

List Sites, Access Parameter,

Code Dictionary, Access Geologic

Unit Code and State/County Files.

2 -- ADD / CHANGE / DELETE 95 -- WATER QUALITY UTILITIES OPTIONS

Enter field or

miscellaneous data

Edit or flag samples,

Count QW records, or

Update Site File.

3 -- RETRIEVE SAMPLES 99 -- EXIT TO SYSTEM

Check entry or make

loglist, Locate samples,

Provide cation/anion

balance, Make tables or

PSTAT data set.

Please enter a number from the above list or a Unix command: 2

8. Choose Option 2 - "ADD CHANGE DELETE"

QW DATA PROCESSING ROUTINE REV NWIS_3_2+19991101

YOU ARE USING WATER-QUALITY DATABASE NUMBER 01

ADD / CHANGE / DELETE DATA OPTIONS

1 -- ENTER FIELD DATA

2 -- ENTER MISCELLANEOUS DATA

3 -- EDIT SAMPLE RECORDS INCLUDING

Modifying QW record header and data, or Deleting QW records.

4 -- FLAG APPROVED SAMPLES

5 -- UPDATE SITE FILE

6 -- COUNT QW RECORDS

98 -- EXIT TO MAIN MENU

99 -- EXIT TO SYSTEM

Please enter a number from the above list or a Unix command: 3

9. Choose Option 3 - "EDIT SAMPLE RECORDS".

QW DATA BASE PATHNAME IS : /usr/opt/nwis/data/midas/db01/qwfile

RECORD EDIT PROGRAM

WED, MAY 24

DO YOU WANT TO IDENTIFY RECORDS BY

1 -- RECORD NUMBER, OR

2 -- AGENCY CODE, STATION NUMBER, DATE, TIME AND MEDIUM

PLEASE ENTER 1 OR 2

Choose Option 1 - "RECORD NUMBER" 1

DO YOU WANT PRECISION CODES TO BE

1 -- DETERMINED BY THE PARAMETER CODE DICTIONARY (PCD)

2 -- SET TO THE PRECISION OF THE VALUES YOU ENTER

PLEASE ENTER 1 OR 2 (1 unless you want to specify precision codes)

PLEASE ENTER RECORD NUMBER (QUIT TO END)? 00000571

10. Choose 1 for precision codes (unless you want to specify).

11. Enter record number and verify that you have pulled up the correct record.

12. Modify either the record header or the analytical data depending on the error.

3. Track Data when it comes back from the Lab

The lab "Schedules" and "lab codes" for analysis are listed on the ASR forms. Use the schedule information from the lab to check the data for completeness.

1. Open the District Web page and click on Databases, then QWDATA, then "NWQL Spin program." http://tauri.cr.usgs.gov/Udocs/eSPiN.html
2. Use the selection options and pull down menu to choose information about the schedules and lab codes you need.
3. Print the schedule and/or lab code information.
4. Periodically use the steps in the "CHECK DATA ENTRY" portion to get the most recent updates to your samples. Then compare the parameters in the list from the spin program to the parameters that have come back from the lab.
5. Scan the data for outlying values and for schedules with partial data returns. All data for a schedule should be transmitted together. You may need to request re-runs for these later. See the WQ specialist or QWDATA DBA for "holding times" and "delete codes", which will give you an idea of how long it may take to see data for some schedules, and why some parameters may have been deleted at the lab.
6. Keep track of what samples have outstanding data and what samples have complete sets of values.
7. To request a re-run from NWQL:
1. Go to the NWQL webpage at http://wwwnwql.cr.usgs.gov/USGS/USGS_gen.html
2. Click on Services.
3. Then click on District Rerun Request form, and complete the form.

NOTE: The lab does NOT automatically update their database with the re-run values.

(You may decide to use the original values.)

4. If you decide to use the re-run value, notify the lab by replying (with history) to the re-run value message the lab sends and request that they update their database with that value.

If you have a question about an analysis, you can email the lab (gs-w-COdenNWQL DenORG).

Any changes to ASR sample header information should be sent to gs-w-COden NWQL DenADP.

4. Review the Data.

When data comes to our District from the NWQL, "WATLISTS" are generated. WATLISTS contain sample information, data, and important remarks from the lab. Review your WATLISTS as soon as you get them (see WATLIST Checklist below). The QW specialist also reviews all of the WATLISTS and makes recommendations if necessary. It is important to understand the remarks from the lab because you may need to request re-runs if something is not right. The specialist can work with you to determine the criteria for re-run requests.

When data are transmitted from the lab, a new and updated WATLIST is created for each sample, until all the schedules have been completed and loaded; retain the WATLISTs until all your data are processed. When all of the data for a sample are back from the lab and have been checked, write and sign your name, date, return the final WATLIST that has the complete set of values for each sample, and give it to the QWDATA DBA. You do not need to sign and return every WATLIST, only the final WATLIST for each sample that shows that all values have been checked and verified for that sample. The QWDATA DBA will archive copies of the WATLIST in the District files in the library.

_______________________________________________________________________________

WATLIST CHECKLIST

Check all values for acceptable limits and missing data.

Read the lab comments-request re-runs on the NWQL homepage: http://wwwnwql.cr.usgs.gov/USGS/district_rerun_request.html

Look for missing record numbers on all of your WATLIST printouts. The absence of a record number on a WATLIST means that you have “badqw,” and unless the WQ DBA has written a note on the WATLIST telling you that it was fixed, the values have not been loaded into the QWDATA system..

Resolve all “badqw” issues (instructions follow).

When you have finalized all the data on the “last” WATLIST for each sample, sign, date, and return the “finalized” WATLIST to the QWDATA DBA.

Talk to the QW specialist if you have any questions.

______________________________________________________________________________

Handling BADQW

Common reasons why you may have “badqw”:

• Typos for station ID, date, time, and/or medium code are frequently made during the “login” sequence (by us and the lab).

• Samples have not been logged in before data return from the NWQL.

• Samples were logged into the wrong database (01=data; 33=QA/QC) See QWDATA DBA.

If you get a “badqw WATLIST” and you have not given the QWDATA DBA your ASR for that sample, do the following:

1. If necessary, fix the internal QWDATA header file by entering the correct information.

2. Send the WQ DBA an E-mail “fix” notice with both the incorrect and the correct sample information. (Station number, date, time, and medium code, the record number and the project number.) Also include the handwritten date that is on the WATLIST so that the badqw file can be located and the changes made. The lab also needs to make the changes so that more schedule data won’t go into the wrong place, and therefore into badqw. Email your corrections to the NWQL at GW-W-Coden NWQL DenADP.

3. Give your corrected ASR forms to the WQ DBA and they will fix and load your badqw. Do not erase errors on your ASR forms. Instead, cross them out and write down the correct information next to the error.

What you should do if you get a badqw WATLIST because you did not log your samples in:

1. Log your badqw samples in and check for errors.

2. Send the WQ DBA an Email “login” note to reload the data. Include the project number, station ID, data, time, and medium code and the new record number.

3. Place the ASR(s) in the ASR In-box in the QWDATA DBA’s office and they will load your badqw.

In some cases you will get a badqw WATLIST that has already been fixed by the QWDATA DBA. This is for your information to avoid badqw in the future, but you should still follow up with the DBA to make sure that all updates have been done.

NOTE: All records (and WATLISTs) will be filed by station ID and archived in the District Library. Prior to FY 2000, records were filed by project number.

References

U.S. Geological Survey, 1990, National Water Information System User’s Manual, Water Quality System, U.S. Geological Survey Open File Report 89-617, Volume 2, Chapter 2.

U.S. Geological Survey, 1996, Quality Assurance Plan for Water-Quality Activities of the Maryland-Delaware-District of Columbia District.

U.S. Geological Survey, National Water Quality Lab technical memorandums (see NWQL’s homepage). ö

DMP 7:

Maintenance of Water-Quality Files from Non-USGS Analytical Laboratories

Introduction

Water Resources Division Memorandum 92.36 states that all National water-quality programs are required to use the Water Resources Division’s Branch of Analytical Services for analytical services providing data for non-research purposes. Before considering an alternative laboratory, the policy on such use must be considered, and the District Water-Quality Specialist must be consulted. The non-USGS Laboratory needs to be approved in accordance with WRD Memo 92.35.

Quality-assurance procedures must be established for each cooperator laboratory supplying data for use by the MD-DE-DC District projects and the District Water Quality Specialist must be consulted, and approval obtained before using cooperator laboratories. Quality-assurance reports for each cooperator laboratory are to be submitted to the Regional Hydrologist and to the Branch of Quality Assurance.

The project staff will need non-USGS Analytical Lab forms equivalent to NWQL ASRs or standardized field forms obtained from the appropriate Discipline Specialist. Data are recorded on field sheets, non-USGS lab printouts, ASRs or non-USGS Analytical Lab, and in NWIS or other databases if appropriate,.

Instructions

1. Each sample sent to a non-USGS Analytical Lab will include a properly completed lab form (or ASR). A copy of the lab form (or ASR) shall be retained for data management purposes. The non-USGS lab form (and/or supplemental attachment) must contain all information contained on the NWQL ASR form.

2) Project staff shall review non-USGS lab printouts of analyzed samples for completeness and accuracy. (Suggested methodology for review is detailed in the Water-Quality Assurance Plan for the MD-DE-DC District). These protocols will be maintained by the project and later archived.

3) Log in analytical results from the non-USGS Analytical lab into NWIS, ensuring that the analyzing agency parameter code field is specified. The non-USGS lab sample record number, and record number generated by QWMENU should be recorded on the field sheet or Non-USGS lab sheet (ASR).

Instructions for processing data from non-USGS labs (such as Microsoft Excel format) using QWSwitchyard follow.
QWSwitchyard

The QWSwitchyard program or “qwsy” is a data conversion program that enables water-quality data to be entered into QWDATA. The program can also be used with other types of data (QWSwitchyard is not limited to water-quality data). Data format include RDB (Excel), SAS, INFO, QWCards, and more. The documentation can be obtained at http://csdokokl.cr.usgs.gov/nawqa/doc/qwsy

If data needs to be converted frequently using the QWSwitchyard program, install the program in the users workarea. Otherwise, prepare the file (an example is shown below) and give the file to the GWSI DBA, who can assist with the processing.

To install Switchyard:

In Unix:

1. Create a “switchyard” directory in your user area

2. cp /cs/gmhatten/REALTIME/sunsy.tar

3. tar –xvf sunsy.tar

Preparing the file: The following example processes an Excel file into QWdata one and star cards, which is the NWIS interchange format supported by the NWQL.

Line 1: To convert the Excel file to a RDB (relational data base) file, to assign the correct Parameter codes in the first row. These are found in Table 2 of the QWSwitchyard documentation and the QWDATA documentation.

Line 2: The second line is for data type and width. The numbers do not need to be meaningful in this format, so insert 10S for each column.

Example partial Excel table:

AGNCY	STAID	LABNO	DATES	TIMES
10S	10S	10S	10S	10S
USGS	01646580	39410	19990106	1045
USGS	01646580	39540	19990203	1102
USGS	01646580	39573	19990216	1106

Line 3 and beyond: The analytical data with the appropriate parameter codes follow the header fields.

There are 13 required record-header fields in Table 4 of the QWSwitchyard documentation. Be careful if cells are left blank. If the QWSwitchyard default (Table 5) is not the desired result, change the blanks to zeros to get the QWData default instead.

The following fields are required for qwcards (QWdata). Some fields may be blank.

AGNCY	Agency	HSTAT	Hydrologic Condition Code
STAID	Station ID	STYPE	Sample Type (often 9)
DATE	Date (yyyymmdd)	EVENT	Hydrologic Event
TIMES	Time (####)	ASTAT	Analysis Status
EDATE	End date	ASRCE	Analysis Source (may be P00028)
ETIME	End time	DSTAT	District processing
MEDIM	Medium code (often 9)

DATE: The Date needs to be converted into the YYYYMMDD format.

In Excel, highlight the date column, select Format ->Cells. Choose the Number tab and in the category box, choose custom, and in the Type box, enter yyyymmdd.

Note: If input data doesn’t specify a century, the default is 19. To avoid any confusion, include four digits for the year.

TIME: Highlight the Time column. Usually, time is separated by a colon (ex. 11:30), but a hyphen or period should work also. Convert the Time data to text, then do a find and replace changing the ‘colon’ to ‘nothing’ by hitting return in the replace box. If this doesn’t work, it is possible that Excel is trying to find the blank spaces after the colon. If you click in the “Find” box and the entire area becomes dark, try deleting/replacing the black space with a colon.

Once the Excel file is ready (and has the two header lines with correct parameter codes), save the file as a .txt file (tab delimited), which simulates the RDB format.

Running QWSwitchyard:

It is easiest to work in the directory where the QWSwitchyard program resides.
Initiate the program by typing ‘qwsy.static’ at the Unix prompt.

Enter Input Directory: The directory where the program resides (“.” Means here, so <rtn>)

Enter Input Filename: filename

Enter Input File Type: rdb

Enter Output Directory: Probably here… “.”

Enter Output Filename: call it qwcards if it is going into QWDATA.

Enter Output File Type: QWC

The defaults can be chosen for the remaining options by hitting return.
If you need more details, see the QWSwitchyard documentation at http://csdokokl.cr.usgs.gov/nawqa/doc/qwsy

Once the qwcards (1 and star card format) file is created, the data file can be loaded into QWData by the QWDATA DBA. Reminder: QWSwitchyard can be used for converting other data formats.ö

DMP 8: ADAPs and Surface-Water Sites

Once the surface-water site is established in the GWSI Site-File (DMPs 3 and 4), the ADAPS DBA have the following information in order to input, edit, and process data in ADAPS. Appendix K lists information required for surface-water sites for entry into the GWSI site file. Additional details and explanations for the required information below are described in ADAPS documentation.

1. The techniques used to obtain hydrologic measurements at the site. Techniques may range in complexity from direct human observation to sophisticated real-time satellite telemetry.

2. The hydrologic variable(s) being measured at the site along with the recording interval of each variable. Some common variables (data descriptor) for surface-water stations include gage height, precipitation, and battery voltage. Wells with automated data-collection equipment record water levels referenced to either sea level or land surface. Selected water-quality parameters can also be logged. The station’s time must also be known (Eastern Standard Time).

3. The type, make, and model number of all sensing equipment being used at the site to log the hydrologic data or transmit the data via phone or satellite. If satellite telemetry will be used, a nesdis id along with other telemetry parameters must be obtained in by consulting with the ADAPS DBA.

6. All changes to a site, such as logging interval, addition or removal of data descriptors, equipment changes, or if the site is to be discontinued or become inactive.

7. When a site has been reviewed and the data is no longer provisional, the ADAPS DBA must be informed so the station can be “Final Flagged”. ö

DMP 9: Recording Field Notes

District policy requires the use of standardized field forms to record field data. Standardized field forms can be obtained from the appropriate Discipline Specialist or DBA, or may be downloaded from one of the District specialists web pages. Standardized forms, which are often formatted to meet the needs of the project, must reflect database requirements and the needs of other potential users of the data. This DMP specifies procedures for recording and managing field notes.

All field forms must be kept in an organized binder or folder with project or network files. Data and information on field forms that will be stored in databases should be entered in a timely manner. Consult the District Archiving Policy Document for archiving field forms.

Requirements:

Project staff recording field notes on field forms must:

• Be trained in the collection of the data they are obtaining,

• Have obtained the correct field forms before doing any field work,

• Have consulted the appropriate QA/QC plans for instructionS and guidelines,

• Have been trained in maintenance of paper files using MD-DE-DC District Procedure Document (DMP 1), and

• Include the serial numbers and/or identification numbers of all equipment used to obtain field measurements on field forms.

If non-standardized forms are required, it is the responsibility of the Project Chief to develop appropriate field forms. To ensure that field forms meet minimum requirements, field forms must be approved by the Discipline Specialists in consultation with the DBAs. The use of notebooks to record field data is not an acceptable substitute for standardized forms

Non-Standard Field Form Requirements

When standardized forms do not exist, the project will develop a new standardized form to meet specific project needs with the following minimum and recommended additional requirements.

Minimum requirements	Recommended additional requirements
Project number	Reason for work (ex. routine sampling)
Site name	Weather conditions
Site id	Instrumentation
Date and time of work	Procedure and method of collection
Site condition	Type of data collected
Persons performing work	Database parameter codes

Some examples include: Hydrolab unit number; time of last calibration; type of sampler; sampling method; beginning, end, and midpoint time of sample collection; type of pump used; purging criteria; location of measuring point; and chemical preservatives and their order of use.ö

DMP 10:

Calibration and Performance Records for Measurement Equipment

Calibration and performance records substantiate the quality of data collected by documenting information about the calibration, performance, maintenance, upgrades, and custody of instrumentation used for hydrologic investigations. Calibration and performance records will be kept for each piece of equipment in the District.

To minimize data-collection errors, all measurement equipment must be calibrated and maintained so that the equipment is measuring values that are within specified tolerances. This DMP specifies procedures for documenting calibration and performance records for measurement equipment.

Requirements:

Project staff using measurement equipment in the laboratory or in the field must first:

1. Read the instrument manual and understand how to calibrate, operate, and maintain the equipment;

2. Review measurement equipment calibration and performance records to determine equipment status prior to use;

3. Review appropriate field forms to determine the type of data to be collected.

The following are needed to manage calibration and performance records:

§ Standardized field forms for surface water, ground water, water quality, or geophysics as obtained from the appropriate discipline specialists.

§ A copy of the instrument manual to be used including manufacturers specifications.

§ Equipment and supplies for calibration and maintenance of the instrument to be used, including extra batteries.

§ A notebook dedicated only to recording and archiving calibration and performance records.

Instructions:

1. Each measurement instrument will have a calibration and performance record in a notebook that will incorporate calibration data in a standard format.

2. The notebook will travel with the measurement equipment and will record chain of custody.

3. The first page of the record will contain:

a. Equipment make, model, serial number, and manufacturer (preferably with a phone number for technical contact);

b. Equipment specifications

• Type of instrument

• Intended use

• Operating ranges

• Temperature sensitivity

• Date of purchase

• Design life;

c. Primary custodian for instrument (with several blanks lines for successions).

4. The record will also contain a copy of the equipment operating manual.

5. For each type of measurement equipment, a standard format will be created by the primary custodian in coordination with the discipline specialist to record calibration and performance records as specified by the manufacturer, and by requirements from appropriate field forms for the type of data collected. To facilitate record review, standard formats will include the following for each calibration:

a. Custodian (name and project);

b. Date, time;

c. Calibration information as appropriate:

• instrument conditioning;

• information on standards and filling solutions (manufacturer, type, strength, batch no., expiration date, etc.);

• records for continuous duty instruments will include measured values before and after calibration and maintenance;

• raw readings and necessary conversion factors;

• calibration temperature;

d. Maintenance information

• cleaning or de-contamination methods used;

• laboratory or field change of membranes, diaphragms, filling solutions etc.;

• battery replacement;

• probe replacement;

• return for conditioning/overhaul by the manufacturer;

e. Remarks

• weather conditions;

• conditions of use (a short narrative e.g. measured volatile organic carbon contaminated ground water in the winter);

• suspicious activity (problems calibrating, error messages etc.);

• problematic occurrences (dropped the probe in the river etc.);

• general remarks (as appropriate from the operator).

Calibration and performance information for each use will be recorded on field notes with the raw data collected at a measurement site and will also be documented being maintained in the record book that travels with the equipment. Consult District Archiving Policy Document for archiving of calibration and performance records for measurement equipment.

References

Holman J.P., Gajda, W.J., Jr., 1984, Experimental Methods for Engineers, 4th ed., McGraw Hill Book Co New York, 514 p. Intergovernmental Task Force on Monitoring Water Quality, 1994, The Strategy for Improving Water Quality Monitoring in the United States: U.S. Geological Survey, Reston Va., 94 p.

Intergovernmental Task Force on Monitoring Water Quality, 1994, The Strategy for Improving Water Quality Monitoring in the United States: Technical Appendixes: U.S. Geological Survey, Reston Va., 117 p.

Wilde, F.D., and, Radtke D.B. (editors), 1996. National Field Manual for the Collection of Water-Quality Data. U.S. Geological Survey Handbooks for Water-Resources Investigations,

Book 9, Chapter A6.

Schroder, L.J., and Shampine, W.J., 1992, Guidelines for preparing a quality assurance plan for District offices of the U.S. Geological Survey: USGS Open File Report 92-136 14 p.

Shampine, W.J., Pope, L.M., and Koterba, M.T., 1992, Integrating Quality Assurance in Project Work Plans of the U.S. Geological Survey: USGS Open File Report 92-162 12 p. ö

DMP 11: Management of Non-Standard Digital Data

Non-standard digital data includes all digital data that cannot be stored in the National Water Information System (NWIS) database. Geophysical logs, Global Positioning System (GPS) data, data logger records, digital site survey records, and other data that exists in digital format are non-standard digital data. Non-standard digital data produced by the U.S. Geological Survey, Water Resources Division has enduring value and should be stored to facilitate processing, publication, and storage. Consult the District Archiving Policy Document for archiving of non-standard digital data files. Project Chiefs will keep a written explanation of the project filing system(s) for non-standard digital data including what is stored and the physical location of the files.

Accuracy and Limitations

The accuracy of data stored will reflect the accuracy of the input readings and conform to USGS report standards for rounding, and use of significant figures. ASCII files should be used whenever possible; however, more complex formats are sometimes required (such as GIS data layers or other multifaceted graphical output like pictures, video, or sound). Project chiefs may establish other formats in cooperation with the appropriate database administrators to determine appropriate and durable storage formats. Non-standard digital data stored in commercial databases for project use will be stored in ASCII format at the conclusion of the project, unless the data is produced as a stand-alone electronic publication.

Instructions:

The following procedures are necessary to properly maintain and organize non-standard digital data files created by each project such that the data files are suitably formatted, stored, and documented for present and future use.

1. Non-standard digital data should be stored so that, at a minimum, identifies the data by site ID, data type, and date of collection.

2. All non-standard digital data that is suitable for publication, referred to in a publication, or is suitable for use in future studies will be stored in an ASCII format if possible, and in another standard format if not.

3. Digital data collected by projects will be stored in directories documented and designated for project data on one of the available distributed information systems so that:

• Digital project records will receive the benefit of systematic backups performed by the computer unit.

• Digital information will be universally available to project teams.

• Digital information will be available for all internal reviews.

4. Filename conventions will indicate site name, type of data, and sampling date.

5. Project staff will follow file name conventions and data formats when the District establishes databases for non-standard digital data.

6. For each data-collection site, the following three files will be maintained and stored together for each data type:

• Raw data as recorded by the instrument.

• Transitional information identifying who, what, where, and how data was recorded and transformed for interpretive use, as well as the expected accuracy and precision of the measurements.

• Transformed data including shifts and other modifications needed to use the data.

7. Data file formats should be tab or space delimited; ASCII if possible. Numerical data may be floating point or fixed format, but if fixed, significant figures should be noted.

8. Digital data collected by projects should be stored on appropriate media to provide a supplemental backup.

References

Intergovernmental Task Force on Monitoring Water Quality, 1994, The Strategy for Improving Water Quality Monitoring in the United States: U.S. Geological Survey, Reston Va., 94 p.

Intergovernmental Task Force on Monitoring Water Quality, 1994, The Strategy for Improving Water Quality Monitoring in the United States: Technical Appendixes: U.S. Geological Survey, Reston Va., 117 p.

Schroder, L.J., and Shampine, W.J., 1992, Guidelines for preparing a quality assurance plan for District offices of the U.S. Geological Survey: USGS Open File Report 92-136 14 p.

Shampine, W.J., Pope, L.M., and Koterba, M.T., 1992, Integrating Quality Assurance in Project Work Plans of the U.S. Geological Survey: USGS Open File Report 92-162 12 p. ö

DMP 12: Management of Stream Sediment Data

While a project or network is active, the stream sediment data files will be maintained in folders by project or network staff. See Knott and others (1993) for accuracy and limitations of data collection, lab analysis, and data reporting. Data are recorded on field sheets, analytical forms, lab printouts and in NWIS. Consult District Archiving Policy Document for archiving of stream sediment data.

It is assumed that Project staff has been trained in proper sediment data collection and analysis techniques. QWMENU and ADAPS data entry and retrieval. Continuous sediment record will be reviewed by a sediment specialist in the Northeast Region. All instantaneous sediment data will be published in the annual Water Data report. (See Novak, 1985).

Materials

1. Standardized field forms for sediment-data collection obtained from the QW Specialist. (Forms are available for downloading from the QW Specialist web page.)

2. Sediment analysis forms obtained from the USGS Sediment Lab being used.

3. Copies of the reports and memorandums listed in the references.

Instructions

1. Before data collection begins, a site must be established using the procedures described in DMP 3.

2. Complete a standard sediment-data collection field form for each sample.

3. Log in the sample by entering information from the field form into the NWIS QWMENU program prior to sample shipment.

4. The sample record number generated by the QWMENU program should be recorded on the field sheet.

5. Before shipping sediment samples to a USGS Sediment Lab, complete a standard laboratory sediment analysis form and ask about any special instructions that may be required for shipping samples.

6. Lab analytical results for sediment data will be entered into QWMENU within 30 days of receipt.

7. For continuous sediment stations, all daily suspended-sediment data must be entered into ADAPS after analysis using sediment computation methods described by Porterfield (1972) and SEDCALC by Koltun and others (1994).

References

Edwards, T.K., and Glysson, G.D., 1988, Field methods for measurement of fluvial sediment: U.S. Geological Survey Open-File Report, 118 p.

Glysson, G.D., 1987, Sediment-transport curves: U.S. Geological Survey Open-File Report 87-218, 47 p.

Knott, J.M., Glysson, G.D., Malo, B.A., and Schroder, L.J., 1993, Quality assurance plan for the collection and processing of sediment data by the U.S. Geological Survey, Water Resources Division: U.S. Geological Survey Open-File Report 92-499, 18 p.

Koltun, G.F., Gray, J.R., and McElhone, T.J., 1994, User’s manual for SEDCALC, a computer program for computation of suspended-sediment discharge: U.S. Geological Survey Open-File Report 94-459, 46 p.

Novak, C.E., 1985, Water Resources Division data reports preparation guide: U.S. Geological Survey Water Resources Division, 119 p.

Office of Surface Water, 1991, Programs and plans--guidelines for the analyses of sediment data: U.S. Geological Survey Office of Surface Water Technical Memorandum No. 91.15, 30 p.

Porterfield, George, 1972, Computation of fluvial sediment discharge, TWRI 3-C3, 66 p.

U.S. Geological Survey Water Resources Division Missouri District, 1993, Technical memo series--quality assurance and operating plan for sediment activities of the Missouri District, 49 p. ö

DMP 13: Management of Geophysical Data

Geophysical records, including borehole geophysical logs and results of surface geophysical surveys, have enduring value to hydrologic studies and to the general public. However, the NWIS database has no provisions for most geophysical data. This DMP establishes a method for managing and storing geophysical data for current and future uses. It is assumed that persons collecting geophysical data understand the principles behind the measurement, are familiar with the equipment, and can output data in suitable formats. The accuracy of recorded geophysical data should reflect the accuracy of measurements made by the geophysical equipment, not the maximum places stored in the data logger. Consult the District Archiving Policy Document for archiving of paper and electronic files of geophysical data according to archiving of paper and non-standard digital data, respectively.

Instructions:

1. A graph of each log should be made on a sheet of paper to be stored in District files which includes (front and/or back) the following information:

• type of log;

• method/probe type used;

• well name and site ID or, if for surface geophysics, location by latitude and longitude of base point lengths and directions of lines, and information indicating location relative to features on the land surface such as roads, streams, and other landmarks likely to remain static for 10-20 years. (Preferably with a sketch or a base map);

• date of log;

• project name;

• project chief;

• logger’s name;

• brief description of the reason for log;

• the expected accuracy and precision of measurements.

2. Digital copies of geophysical logs will be created, stored, and handled according to specifications in DMP 11 Management of non-standard digital data. Digital data for some types of logs is best stored on compact discs (CD’s) because of the size of the files. ö

DMP 14: Archiving Paper Files and Project Files in the District Library

Archiving is the final step in the processes of data collection, analysis, and interpretation. Archiving is the systematic process to ensure that data (electronic and paper form) and information will be permanently stored and maintained without change in a secure and accessible environment. In general, all data published in WRD reports, or used to support scientific analyses leading to conclusions in the reports, are archived. The Discipline Specialists and Supervisors are responsible for ensuring that Project data is properly stored.

Electronic archiving is the systematic process of removing data from active, on-line computer storage and preserving it with the capability to recover the data. See the District Archival Plan (DAP) for specific instructions for storing electronic data and report documents. All data will also be stored electronically in consultation with the DBA. If possible, data will be archived in NWIS.

Site Files

At the conclusion of a project, the paper file for each data-collection site will be archived in the District library. Site-File folders will be filed by Federal Information Processing Standards (FIPS) county code, then by well name within each particular FIPS county code. If a site has been used by two or more different projects, Site-File folders for each project are maintained in separate, but sequential, files. Data-organization and verification efforts during the project will ensure more rapid, efficient, and quality-assured responses to information requests.

It is the responsibility of the Project Chief to archive the Site-File folders. It is the responsibility of the GWSI DBA to ensure that Site-File folders have been properly archived and to resolve any filing or site-information problems.

Project Files

Critical components of project files maintained by the Project Chief will also need to be archived at the conclusion of a project. Project files archived in the District library will be no more than approximately 4-in. thick and will be filed by project account number. The project files must contain the following information:

1. A copy of the project proposal.

2. Copies of all Management Information System (MIS) reports, important correspondence, and all quarterly progress reports.

3. Multi-site data tables.

4. Important maps, model runs, and other interpretive information.

5. A copy of the final report(s) including any errata.

8. A list of project personnel and their duties—especially with relation to installation of data-collection sites, data collection and management, and data analysis and report writing.

9. A compilation of all data-collection sites used in the project, with site ID’s, and summary statements of the types of data collected at each site.

All remaining important project information will be archived in the District warehouse in boxes labeled with the 9-digit project number, project name, date of project completion or termination, name of Project Chief, and a brief description of the contents. It is the responsibility of the Project Chief to organize and archive important project files in the District library and warehouse.ö

REFERENCES

Arvin, D.V., 1993, Quality-assurance plan for the U.S. Geological Survey--Indiana District water-use program: U.S. Geological Survey Open-File Report 93-88, 31 p.

Biesecker, J.E., 1991, The importance of data management: U.S. Geological Survey Information Systems Developments, v. 8, no. 6, p. 170-171.

Edwards, T.K., and Glysson, G.D., 1988, Field methods for measurement of fluvial sediment: U.S. Geological Survey Open-File Report, 118 p.

Glysson, G.D., 1987, Sediment-transport curves: U.S. Geological Survey Open-File Report 87-218, 47 p.

Holman J.P., Gajda, W.J., Jr., 1984, Experimental Methods for Engineers, 4th ed.: New York, McGraw Hill Book Co. 514p.

Intergovernmental Task Force on Monitoring Water Quality, 1994, The Strategy for Improving Water-Quality Monitoring in the United States: Reston Va., U.S. Geological Survey, 94 p.

Intergovernmental Task Force on Monitoring Water Quality, 1994, The Strategy for Improving Water-Quality Monitoring in the United States: Technical Appendixes: U.S. Geological Survey, Reston Va., 117 p.

Knott, J.M., Glysson, G.D., Malo, B.A., and Schroder, L.J., 1993, Quality assurance plan for the collection and processing of sediment data by the U.S. Geological Survey, Water Resources Division: U.S. Geological Survey Open-File Report 92-499, 18 p.

Koltun, G.F., Gray, J.R., and McElhone, T.J., 1994, User’s manual for SEDCALC, a computer program for computation of suspended-sediment discharge: U.S. Geological Survey Open-File Report 94-459, 46 p.

Maddy, D.V., Lopp, L.E., Jackson, L.D., Coupe, R.H., and Schertz, T.L., 1989, National water information system user’s manual, v. 2, chap. 2, version 90.1--water-quality system: U.S. Geological Survey Open-File Report 89-617, 218 p.

Martin, J.D, Cohen, D.A, 1994, Policy and Procedures for the Management and Archival Storage of Data Collected for Hydrologic Investigations, U.S. Geological Survey, Indiana District: U.S. Geological Survey, Open-File Report 94-61, 21 p.

Mathey, S.B, ed., 1989, National water information system user’s manual, v. 2, chap. 4, version 90.1--ground-water site inventory system: U.S. Geological Survey Open-File Report 89-587, 242 p.

Novak, C.E., 1985, Water Resources Division data reports preparation guide: U.S. Geological Survey Water Resources Division, 119 p.

Office of Surface Water, 1991, Programs and plans--guidelines for the analyses of sediment data: U.S. Geological Survey Office of Surface Water Technical Memorandum No. 91.15, 30 p.

Porterfield, George, 1972, Computation of fluvial sediment discharge, TWRI 3-C3, 66 p.

Schroder, L.J., and Shampine, W.J., 1992, Guidelines for preparing a quality assurance plan for District offices of the U.S. Geological Survey: USGS Open-File Report 92-136 14 p.

Shampine, W.J., Pope, L.M., and Koterba, M.T., 1992, Integrating Quality Assurance in Project Work Plans of the U.S. Geological Survey: USGS Open-File Report 92-162 12 p.

U.S. Geological Survey, 1984a, Water-data program, Water Fact Sheet, 2 p.

U.S. Geological Survey, 1984b, Federal-State Cooperative Water-Resources Program: U.S. Geological Survey, Water Fact Sheet, 2 p.

U.S. Geological Survey, 1990, National Water Information System User’s Manual, Water Quality System: U.S. Geological Survey Open-File Report 89-617, Volume 2, Chapter 2.

U.S. Geological Survey Water Resources Division Missouri District, 1993, Technical memo series-quality assurance and operating plan for sediment activities of the Missouri District, 49 p.

U.S. Geological Survey, 1996, Quality Assurance Plan for Water-Quality Activities of the Massachusetts-Rhode Island District

U.S. Geological Survey, 1997, Office of Ground Water, A Quality-Assurance Plan for District Ground-water Activities of the USGS, Open File Report 97-11, GWPD 5.

U.S. Geological Survey, 1997, Office of Ground Water, Technical Memorandum No. 93-01, Programs and Plans--Establishment of a National Policy to Archive Ground-Water Flow and Transport Models, October 28, 1992.

U.S. Geological Survey, 1997, Office of Ground Water, Technical Memorandum No. 94-02, Guidance for the Preparation, Approval, and Archiving of Aquifer-test Results, June 2, 1994.

Wilde, F.D., and, Radtke D.B. (eds.), 1996. National Field Manual for the Collection of Water-Quality Data. U.S. Geological Survey Handbooks for Water-Resources Investigations, Book 9, Chapter A6.

WRD 92.035: Policy of the Water Resources Division on the Use of Laboratories.

WRD 92.036: Policy of the Water Resources Division on the Use of Laboratories by National Water-Quality Programs.

WRD 92.037: Policy of the Water Resources Division on Laboratory Analytical Methodology.

WSP 2175: Measurement and Computation of Streamflow, Volumes 1 and 2. ö

APPENDIXES

Appendix A	Database Administrators (DBA’S) and Managers Duties
Appendix B	State and County Codes
Appendix C	Required Site-File information for all data-collection sites
Appendix D	Additional required Site-File information for all ground-water sites
Appendix E	Required information (if available) for all ground-water sites to be entered into GWSI
Appendix F	GWSI table format examples
Appendix G	Required information for all water-quality samples
Appendix H	Required WATSTORE parameter codes for the Water-Quality System for all water-quality samples
Appendix I	Required WATSTORE parameter codes for the Water-Quality System for all field alkalinity measurements
Appendix J	National Water-Quality Laboratory-U. S. Geological Survey Analytical Services Request (ASR) Form Codes
Appendix K	Additional required information to be stored in the Automated Data Processing System

Appendix A. Database Administrators (DBA’S) and Managers Duties

All DBAs 1) Train users of NWIS programs.

2) Check that all data entered into NWIS is complete.

3) Check that staff follows data management procedures and policy.

4) Delete or merge data where duplicate sites or data exist.

5) Check that data is posted correctly to the web.

6) Assist Information Officer with information requests.

7) Attend yearly database reviews.

District Database Manager 1) Serve as database and NWIS resource.

Wendy S. McPherson 2) Coordinate NWIS database activities.

3) Ensure real-time webpage is being updated with current data.

4) Develop and execute data-checking plan.

5) Provide District level training.

6) Advise staff on data exchange formats.

NWIS DBAs:

GWSI DBA 1) Maintain the GWSI database.

Wendy S. McPherson 2) Assist in duplicate checking.

3) Assign well names.

4) Maintain master site location map.

5) Write Site-File and well data to the database.

ADAPS DBA 1) Maintain the ADAPS database (also see Bob James).

Rick Saffer 2) Assign 8-15 digit downstream order numbers for surface-water sites.

3) Maintain master surface water site location map.

4) Assist with Annual Report.

5) Write Fortran programs to decode all data transmitted from satellites.

QWDATA DBA 1) Maintain QWDATA database.

Betsy Marchand 2) Distribute WATLIST returns from NWQL to Project Chiefs.

3) Assist Project Chiefs in correction of badqw.

4) Send badqw corrections to NWQL.

5) Assist with Annual Report.

SWUDS and AWUDS DBA 1) Maintain all water-use data collected by the District.

Judy Wheeler 2) Maintain the SWUDS and AWUDS databases.

OTHER:

Geophysical DBA 1) Ensure geophysical data are stored in the most efficient and usable form.

Earl Greene 2) Create and maintain District geophysical files.

Discipline Specialists 1) Approve all non-standardized field forms before project use.

Gary Fisher-Surface Water 2) Review and maintaining District QA plans.

Earl Greene-Ground Water 3) Oversee project data collection, management, and archival.

Cherie Miller-Water Quality

Appendix B. State and County Codes

Counties in Maryland (State Code 24)

Code	County	Code	County
001	Allegany	025	Howard
003	Anne Arundel	027	Kent
005	Baltimore	031	Montgomery
007	Calvert	033	Prince Georges
009	Caroline	035	Queen Annes
011	Carroll	037	St. Marys
013	Cecil	039	Somerset
015	Charles	041	Talbot
017	Dorchester	043	Washington
019	Frederick	045	Wicomico
021	Garrett	047	Worcester
023	Harford	510	Baltimore City

Counties in Delaware (State Code 10)

Code	County
001	Kent
003	New Castle
005	Sussex

District of Columbia (State Code 11)

To access the codes for other states, use GWSI option 95 Utility menu, choose 3: Query Support Files. Option 6 gives a list of county codes for a state. Also available are lists of geohydrologic/aquifer codes, parameter codes, and state FIPS codes.

FIPS codes for neighboring states include:

Code	State
42	Pennsylvania
51	Virginia
54	West Virginia

Appendix C. Required Site-File information for all data-collection sites

[FIPS, Federal Information Processing Standards]. Bold components are mandatory fields.

Site-file component number	Brief description	Remarks
C4	Agency code	5-character code (example: USGS)
C1	Site number	8- or 15-digit number
C5	Project number	9-digit number (example: 442413400)
C12/900	Station name	See DMP 3 for naming conventions.
C9	Latitude
C10	Longitude
C11	Latitude/longitude accuracy
C35	Latitude/longitude method	GPS is preferred.
C36	Latitude/longitude datum	Generally NAD27 for topographic maps; NAD83 for GPS
C6	District code	Maryland-Delaware-D.C. District = 24
C7	State code	Maryland-Delaware-D.C. = 24, DE = 10, DC =11
C8	County code	3-digit FIPS county code (ask GWSI DBA)
C14	Location map	Topographic or other map name, with State initials.
C15	Location map scale	State as a representative fraction (1:24,000=24000)
C16	Altitude of land surface or gage datum	In feet above sea level.
C17	Method of altitude determination
C18	Altitude accuracy
C20	Hydrologic unit code (HUC)	Found on HUC map (see GWSI DBA).
C802	Station or site type
C803	Agency use of site	A=Active, I=Inactive, O=Inventory Only
C804	Type of data collected
C805	Type of instrumentation
C806	Remarks	Include the name of USGS person establishing the site. This may also be stored in the Misc. Remarks section.
C3	Data reliability	C=field checked, L =poor location, M=minimal data, U=unchecked
C813	Greenwich Mean Time (GMT) offset	-5 hours for MD-DE-D.C. District Eastern Standard Time
C814	Local standard time flag	Maryland-Delaware-D.C. District = Yes

Appendix D. Additional required Site-File information for all ground-water sites [WATSTORE, Water Data Storage and Retrieval System]. Bold components are mandatory fields.

Site-file component number	Brief description	Remarks
C32	Web ready flag	Conditional if all mandatory fields are complete
C19	Topographic setting
C2	Type of ground-water site
C21	Date of construction
C23	Primary use of site
C24	Primary use of water
C713	Aquifer type
C714	Aquifer code	8-character WATSTORE code
C28	Well depth	In feet below land surface
C27	Hole depth	In feet below land surface
C29	Source of depth data
C237	Water level	In feet below land surface or altitude
C235/C709	Date and time of water-level measurement	If water level is given
C239	Method of water-level measurement
C238	Site status during water-level measurement
C244	Source of water-level data

Appendix E. Required information (if available) for all ground-water sites to be entered into GWSI. Bold components are mandatory fields.

GWSI component number	Brief description	Remarks
CONSTRUCTION FILE
Construction Record
C60	Date construction completed
C63	Contractor’s name
C64	Source of construction data
C65	Method of construction
C66	Type of finish
C67	Type of seal
C68	Depth to bottom of seal	In feet below land surface
C69	Method of development
C70	Hours of development
C71	Special treatment
Hole Record
C73	Depth to top of interval	In feet below land surface
C74	Depth to bottom of interval	In feet below land surface
C75	Diameter of interval	In inches
Casing Record
C77	Depth to top of casing	In feet below land surface
C78	Depth to bottom of casing	In feet below land surface
C79	Diameter of casing	In inches
C80	Casing material
C81	Casing thickness	In inches
Openings Record
C83	Depth to top of opening
C84	Depth to bottom of opening
C85	Opening material
C86	Opening type
C87	Diameter of opening
C89	Opening length	In inches
C88	Opening width	In inches

GWSI component number		Brief description	Remarks
Lift Record (required only if well is equipped with a pump)
C43		Type of lift
C44		Depth to intake	In feet below land surface
C45		Type of power
C268		Rated pump capacity	In gallons per minute
Repair Record
C166	Nature of repair
C167	Date of repair
C169	Name of contractor performing repair
Spring Record (required for springs only)
C172	Local name of spring
C173	Type of spring
C174	Permanence of spring

Appendix E continued... Required information (if available) for all ground-water sites to be entered into GWSI. Bold components are mandatory fields.

Measuring Point Record
C321	Begin date for measuring point
C322	End date for measuring point
C323	Height of measuring point	In feet above land surface
C324	Description of measuring point	Include altitude of measuring point in feet above sea level
WATER-LEVEL FILE
C235	Water-level measurement date
C709	Water-level measurement time	24-hour time (example: 1425)
C237	Water level	In feet below land surface
C238	Water-level measurement status
C239	Water-level measurement method
C276	Water-level measurement accuracy
DISCHARGE FILE
C148	Date discharge measured
C703	Type of discharge
C150	Discharge	In gallons per minute
C151	Source of discharge data
C152	Discharge measurement method
C153	Production water level	In feet below land surface

Appendix E continued... Required information (if available) for all ground-water sites to be entered into GWSI. Bold components are mandatory fields.

GWSI component number	Brief description	Remarks
DISCHARGE FILE -- continued
C154	Static water level	In feet below land surface
C155	Source of water-level data
C156	Water-level measurement method
C157	Pumping period	In hours
C272	Specific capacity	In gallons per minute per foot of drawdown
C309	Drawdown
MISCELLANEOUS FILE
Owner’s Record
C159	Date of ownership
C161	Owner’s name
Miscellaneous Other ID
C190	Misc. other ID	State permit number
C191	Assigner
Miscellaneous/Geophysical Logs Record
C199	Type of geophysical log
C200	Top of logged interval	In feet below land surface
C201	Bottom of logged interval	In feet below land surface
C202	Source of data
Cooperator’s Data Record
C213	Cooperator’s site identifier
C218	Remarks	Include pertinent cooperator information
C200	Top of logged interval	In feet below land surface
C201	Bottom of logged interval	In feet below land surface
C202	Source of data
Cooperator’s Data Record
C213	Cooperator’s site identifier
C218	Remarks	Include pertinent cooperator information

Appendix E continued... Required information (if available) for all ground-water sites to be entered into GWSI. Bold components are mandatory fields.

GWSI component number	Brief description	Remarks
Remarks Record
C184	Remarks date
C185	Remarks	Record person’s name and reason for changes to the Site-File or GWSI files
GEOHYDROLOGIC LOGS FILE
Geohydrologic Units Record
C91	Depth to top of unit	In feet below land surface
C92	Depth to bottom of unit	In feet below land surface
C93	Unit identifier	8-character WATSTORE code
C96	Lithology code
C304	Contributing unit code	Identifies primary and secondary aquifers
C97	Lithologic modifier
HYDRAULICS FILE
C100	Hydraulic unit	8-character WATSTORE code
C101	Depth to top of interval	In feet below land surface
C102	Depth to bottom of interval	In feet below land surface
C103	Hydraulic unit type
C104	Remarks	Include method of determination
C305	Source of data
C107	Transmissivity	In feet squared per day
C108	Horizontal conductivity	In feet per day
C109	Vertical conductivity	In feet per day
C110	Storage coefficient
C103	Hydraulic unit type
C104	Remarks	Include method of determination
C305	Source of data
C107	Transmissivity	In feet squared per day
C108	Horizontal conductivity	In feet per day
C109	Vertical conductivity	In feet per day
C110	Storage coefficient

Appendix F. GWSI table format examples

There are four formats for GWSI tables. Examples are given below.

Specify format (1=Std, 2=Dump 3=Subfile, 4=Special (<CR>=1):

1. Standard table: lists the data you specify to retrieve in columns. This is generally the retrieval format for a large number of sites with only a few data fields of interest.

DATE: 07/07/00 Example of a standard table format PAGE 1

WATER- WATER

LEVEL LEVEL

LOCAL WELL NUMBER SITE-ID DATE (FEET)

BA Dc 444 392931076410301 10-09-1985 44

09-26-1988 43.67

10-04-1988 43.85

10-26-1988 44.25

10-28-1988 44.43

11-04-1988 44.53

12-05-1988 44.83

01-17-1989 45.07

02-10-1989 44.94

03-13-1989 44.52

2. Dump: Lists information for each site down the page.

GWSI RETRIEVAL/TABLING - NWIS_3_2+19991101 gw.table

DATE: 07/07/00 Example of a dump forma1

C001 Site ID (station number) 392931076410301

C002 Type of site W

C003 Record classification C

C004 Source agency code USGS

C005 Project number 442400200

C006 District code 24

C007 State code 24

C008 County code 005

C009 Latitude 392931

C010 Longitude 0764103

C011 Lat-long accuracy code S

C012 Local well number BA Dc 444

C014 Name of location map COCKEYSVILLE

C015 Scale of location map 24000

C016 Altitude of land surface 390

C017 Method altitude determined M

C018 Altitude accuracy 10

C019 Topographic setting S

Appendix F continued…: GWSI table format examples

3. Subfile: This type of file contains no headings or extra spaces. It is used when you want to use the data in another computer program such as Excel.

BA Dc 444 39293107641030119880926 43.67

BA Dc 444 39293107641030119881004 43.85

BA Dc 444 39293107641030119881026 44.25

BA Dc 444 39293107641030119881028 44.43

BA Dc 444 39293107641030119881104 44.53

BA Dc 444 39293107641030119881205 44.83

BA Dc 444 39293107641030119890117 45.07

BA Dc 444 39293107641030119890210 44.94

BA Dc 444 39293107641030119890313 44.52

BA Dc 444 39293107641030119890413 43.28

BA Dc 444 39293107641030119890510 41.02

4. Special: For retrieving water levels for wells.

The following special formats are available -

(1) Daily water levels by year

(2) 5-Day water levels by year

(3) Intermittent water levels by year

(4) Intermittent water levels, multiple years

SITE: 392931076410301

WATER LEVELS IN FEET BELOW LAND SURFACE DATUM

WATER YEAR OCTOBER 1988 TO SEPTEMBER 1989

DAY OCT NOV DEC JAN FEB MAR APR MAY JUN P

1 --- --- --- --- --- --- ---

2 --- --- --- --- --- --- ---

3 --- --- --- --- --- --- ---

4 43.85 44.53 --- --- --- --- ---

5 --- --- 44.83 --- --- --- ---

Appendix G. Required information for all water-quality samples

[WATSTORE, Water-Data Storage and Retrieval System; FIPS, Federal Information Processing Standards]

Data	Remarks
Agency Code	5-character code (example MD003 or USGS)
Site number	8- or 15-digit number
Project number	9-digit number (example 442418900)
Sample year
Sample month
Sample day
Sample time	24-hour time (example: 1435)
State code	Maryland-Delaware-D.C = 24
District code	Maryland-Delaware-D.C. District = 24
County code	3-digit FIPS county code
Sample medium
Geologic unit	For ground-water samples only, 8-character WATSTORE code
Analysis status
Hydrologic condition
Sample type
Hydrologic event

Appendix H. Required WATSTORE parameter codes for the Water-Quality System for all water-quality samples

Parameter Code	Brief description	Remarks
00027	Collecting agency
00028	Analyzing agency
00029	Project number	9-digit code (example: 442413400)
71999	Sample purpose
82398	Sampling method
84143	Well-purging condition	For ground-water samples only
84144	Well-selection criteria	For ground-water samples only
84146	Predominant land use within 100 feet of well	For ground-water samples only
84147	Predominant land use within 0.25 miles of well	For ground-water samples only
84148	Fraction of predominant land use within 0.25 miles of well	For ground-water samples only
84164	Sampler type
72019	Depth to water	For ground-water samples only, in feet below land surface
00020	Air temperature	In degrees Celsius
00010	Water temperature	In degrees Celsius
00025	Barometric pressure	In millimeters of mercury
00003	Sampling depth	Depth of sampler intake, in feet below land surface or gage datum
99905	Person collecting sample	3-digit code
99906	Secondary person collecting sample	3-digit code

Appendix I. Required WATSTORE parameter codes required to be entered in the Water-Quality System for all field alkalinity measurements

Parameter code	Brief description
Non-Filtered Sample
00410	Fixed-end point alkalinity
00419	Incremental-end point alkalinity
00450	Bicarbonate
00447	Carbonate
Filtered Sample
39036	Fixed-end point alkalinity
39086	Incremental-end point alkalinity
00453	Bicarbonate
00452	Carbonate

Appendix J. National Water-Quality Laboratory-U.S. Geological Survey Analytical Services Request (ASR) Form Codes

Site Type

Codes	Description
SW	Stream
GW	Well
SP	Spring
LK	Lake
ES	Estuary
ME	Meteorological

Code	Description
A	Not determined
H	Initial entry
1	Retrieved, in review
3	Data in temporary hold status
7	Reviewed, approved for transfer to EPA STORET
9	Proprietary data (Approval by Regional Hydrologist required)

Analysis Status
Appendix J continued... National Water-Quality Laboratory-U.S. Geological Survey Analytical Services Request (ASR) Form Codes

Sample Medium

Code		Description
O		Not determined
A		Artificial
B		Solids (street sweepings, etc.)
C		Animal tissue
D		Plant tissue
E		Core material
F		Interstitial water
G		Soil
H		Bottom material
J		Sludge
K		Soil moisture
L-P		Taxonomic data
	L	Phytoplanktonic species composition and enumeration
	M	Phytoplanktonic species composition
	N	Periphytic species composition
	O	Benthic invertebrate species composition and enumeration
	P	Periphytic diatoms species composition and enumeration
Q		Quality-assurance sample - Artificial
R		Quality-assurance sample – Surface water
S		Quality-assurance sample – Ground water
T		Quality-assurance sample – Wet deposition
U		Quality-assurance sample – Bulk deposition
V		Quality-assurance sample – Suspended sediment
W		Quality-assurance sample – Bottom material
X		Quality-assurance sample – Animal tissue
Y		Quality-assurance sample – Plant tissue
Z		Quality-assurance sample – Interstitial water
1		Suspended sediment
2		Leachate
3		Dry deposition
4		Landfill effluent
5		Elutriation
6		Ground water
7		Wet deposition
8		Bulk deposition
9		Surface water

Appendix J continued... National Water-Quality Laboratory-U.S. Geological Survey Analytical Services Request (ASR) Form Codes

Analysis Source

Code	Description
A	Not determined
B	Non-USGS field
C	Non-USGS lab only
D	Non-USGS lab and field
F	USGS field and non-USGS field
G	USGS field and non-USGS lab
H	USGS field and non-USGS lab and field
1	USGS lab and non-USGS field
2	USGS lab and non-USGS lab
3	USGS lab and non-USGS lab and field
4	USGS lab and field and non-USGS field
5	USGS lab and field and non-USGS lab
6	USGS lab and field and non-USGS lab and field
7	USGS field only
8	USGS lab only
9	USGS lab and field

Hydrologic Condition

Code	Description
A	Not determined
4	Stable, low stage
5	Falling stage
6	Stable, high stage
7	Peak stage
8	Rising stage
9	Stable, normal stage

Appendix J continued... National Water Quality Laboratory-U.S. Geological Survey Analytical Services Request (ASR) Form Codes

Sample Type

Code	Description
A	Not determined
B	Other QA
H	Composite (time)
1	Spike
2	Blank
3	Reference
4	Blind
5	Duplicate
6	Reference material
7	Replicate
8	Spike Solution
9	Regular

Hydrologic Event

Code	Description
A	Spring breakup
B	Under ice cover
C	Glacial lake outbreak
D	Mudflow
E	Tidal action
H	Dam break
J	Storm
1	Drought
2	Spill
3	Regulated flow
4	Snowmelt
5	Earthquake
6	Hurricane
7	Flood
8	Volcanic action
9	Routine sample

Appendix J continued... National Water Quality Laboratory-U.S. Geological Survey Analytical Services Request (ASR) Form Codes

Remark

Code	Description
Blank	Not remarked
O, E	Estimated value
1, <	Actual value is known to be less than value shown
2, >	Actual value is known to be greater than value shown
3, M	Presence of material verified but not quantified
4, N	Presumptive evidence of presence of material
U	Material specifically analyzed for but not detected
B, K	Results based on colony count outside the acceptable range (non-ideal colony count)
A	Average value
V	Variance
P	Most probable value
L	Biological organism count less than 0.5 percent (may be only observed)
D	Biological organism count equal to or greater than 15 percent (dominant)
&	Biological organism estimated as dominant
#	Delete the remark

Appendix K. Additional required information to be stored in the Automated Data Processing System

Site-File component number	Brief description	Remarks
C813	Mean Greenwich time offset	Maryland-Delaware-D.C. District = -5
C814	Local standard time flag	Maryland-Delaware-D.C. District = Yes
For Lake and Stream Sites Only
C807	Base discharge	In cubic feet per second
C808	Drainage area	In square miles
C809	Contributing drainage area	In square miles
C810	Crest-stage gage upstream elevation	In feet above gage datum
C811	Crest-stage gage downstream elevation	In feet above gage datum
C812	Gage height of zero flow	In feet above gage datum