Maintainer: Molly Maupin
Privacy Statement || Disclaimer
URL: http://idaho.usgs.gov/webwork/mamaupin/guidance/su01_swgisSum03.html
These guidelines are directed to the FY01 study units for the first data aggregation of Cycle-II.
Purpose:
This document describes the contents and procedures for preparing the first set of SW GIS basin boundary data from FY01 study units. It explains what basin boundaries are being requested and specific information about coverage and metadata content and format.
Scope:
For the first Cycle-II SW GIS data aggregation from FY01 study units please submit a complete set of the following:
It is anticipated that the largest percentage of time and effort for this request will involve bringing Cycle-I basin boundary documentation (possibly built using the old DOCUMENT command) to FGDC compliancy. USGS Enterprise GIS supports a metadata webpage that is very useful. It explains how to import old ARCINFO DOCUMENT metadata into ArcCatalog, which is the preferred method. There are instructions on how to create a master template that can be used to create text formatted, FGDC-compliant metadata files for coverages that were created the same way. ArcCatalog is the recommended software that NAWQA is using to create, update and export metadata for basin boundary coverages. DOCUMENT metadata is no longer acceptable.
If you have questions about missing basin boundaries, or metadata conversion and updating processes, please call the following persons:
Guidelines
The following are standard conventions and procedures for SW GIS coverages creation and submittal:
Some sites are identified in the request spreadsheet that will need to have two separate coverages submitted, one which delineates the total potential (contributing and non-contributing) drainage area, and another which delineates only the contributing drainage area. The total potential drainage area coverage should include contributing plus non-contributing areas, and should depict a larger area than the other coverage. This coverage might include those areas that provide flow during storm conditions or when certain man-made contributions are in effect. The total potential drainage area coverages should be named with a 't' prefix before the unique 8-digit STAID number, and these coverages will be used to compile a separate set of ancillary data to aid in hydrologic analyses of water-quality during high-flow conditions. The other coverage should delineate only the contributing drainage area for the site, and should depict a smaller geographic area. This coverage name should have the 'b' prefix before the unique 8-digit STAID number.
For sites that have only one coverage that depicts the drainage area, a 'b' prefix should be concatenated with the 8-digit STAID. If your study unit has reservoir coring sites, name the basin boundary coverages 'r' + 8-digit 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. Here are a few examples:
STAID COVERAGE NAME 04087000 b04087000 04086307 b04086307 435426488092701 b43542641 435426488092702 b43542642 02334080 r02334080
PROJECTION ALBERS UNITS METERS DATUM NAD83 PARAMETERS 29 30 00 45 30 00 -96 00 00 23 00 00 0.0 0.0
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 CAdditional 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. Use leading zeros in station numbers where applicable.
By-products of the coverages you provide, such as statistics of fertilizer/pesticide use, landuse may have wide distribution outside the USGS. Therefore, the metadata you provide about how the coverage was initially created will preempt future questions. It is important to include any possible constraints on the use of the data. Metadata should accurately reflect the particulars for the basin in which it references. Using a master template is fine but individual editing of some sections of the metadata are necessary.
Critical a). A basin boundary exist for each SW Status and Trends and SWQA sites, as well as the specially
noted selected sites (see SCOPE section at top of this page)
Critical b). A README file exists that lists all sites in the current submission. It may contain any other
explanatory information about coverage names, or information pertinent to particular coverages.
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 sample site are located within the basin boundary.
Coverages will be drawn and compared with site locations, using coordinates from NWIS, to verify that
the coverage includes 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%.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.
Critical h). FGDC-compliant metadata for each basin boundary coverage are provided in ASCII format using correct
naming convention. Metadata files should be checked using mp and errors should be cleaned up.
Critical i). CHECKDATA.aml has been run and ALL errors have been corrected. See next section.
Arc:checkdata {NOREPORT | REPORT_FILE}
If you don't have the patch installed, the AML can be downloaded from http://sd.water.usgs.gov/usgs/nawqa_gis/checkdata/. CHECKDATA will be run on the coverages after you submit them and is considered a critical error and will precipitate questions if there are errors.
A README file is a handy way to convey special circumstances about coverages, such as when standard naming conventions don't work, or when there are missing basins that will not be provided in the current aggregation. Please create and store a README file in the directory where the coverages are located, so that when they are 'packaged up and sent' using instructions in the next section, the README file goes with the coverages. If there are no special circumstances for coverages in your aggregation, then put only a list of all coverages that are present in the current aggregation.
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
THANK YOU!
| Ground-water 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/su01_swgisSum03.html |
|