Winter 2005 National Data Request
Guidelines for Preparing Ground Water GIS Coverages for National Data Aggregation
12/27/2005
Purpose
This document describes how to prepare the ground water GIS coverages requested for national aggregation.Timetable
The response date for sending the GW GIS data to Kerie Hitt is March 31, 2006. Check the status log for a list of responses to date.Scope
This data request applies to eight study units (ACAD, EIWA, LINJ, LIRB, PUGT, SACR, TRIN, USNK) and covers two items:We are requesting the following:
If the boundary has changed since cycle 1, we need the revised boundary. For example:
GUIDELINES FOR SUBMITTING LUS AND MAS BOUNDARY POLYGON COVERAGE(S)
The study unit Ground Water Specialist and GIS specialist should work together to complete this request. The study unit Ground Water Specialist should prepare the metadata with the help of the GIS Specialist.
Circular 1112 by Gilliom and others contains a description of cycle 1 ground water study design, the selection of agricultural land use studies, and well selection strategy, which still apply to cycle 2 design.
The urban land use study plan contains information about the urban land use design.
Please prepare boundary coverages for:
a) For example, for a major aquifer study (sus1), an agricultural land-use study of vineyards (lusor1a), and an agricultural land-use study of almonds (lusor2a) in the eastern San Joaquin Valley alluvial fans, the SANJ study unit would first prepare a coverage that represents the boundary of the eastern San Joaquin Valley alluvial fans. This boundary also would be the overall boundary for LUS studies because it defines the areal extent of the ground water being sampled.
Although the same polygon represents the overall boundary of the MAS and both LUSs, SANJ would provide one coverage for each network: 1) one for the MAS, 2) one for the vineyard LUS, and 3) one for the almond LUS. Each coverage would have a customized metadata file that describes how the wells were selected for that network.
In this example, these coverages would result:
OVERALL BOUNDARY SUCODE 1. SUS1_BND xxxxsus1 2. LUSOR1A_BND xxxxlusor1 (same as SUS1_BND) 3. LUSOR2A_BND xxxxlusor2 (same as SUS1_BND)b) If a land-use study was not nested within one of the major aquifer studies, submit a separate coverage representing the overall boundary of the hydrolgeologic unit within which the LUS is located and metadata for that coverage.
OVERALL BOUNDARY SUCODE 1. LUSCR1_BND xxxxluscr1
Each time a network is sampled, the associated targeted land use area should be clear. If the targeted area changes, it should be updated, but the original coverage, which was relevant to previous sampling, will be retained.
Most of the time, we would expect the targeted area to be stable from cycle 1 to cycle 2, with any replacement wells falling within the original area.
Continuing the example from #1a, the targeted land use for the vineyard LUS would be the intersection of the vineyards land use with the San Joaquin Valley alluvial fans and the targeted land use for the almonds LUS would be the intersection of the almonds land use with the San Joaquin Valley alluvial fans. Each targeted land use LUS coverage would be nested within the corresponding overall boundary coverage.
SANJ would submit a metadata file for each targeted land use coverage. The coverage metadata should describe the relation of the LUS to the overall boundary coverage and how the wells were selected.
TARGETED LAND USE OVERALL BOUNDARY SUCODE 1. LUSOR1A_TRG 1. LUSOR1A_BND (same as SUS1_BND) xxxxlusor1a 2. LUSOR2A_TRG 2. LUSOR2A_BND (same as SUS1_BND) xxxxlusor2aIn the second example #1b, one coverage of targeted land use would result:
TARGETED LAND USE OVERALL BOUNDARY SUCODE 1. LUSCR1_TRG 1. LUSCR1_BND (not an SUS) xxxxluscr1Here is an illustration showing the concept of LUS boundaries being nested within the MAS boundary. (This example contains three gif files, each about 6 KB.) (See also the map showing the location of ground-water chemistry sites in Circular 1159, p.24, for a similar example.)
The "targeted" coverage for the urban land-use studies should be the coverage that results from the intersection of the areal extent of the aquifer being studied with the residential/commercial land use (minus transportation and industrial land use), provided that the wells were located to achieve at least 75 percent new residential/commercial land use. The "targeted" coverage should be the same one used for random selection of drilling sites. If you have questions as to which coverage to submit, please consult the urban land use study plan or contact Curtis Price (cprice) or Paul Squillace (pjsquill).
Please name each coverage according to the NETCODE of the ground water study.
For example, SUS1_BND or LUSCR1_BND.
For example, LUSCR1_TRG or LUSRC1_TRG.
For all of the above, please use the standard netcodes described in the cycle 2 coding instructions. Please cross-check the coverage names with the network description table so that the netcodes are consistent. For example, if the netcode for a cropland LUS is luscr1, name the coverage LUSCR1_BND or LUSCR1_TRG. Do not name the coverage using LUSAG1 or LUSAG or LUSCR.
| National Projection Parameters | |
|---|---|
| PROJECTION | Albers |
| UNITS | Meters |
| DATUM | NAD83 |
| PARAMETERS | |
| 1st Standard Parallel | 29 30 00 |
| 2nd Standard Parallel | 45 30 00 |
| Central Meridian | -96 00 00 |
| Latitude of Projection's Origin | 23 00 00 |
| False Easting | 0.0 |
| False Northing | 0.0 |
Please include the following fields in the coverage .pat files:
Minimum required items:
AREA 4 12 F 3
PERIMETER 4 12 F 3
NETCODE_BND# 4 5 B
NETCODE_BND-ID 4 5 B
SUCODE 12 12 C Please enter SUCODE as lower case.
Minimum required items:
AREA 4 12 F 3
PERIMETER 4 12 F 3
NETCODE_TRG# 4 5 B
NETCODE_TRG-ID 4 5 B
SUCODE 12 12 C Please enter SUCODE as lower case.
Please prepare an ASCII file of FGDC-compliant metadata to describe each coverage. (Metadata tools are available to guide this process. The tools contain also a section on converting DOCUMENT-style metadata to FGDC-text format. For additional assistance please contact Curtis Price, Kerie Hitt, or Naomi Nakagaki.) Name the metadata file COVERNAME.met.
The coverage documentation must STAND BY ITSELF--that is, people should be able to use the coverage documentation to answer basic questions about the ground water network design without having to go back to planning design papers and other supporting documents. Please make sure that the metadata files give detailed information about the ground water network and well selection process. The study unit Ground-Water Specialist should prepare the metadata with the help of the GIS Specialist.
Here is an EXAMPLE of the METADATA contents for a fictitious ground water study.
Please explain in the documentation how the coverage was used in selecting the well locations and other unique features of the study design. Please describe the process/criteria for selecting the wells and what source coverages (e.g., geology, physiography, hydrology, and so forth) were intersected to derive the study boundary. If wells had to be replaced or added, please describe whether the replacement wells were sited within the original study area. Please describe any changes in the study boundary if the study was expanded or combined with another study or otherwise revised. Please record information about what type of land use is being studied, what crop types or urban areas are involved, and so forth. Please include what netcode corresponds to each boundary coverage.
Please verify that the ground water sampling sites are located within the ground water study areas as defined by the GIS coverages. If some of the sites are located outside the boundary of the corresponding study area, please determine whether the boundary of the study area needs to be changed or whether the coordinates of the stations need to be verified. If the GIS coverage and a site location are correct, but a site still falls outside of the GIS boundary, then the documentation for the boundary coverage should explain why this occurs. For example, the documentation could state that the site was verified in the field to be sampling the correct location and the correct aquifer, but the hydrogeologic unit or land use coverage is generalized.
If you prepare a "master" metadata file and use a copy of this file as the start for the metadata for each specific data set, please remember to tailor each succeeding file to the particular data set being described. If references to the first data set remain in the succeeding metadata files, the metadata does not make any sense.
Please verify the following:
Each polygon coverage can be made up of a single polygon or many discontiguous polygons. If you manage your data in shapefiles, please convert the shapefiles to coverages with the requested projection and send the coverages. Please do not send shapefiles.
All polygons WITHIN the ground water study should be coded with a valid SUCODE. A valid SUCODE should correspond to the SUID + NETCODE used to create the coverage name. Use lowercase letters for SUCODE. Please use the standard netcodes described in the Cycle II Network Coding Guidance.
All polygons OUTSIDE the ground water study, including the universe polygon ("null polygon") and any interior polygons that are "cut out" of the ground water study, should be coded with a blank SUCODE.
Please correct any errors identified by CHECKDATA.
You can use ArcCatalog to create the metadata but please export the metadata to ASCII text.
An AML interface to mp that allows you to run mp similar to an ArcInfo command is available on the USGS ArcInfo Enhancement Patch.
Please correct any errors identified by mp.
Please replace the default information generated as a template from the AML metadata tool called "FGDCMETA" (available on the USGS ArcInfo Enhancement Patch) with information specific to your data sets.
Copy the ground water coverage(s) and ASCII metadata file(s) into an empty directory (folder) named suidgw, where suid is your 4-letter study unit abbreviation.
Select this folder in Windows Explorer, right click, and choose "Send to compressed (zipped) folder." You can answer "No" to the question "Do you want to designate Compressed (zipped) Folders as the application for handling ZIP files?"
Copy the resulting file (suidgw.zip) to enterprise ftp - ftp://ftpint.usgs.gov/private/nonvisible/er/nawqa/gwbnds - or attach the file to an email message to Kerie Hitt (kjhitt@usgs.gov). (Enterprise ftp provides centralized file transfer service.)
Please email Kerie Hitt (kjhitt@usgs.gov) when the files are available in the ftp directory. Please include in your email any other explanatory material you think is necessary for us to understand your submission. Thank you.