NAWQA Data and Information for internal use only

Fall 2002 National Data Request

(1997 Study Units, incl YAKI and DLMV)

Guidelines for Preparing the FINAL SW GIS Data Set for National Synthesis

10/08/02


WHAT'S NEW:

Please send a complete set of fixed, bed sediment and tissue, coring and synoptic site basin boundaries with their associated metadata files for your study unit. This is the final SW GIS aggregation for FY97 study units.

A spreadsheet is provided that lists each study unit and the basin boundary coverages that have been received so far. It also list sites where basin boundary coverages have not been received but are expected because they are in one of the networks mentioned above. Please use this spreadsheet (November 13, 2002) to identify sites that are being specifically requested at this time.

In the spreadsheet, each study unit has many rows of data; one row for each basin. The rows have been compressed to make the spreadsheet easier to view. To view the sites for your study unit click on the plus sign (+) just below your study unit name. To compress the rows back up click on the minus sign (-).

Each study unit's list was built by comparing the latest netsite table (August 2002) and the latest set of basin coverages that Molly Maupin has. Sites that are in bold and contain an 'x' in the column 'Basins not recieved' are being emphasized in this request. If your study unit does not have basin boundary coverages for these sites or for some reason cannot create a coverage for them, please explain why in the "Notes" column of the spreadsheet. Include the spreadsheet with your aggregation of coverages.

If the list of sites in the spreadsheet is complete (there are no missing basin boundaries) and you have no updated coverages for sites on the list, then send email to Molly Maupin (mamaupin@usgs.gov) and the latest compilation of basin boundary coverages for your study unit will be used.

REMEMBER, basin boundaries are not necessary for related sites. It is not anticipated that new sites (and new coverages) will be added to the list. If you have a coverage for a site not on the list, then add it to the list and indicated which network it belongs to in the "Notes" column. Send the coverage with it's metadata.

See this webpage to view or retrieve the latest edition of coverages for your study unit . They are tarred and compressed files that are listed by study unit towards the bottom of this webpage.

Purpose


This document describes the contents and procedures for preparing the FINAL set of SW GIS basin coverages from FY97 study units.

Timetable

Guidelines were released on October 8, 2002 and GIS coverages are due back to Molly Maupin (mamaupin@usgs.gov) by November 18, 2002. Please send questions or comments to Molly.

Scope

A complete set of fixed, bed sediment and tissue, coring and synoptic basin coverages and metadata are being requested.

Synoptic sites will include ALL sites where samples were collected according to NAWQA protocols for chemical, biological and ecological sampling. If a site exists in your network file coded as synoptic (syn), and data were collected and stored in NWIS or Bio-TDB as NAWQA samples, then a coverage will be expected. Sites that contribute to study-unit results and yield archival-quality data should be considered a synoptic site.

With the exception of a few sites that have noncontributing drainage areas associated with them, only one basin boundary coverage per site is requested. Two coverages are required for those sites that have contributing areas that provide additional drainage under certain conditions: 1) a coverage of the contributing drainage area under normal conditions, and 2) a coverage of the total potential drainage area (contributing + noncontributing). The second coverage might include those areas that provide flow during storm conditions, or when certain man-made conditions are in effect. For sites that have drainage areas that are larger under special conditions, the second coverage (contributing + noncontributing), or total potential drainage area, will be used to compile a separate set of ancillary data to aid in hydrologic analyses of water-quality during high-flow conditions.

The area derived from a basin boundary coverage will be compared to the NWIS drainage area for that site. Differences greater than 10% between the two areas will require additional verification and checking. Also, the location of the sampling station and the basin boundary will be checked to make sure the stations falls within the coverage.

One metadata file is requested for each basin boundary coverage. Metadata requirements are explained below.

Guidelines

If you manage your data in shapefiles, please convert the shapefiles to coverages with the requested projections. Send only coverages, please do not send shapefiles .

1. Coverage name:

For basins that correspond to a site with a 8-digit STAID, please name contributing basin coverages 'b' + STAID. Coverages for total potential (contributing + noncontributing) drainage coverages should be named with a 't' + STAID. If your study unit has reservoir coring sites, name the basin boundary coverages 'r' + STAID. For those STAIDs that are longer than 8-digits, use only the first 8 digits. If the first 8 digits are not unique, use the first 7 and the 15th digit to guarantee uniqueness of names. Consult the spreadsheet for the few situations where this rule does not suffice. Otherwise, here are a few examples:
        STAID                           COVERAGE NAME
        04087000                        b04087000
        040863075                       b04086307
        435426488092701                 b43542641
        435426488092702                 b43542642
        02334080                        r02334080

2. Projection parameters:

For all but COOK and OAHU, please project coverages to the national albers projection, with central meridian at -96 and North American Datum of 1983 (NAD83):
        PROJECTION ALBERS
        UNITS METERS
        DATUM NAD83
        PARAMETERS
        29 30 00
        45 30 00
        -96 00 00
        23 00 00
        0.0
        0.0
Projection parameters for COOK:
        PROJECTION ALBERS
        UNITS METERS
        DATUM NAD83
        PARAMETERS
        55 00 00
        65 00 00
        -154 00 00
        50 00 00
        0.0
        0.0
Projection parameters for OAHU:
        PROJECTION ALBERS
        UNITS METERS
        DATUM NAD83
        PARAMETERS
        08 00 00
        18 00 00
        -157 00 00
        00 00 00
        0.0
        0.0

3. Polygon attribute table template:

At minimum, include STAID, defined as a 15-character wide item:

        AREA            4  12   F  3
        PERIMETER       4  12   F  3
        Bxxxxxxxx#      4   5   B           or Txxxxxxxx# or Rxxxxxxxx#
        Bxxxxxxxx-ID    4   5   B           or Txxxxxxxx-ID or Rxxxxxxxx-ID
        STAID          15  15   C
Additional attributes are optional as long as they are explained in the metadata. Please keep the first four attributes in the covername.PAT file as they are defined above. If, for some reason, STAID is defined as anything other than character, then leading zeros will be dropped and the STAID will no longer match other data files.

Please make sure that all polygons coverages have topology; please build coverages before submitting the final dataset to Molly .

4. Metadata:

Please prepare an ASCII file of FGDC-compliant metadata for each drainage basin coverage. Name the metadata file covername.met, where covername would be the same as bxxxxxxxx, or txxxxxxxx, or rxxxxxxxx. See metadata tools for complete help on how to get metadata files created using various tools and versions of ArcInfo. If you are using Arc8 and have metadata stored in ArcCatalog, you can export and check the data with the mp aml. See the section (in the link above) called "Managing metadata", or use the command:
Arc: mp bxxxxxxxx\metadata.xml # bxxxxxxxx.met TEXT

It is important to include any information about how the basin was delineated. Include possible constraints on the use of the data within the metadata file in the section called "Use_constraints".

5. QAQC:

The following checks are made on data you submit, they are listed as 'Critical' and 'Non-critical' to indicate their importance. A 'Critical' check that fails will have to be corrected by the study unit.
Critical        a). Basin boundary coverages exist for each fixed, bed-sediment and 
                    tissue, reservoir coring site, and synoptic site that are
                    identified in the station-network (netsite.suid) file or Bio-TDB. For example,
                    if you send a coverage, but the STAID isn't listed in the netsite
                    file then you'll be asked to provide the network code for the site. 
                    If a site exists in the netsite file or Bio-TDB, but no coverage exists, then 
                    questions will arise.

Critical        b). A README file exists to explain sites for which a basin boundary 
                    coverage is not available or applicable (e.g. the site is an outfall 
                    of a sewage treatment plant, or the site is along a conveyance channel).

Critical        c). STAID is correctly populated and defined in the covername.PAT.
        
Non-critical    d). The coverages have polygon topology.

Critical        e). Projections of the coverages comply with the national projection 
                    parameters.

Critical        f). The location for the sampling site are located near the GIS basin-boundary 
                    line. Coverages will be drawn and compared with site locations, using
                    latitude and longitude coordinates from NWIS, to verify that the coverage 
                    encompasses the site. Sites that plot noticeably inside, or outside of 
                    the coverage boundary will be questioned. If you have coordinates that are 
                    collected from NAWQA fieldwork that differ from NWIS C009 and C010 
                    values, a note in the README file would be sufficient.
        
Non-critical    g). The basin boundary coverage drainage area and NWIS drainage area are 
                    within 10%.

Critical        h). FGDC-compliant metadata for each basin boundary coverage are provided 
                    in ASCII format using correct naming convention.
        
Critical        i). CHECKDATA.aml has been run and ALL errors have been corrected. 
                    See next section.
Run the CHECKDATA.AML program to perform a final check to ensure basin boundary coverages are free of potential ARC-related problems. Fix any detected errors; they are marked with an "!" in the output file.

CHECKDATA is in the arc custom patch so you probably have it as an arc command already. Syntax for the CHECKDATA.AML program is as follows:

                Arc:checkdata {NOREPORT | REPORT_FILE}

If you don't have the patch installed, the AML can be downloaded from ftp://hqwiftp.er.usgs.gov/pub/GIS/arcinfo/misc/checkdata.aml.

6. Submit coverages and metadata:

Copy all basin coverages and their associated ASCII metadata files into an empty directory, cd to the new directory, and archive (tar) and compress (gzip) the entire directory. Then copy the compressed archive file into your anonymous ftp area. The syntax for the UNIX tar commands is as follows:

tar -cf - * | gzip -c > /var/ftp/pub/suidsw.targz

(NT users can get tar and gzip utilities from here.

Please do not use WinZip to archive ArcInfo datasets. If you do not have gzip available on NT, you can get it from
 

ftp://hqwiftp.er.usgs.gov/pub/GIS/arcinfo/gbin.tgz


Please e-mail Molly Maupin (mamaupin) with the FTP address of the compressed tarfile when it's available.

THANK YOU!


Top of doc Ground-water GIS Data Request 97 SU Urban LUS GIS Data Request


U.S. Department of the Interior, U.S. Geological Survey 
Maintainer: Molly Maupin
Privacy Statement || Disclaimer
URL: http://idaho.usgs.gov/webwork/mamaupin/guidance/su97_swgis2002.html 
FirstGov, 'Your First Click to the U. S. Government'