Boundary FAQ Metadata
Frequently-anticipated questions:
- Title:
-
Pipe Spring National Monument Vegetation Mapping Project - Park Boundary
- Abstract:
-
This is an Arc/Info coverage consisting of 1 polygon representing the park boundary for Pipe Spring National Monument, Arizona. This GIS dataset is not a legal description of the park's boundary. Use only as a graphic of the park's extent. The boundary was collected by a Trimble GeoXT GPS unit with external antenna, Hurricane, and post processed in GPS Pathfinder Office 3.0 for differential corrections.
- How should this data set be cited?
National Park Service, Pipe Spring National Monument, ZNP Resource Management & Research GIS, 20050122, Park Boundary of Pipe Spring National Monument Vegetation Mapping Project: N/A N/A, N/A, N/A.
Online Links:
- What geographic area does the data set cover?
- West_Bounding_Coordinate: -112.742191
- East_Bounding_Coordinate: -112.737527
- North_Bounding_Coordinate: 36.864707
- South_Bounding_Coordinate: 36.860959
- Description_of_Geographic_Extent: Pipe Spring National Monument
- What does it look like?
- none (none)
-
none
- Does the data set describe conditions during a particular time period?
- Calendar_Date: 09-Nov-2004
- Currentness_Reference: ground condition
- What is the general form of this data set?
- Geospatial_Data_Presentation_Form: vector digital data
- How does the data set represent geographic features?
- How are geographic features stored in the data set?
This is a Vector data set.
It contains the following vector data types (SDTS terminology):
- Entity point (5)
- Point (4)
- GT-polygon composed of chains (1)
- Point (4)
- What coordinate system is used to represent geographic features?
- Grid_Coordinate_System_Name: Universal Transverse Mercator
- Universal_Transverse_Mercator:
-
- UTM_Zone_Number: 12
- Transverse_Mercator:
-
- Scale_Factor_at_Central_Meridian: 0.999600
- Longitude_of_Central_Meridian: -111.000000
- Latitude_of_Projection_Origin: 0.000000
- False_Easting: 500000.000000
- False_Northing: 0.000000
Planar coordinates are encoded using coordinate pair
Abscissae (x-coordinates) are specified to the nearest 0.000005
Ordinates (y-coordinates) are specified to the nearest 0.000005
Planar coordinates are specified in meters
The horizontal datum used is North American Datum of 1983.
The ellipsoid used is Geodetic Reference System 80.
The semi-major axis of the ellipsoid used is 6378137.000000.
The flattening of the ellipsoid used is 1/298.257222.
- How does the data set describe geographic features?
- pisp_bndry
- Feature Class
(Source: National Park Service)
- FID
- Internal feature number.
(Source: ESRI)
Sequential unique whole numbers that are automatically generated.
- Shape
- Feature geometry.
(Source: ESRI)
Coordinates defining the features.
- AREA
- Perimeter of feature in internal units.
(Source: ESRI)
Positive real numbers that are automatically generated.
- PERIMETER
- Perimeter of feature in internal units.
(Source: ESRI)
Positive real numbers that are automatically generated.
- PISP83_
- Unknown field created by coverage originator but not documented.
(Source: Unknown)
Unknown
- PISP83_ID
- Unknown field created by coverage originator but not documented.
(Source: Unknown)
Unknown
- ACRES
- Acres calculated in squared meters.
(Source: Producer defined.)
Positive real numbers.
- SQ_FT
- SQ_FT calculated in squared feet.
(Source: Producer defined.)
Positive real numbers.
- PERIM_FT
- Perimeter calculated in squared meters.
(Source: Producer defined.)
Positive real numbers.
- HECTARES
- Hectares calculated in squared meters.
(Source: Producer defined.)
Positive real numbers.
- LOCATION_A
- Location/asset number as recorded in FMSS.
(Source: Unknown)
Unknown
- EQPT_FEATU
- Equipment/feature number as recorded in FMSS.
(Source: Unknown)
Unknown
- COMMENT
- Information about the park boundary.
(Source: User Defined)
Text Field
- SOURCE
- Data collection method.
(Source: Unknown)
Unknown
- COLLECTOR
- Name of the person who collected the feature.
(Source: Unknown)
Text Field
- PARKCODE
- Four letter code to define the National Park unit.
(Source: NPS)
Park acronym.
- PROGNM
- Program name.
(Source: NPS)
Text Field.
- PRJNM
- Name of the project.
(Source: Unknown)
Text Field.
- MAX_PDOP
- Highest PDOP.
(Source: Unknown)
Unknown
- CORR_TYPE
- What correction occurred.
(Source: Unknown)
Text Field.
- RCVR_TYPE
- Type of GPS unit used.
(Source: Unknown)
Text Field.
- GPS_DATE
- Date it was collected.
(Source: Unknown)
Date.
- GPS_TIME
- The time it was collected.
(Source: Unknown)
Time.
- FEAT_NAME
- Name of the feature in the data dictionary.
(Source: NPS)
Text Field.
- DATAFILE
- File Name.
(Source: Unknown)
Text Field.
- DATA_DICTI
- Name of the data dictionary.
(Source: Unknown)
Text Field.
- AVG_VERT_P
- Feature's vertical precision estimation.
(Source: Unknown)
Unknown
- AVG_HORZ_P
- Feature's horizontal precision estimation.
(Source: Unknown)
Unknown
- AREA_ID
- ID given to the specific record or polygon area.
(Source: Unknown)
Unknown
- X_COORD
- Coordinate for the middle of the polygon(s).
(Source: USGS)
Numerical.
- Y_COORD
- Coordinate for the middle of the polygon(s).
(Source: USGS)
Numerical.
- Entity_and_Attribute_Overview:
-
The following attribute items are generated within ArcInfo: FID, Shape, Area, Perimeter, bndry#, and bndry-ID. Please consult ESRI (http:\\www.esri.com) for information about these first 6 attributes.
The following attribute items were user defined and user calculated (created and populated in the Arc/INFO environment, after collection occurred):
ACRES: area of the features in acres, calculated by multiplying the area item (which is in square meters) by .0002471054.
SQ_FT: area of the feature in square feet, calculated by multiplying the area item (which is in square meters) by 10.76391042.
PERIM_FT: perimeter of the feature in feet, calculated by multiplying the perimeter item (which is in meters) by 3.280839895.
HECTARES: area of the feature in hectares (a metric unit of area equal to 10,000 square meters or 2.47 acres), calculated by the area item (which is in square meters) by .0001.
The following attributes are user defined and have the following definitions:
LOCATION_ASSET: the location/asset number as recorded in FMSS.
EQPT_FEATURE: the equipment/feature number as recorded in FMSS.
COMMENT: general comments about the feature(s).
SOURCE: the data collection method; they are coded as following:
1 = GPS collected (differential)
2 = stable base map
3 = unstable base map,
4 = key punched interpolation
5 = Heads Up Digitizing (HUD)
6 = HUD with NAD 83 aerials
7 = HUD with NAD DOQQs
8 = GPS collected (Recreational grade and not differentially corrected)
9 = the PUT command was utilized to get this feature from another coverage
10 = feature created by buffering an existing feature
11 = scanned basemap
12 = flight GPS
99 = unknown
COLLECTOR: the first initial and last name of the person who collected the feature.
PARKCODE: the four letter acronym that designates the park's name, also known as the alpha-code.
PROGNM: the name of the program needing the information.
PRJNM is the name of the project that the GPS collector is collecting data for.
The following 11 attributes are generated by the export utility in Pathfinder Office 3.0.
MAX_PDOP is the highest PDOP attained while collecting the positions for each feature.
CORR_TYPE is what correction occurred (i.e. differential = differentially corrected with files downloaded from a base station)
RCVR_TYPE is the type of Trimble receiver used to GPS
GPS_DATE is the date the data were collected for that feature.
GPS_TIME is the time the data were collected for that feature.
FEAT_NAME is the name of the feature as it appears in the data dictionary on the GPS.
DATAFILE is the name of the exported file
DATA_DICTIONARY_ is the name of the data dictionary used.
VERT_PREC is an estimation of the feature's vertical precision.
HORZ_PREC is an estimation of the feature's horizontal precision.
AREA_ID is the ID given to the specific record or polygon area.
The following attribute items were added by the Arc/INFO command 'addxy':
X-COORD: the "x" coordinate for the middle of the polygon(s), also known as the longitude of the midpoint. The coordinates for this dataset are projected as UTM NAD83 Zone 12, units meters.
Y-COORD: the "y" coordinate for the middle of the polygon(s), also known as the latitude of the midpoint. The coordinates for this dataset are projected as UTM NAD83 Zone 12, units meters.
- Entity_and_Attribute_Detail_Citation: From dataset creator.
- Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
- National Park Service, Pipe Spring National Monument, ZNP Resource Management & Research GIS
- Who also contributed to the data set?
Sandy White
- To whom should users address questions about the data?
Zion National Park
c/o GIS Specialist
GIS Specialist
Resource Management & Research, GIS Program
Springdale, UT 84767
USA
435-772-0213 (voice)
(435) 772-3829 (FAX)
- Hours_of_Service: 8:00 a.m. to 4:00 p.m. Monday Through Friday
- Contact_Instructions:
-
If you have problems downloading data, please send a fax with your request.
This coverage serves as Pipe Spring National Monument's official park boundary. This data is used to determine land ownership, shared boundaries, fence lines, and is used in many map compositions and analyses conducted for the park. The intended use of all data in the park's GIS library is to support diverse park activities including planning, management, maintenance, research, and interpretation.
- From what previous works were the data drawn?
- GPSdata (source 1 of 2)
-
National Park Service, Pipe Spring National Monument, ZNP Resource Management & Research GIS, Unpublished Material, Global Positioning System (GPS) data: N/A N/A, N/A, N/A.
- Type_of_Source_Media: digital data file
- Source_Scale_Denominator: 500
- Source_Contribution:
-
Serves as the spatial field and corrected GPS data from which coverages were created from.
- AML (source 2 of 2)
-
Office, Trimble Pathfinder 3.0, Unpublished Material, AML Macro.
- Type_of_Source_Media: digital data file
- Source_Scale_Denominator: 500
- Source_Contribution:
-
ARC Macro Language: an organized sequence of ARC/INFO commands that, when executed or "ran" at the ARC prompt, will perform sophisticated geoprocessing operations. In this case, the commands created a coverage from the Trimble data file(s).
- How were the data generated, processed, and modified?
- Date: 09-Nov-2004 (process 1 of 5)
-
The boundary was collected by a Trimble GeoXT GPS unit with external antenna, Hurricane, using the pisp_generic data dictionary. The feature it was stored on was 'boundary'. the process software and version is TerraSync 2.40.
Person who carried out this activity:
Pipe Spring National Monument
c/o Sandy White
SCA GIS Fellow; Aug 2004 - Jan 2005
HC65 Box 5
Fredonia, AZ 86022
USA
(928) 643-7105 (voice)
435-772-3829 (FAX)
Sandy_White@contractor.nps.gov
- Hours_of_Service: 8:00 a.m. - 5:00 p.m. Monday - Friday
- Contact_Instructions: Please contact by email or fax.
Data sources used in this process:
Data sources produced in this process:
- Date: 09-Nov-2004 (process 2 of 5)
-
The boundary's spatial data were downloaded from the GPS unit to the computer, post-processed for differential correction using the base station files from the Dixie National Forest in Cedar City, Utah, and exported to an AML. The process software and version is GPS Pathfinder Office 3.0.
Person who carried out this activity:
Pipe Spring National Monument
c/o Sandy White
SCA GIS Fellow; Aug 2004 - Jan 2005
HC65 Box 5
Fredonia, AZ 86022
USA
(928) 643-7105 (voice)
(928) 643-7583 (FAX)
Sandy_White@contractor.nps.gov
- Hours_of_Service: 8:00 a.m. - 5:00 p.m. Monday - Friday
- Contact_Instructions: Please contact by email or fax.
Data sources used in this process:
Data sources produced in this process:
- Date: 18-Nov-2004 (process 3 of 5)
-
Ran the AML to create the coverage; the resulting coverage was checked for attribute completeness. The process software and version was ARC 9.0.
Person who carried out this activity:
Pipe Spring National Monument
c/o Sandy White
SCA GIS Fellow; Aug 2004 - Jan 2005
HC65 Box 5
Fredonia, AZ 86022
USA
(928) 643-7105 (voice)
(928) 643-7583 (FAX)
Sandy_White@contractor.nps.gov
- Hours_of_Service: 8:00 a.m. - 5:00 p.m. Monday - Friday
- Contact_Instructions: Please contact by email or fax.
Data sources used in this process:
Data sources produced in this process:
- Date: 03-Jan-2005 (process 4 of 5)
-
Corrected source (width, output, and type); added and calculated the following items: acres, sq_ft, perim_ft, hectares, x coordinate, and y coordinate. The process software and version was Arc/INFO 9.0.
Person who carried out this activity:
Pipe Spring National Monument
c/o Sandy White
SCA GIS Fellow; Aug 2004 - Jan 2005
HC65 Box 5
Fredonia, AZ 86022
USA
(928) 643-7105 (voice)
(928) 643-7583 (FAX)
Sandy_White@contractor.nps.gov
- Hours_of_Service: 8:00 a.m. - 5:00 p.m. Monday - Friday
- Contact_Instructions: Please contact by email or fax.
Data sources used in this process:
Data sources produced in this process:
- Date: Unknown (process 5 of 5)
-
Dataset moved.
Data sources used in this process:
- c:\o\metadata_posting\pisp_2005_12\pisp_bndry
- What similar or related data should the user be aware of?
Pipe Spring National Monument and Zion National Park GIS Branch, Unknown, bndry: N/A N/A, N/A, N/A.
- How well have the observations been checked?
Data collection was streamlined through use of data dictionaries' attribute menus installed in the Global Positioning System (GPS) data logger. This procedure enhances attribute accuracy by reducing attribute-related decision making in the field and minimizing keying errors. Park staff have ground checked and verified all features and attributes.
- How accurate are the geographic locations?
GPS accuracy was recorded and exported to the coverage as an attribute. These attributes were retrieved from attribute statistics in ArcCatalog 9.0. The value stated below is the average horizontal precision for the dataset.
- How accurate are the heights or depths?
GPS accuracy was recorded and exported to the coverage as an attribute. These attributes were retrieved from attribute statistics in ArcCatalog 9.0. The value stated below is the average vertical precision for the dataset.
- Where are the gaps in the data? What is missing?
This coverage is 100% complete.
- How consistent are the relationships among the observations, including topology?
This dataset was processed following Zion National Park, GIS Program Standards. These standards verify that every dataset created, imported, and exported, in, from, or to, the park adheres to certain processing standards that are FGDC compliant. This coverage has been checked for misattributed items and proper topology.
Are there legal restrictions on access or use of the data?
- Access_Constraints: none
- Use_Constraints:
-
This GIS dataset is not a legal description of the park's boundary. Use only as a graphic of the park's extent.
- Who distributes the data set? (Distributor 1 of 1)
USGS/CSS/Core Science Analytics and Synthesis
c/o USGS-NPS Vegetation Mapping Program Coordinator
Denver Federal Center, Building 810, Room 8000, MS 302
Denver, Colorado 80225
(303) 202-4220 (voice)
303-202-4219 (FAX)
gs-b-npsveg@usgs.gov
- What's the catalog number I need to order this data set?
Downloadable Data
- What legal disclaimers am I supposed to read?
The U.S. Geological Survey and the National Park Service shall not be held liable for improper or incorrect use of the data described and/or contained herein. These data and related graphics (if available) are not legal documents and are not intended to be used as such.
The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived. It is the responsibility of the data user to use the data appropriately and consistent within the limitations of geospatial data in general and these data in particular. Any related graphics (if available) are intended to aid the data user in acquiring relevant data; it is not approriate to use the related graphics as data.
The U.S. Geological Survey and the National Park Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. It is strongly recommended that these data are directly acquired from an U.S. Geological Survey and National Park Service servers and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully on a computer system at the U.S. Geological Survey, no warranty expressed or implied is made regarding the utility of the data on another system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data. It is also strongly recommended that careful attention be paid to the contents of the metadata file associated with these data. Mention of trade names or commercial products in this metadata report does not constitute endorsement or recommendation for use by the U. S. Department of the Interior, U. S. Geological Survey and National Park Service.
- How can I download or order the data?
- Availability in digital form:
- Cost to order the data: None
- Dates:
- Last modified: 27-Oct-2004
Last Reviewed: 15-Dec-2010
- Metadata author:
-
USGS/CSS/Core Science Analytics and Synthesis
c/o USGS-NPS Vegetation Mapping Program Coordinator
Denver Federal Center, Building 810, Room 8000, MS 302
Denver, Colorado 80225
(303) 202-4220 (voice)
303-202-4219 (FAX)
gs-b-npsveg@usgs.gov
- Metadata standard:
- FGDC Biological Data Profile of the Content Standard for Digital Geospatial Metadata (FGDC-STD-001.1-1999)
- Metadata extensions used:
-
Generated by mp version 2.9.12 on Wed Dec 15 11:23:11 2010
Return to USGS Vegetation Characterization Program at Pipe Spring National Monument
|
Biological Informatics Program 
U.S. Department of the Interior |
U.S. Geological Survey
