National Park System Boundary Dataset

Metadata also available as

Metadata:
Identification_Information:
Citation:
Citation_Information:
Originator: National Park Service, Water Resources Division
Originator: Bureau of Transportation Statistics (comp.)
Publication_Date: 15 March 2002
Title: National Park System Boundary Dataset
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Fort Collins, CO
Publisher: National Park Service, Water Resources Division
Online_Linkage: <http://www.nps.gov/gis/>
Larger_Work_Citation:
Citation_Information:
Originator: Bureau of Transportation Statistics (BTS)
Publication_Date: 2002
Title: National Transportation Atlas Databases (NTAD) 2002
Edition: 2002
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Washinton DC
Publisher: Bureau of Transportation Statistics (BTS)
Online_Linkage: <http://www.bts.gov/gis/>
Description:
Abstract:
This dataset contains 351 National Park System unit boundaries. Under the jurisdiction of the National Park Service (NPS), these park units are located throughout the United States (U.S.) and its territories. Almost all of the parks are located north of the equator in the western hemisphere; although a couple of parks are south of the equator or in the eastern hemisphere. The dataset was compiled (and edited) from a variety of sources: park-based GIS databases; U.S. Geological Survey 7.5' 1:24,000 quadrangles; NPS Park Land Status Maps; legal descriptions; etc. The boundaries are in geographic (decimal degree) North American Datum 1983. The "ID_" field contains the unique four-character park code identifying each park. The "NAME1_" field contains the full park name. The "NAME2_" field contains information about the source, scale, and date of the boundary. The boundaries are generally the designated boundary. Inholdings may or may not be shown depending on the park. This dataset was originally created in Environmental Systems Research Institute's (ESRI) ATLAS*GIS software, and is currently maintained by the NPS with this software. This version of the dataset was created using ESRI's ArcTools 8.0.2 Import to Shapefile from .AGF file command. To obtain the most accurate, current boundary, users should contact the specific park.
Purpose:
These digital park unit boundaries should not be used for any legal boundary disputes. They are intended solely for use only in identifying the general locations of national park units throughout the U.S. This dataset was compiled to assist the NPS Water Resources Division in determining the proximity of certain hydrographic features to national park units and whether national park units are contained in other management units.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 15 March 2002
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: Irregular
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -170.723536
East_Bounding_Coordinate: 145.729807
North_Bounding_Coordinate: 68.655917
South_Bounding_Coordinate: -14.288455
Keywords:
Theme:
Theme_Keyword_Thesaurus: none
Theme_Keyword: National Park Boundaries
Theme_Keyword: Federal Lands
Theme_Keyword: Boundaries
Theme_Keyword: National Park System
Theme_Keyword: National Parks
Theme_Keyword: Preserved Areas
Theme_Keyword: parks
Theme_Keyword: park
Place:
Place_Keyword_Thesaurus: none
Place_Keyword: National Park System
Place_Keyword: United States
Place_Keyword: US
Place_Keyword: USA
Place_Keyword: Puerto Rico
Place_Keyword: Guam
Place_Keyword: Samoa
Place_Keyword: US Territories
Stratum:
Stratum_Keyword_Thesaurus: none
Stratum_Keyword: ground
Temporal:
Temporal_Keyword_Thesaurus: none
Temporal_Keyword: 2002
Access_Constraints: None
Use_Constraints:
These digital national park unit boundaries should not be used for any legal boundary disputes. To obtain the most accurate, current boundary, users should contact the specific park. The National Park Service (NPS) shall not be held liable for improper or incorrect use of the park boundary data described and/or contained herein. These data 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 no better than the original sources from which they were derived. In fact, the data are likely less accurate than the original sources as no attempt has been made to thoroughly error check the data. It is the responsibility of the data user to use the data appropriately and consistently within the limitations of geospatial data in general, and these data in particular. 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 be directly acquired from an NPS server, and not indirectly through other sources that may have changed the data in some way. Although these data have been processed successfully on a computer system at the National Park Service, 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. Acknowledgment of the National Park Service (NPS) and the Bureau of Transportation Statistics (BTS) National Transportation Atlas Database would be appreciated in products derived from these data.
Point_of_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Dean Tucker
Contact_Organization: National Park Service, Water Resources Division
Contact_Position: Natural Resource Specialist
Contact_Address:
Address_Type: mailing and physical address
Address: 1201 OakRidge Drive, Suite 250
City: Fort Collins
State_or_Province: CO
Postal_Code: 80525
Country: USA
Contact_Voice_Telephone: 970-225-3516
Contact_Facsimile_Telephone: 970-225-9965
Contact_Electronic_Mail_Address: Dean_Tucker@nps.gov
Data_Set_Credit:
The National Park Service (NPS) develops and maintains the spatial data from which this geospatial layer was derived.
Native_Data_Set_Environment:
Microsoft Windows NT Version 4.0 (Build 1381) Service Pack 6; ESRI ArcCatalog 8.1.0.642
Cross_Reference:
Citation_Information:
Originator: National Park Service, Water Resources Division
Originator: Bureau of Transportation Statistics (comp.)
Publication_Date: 15 March 2002
Title: National Park System Boundary Dataset
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Ft. Collins, CO
Publisher: National Park Service, Water Resources Division
Online_Linkage: <http://www.nps.gov/gis/>
Larger_Work_Citation:
Citation_Information:
Originator: Bureau of Transportation Statistics (BTS)
Publication_Date: 2002
Title: National Transportation Atlas Databases (NTAD) 2002
Edition: 2002
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Washington DC
Publisher: Bureau of Transportation Statistics (BTS)
Online_Linkage: <http://www.bts.gov/gis/>
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
Attribute accuracy was tested by manual comparison of the source with hard copy printouts. Attributes were further verified by visual inspection.
Quantitative_Attribute_Accuracy_Assessment:
Attribute_Accuracy_Value: unknown
Logical_Consistency_Report:
Tests for logical consistency are performed by digitizing software (ATLAS*GIS). Each park unit is comprised of one or more polygons.
Completeness_Report:
Dataset contains boundaries for only 351 of 385 park units. The missing units are typically very small (an acre or less) and don't appear on U.S. Geological Survey 7.5' quadrangles. Park boundaries are generally the legislative boundary only. No attempt has been made to include or exclude inholdings within the designated boundary. For some parks they are shown; others they are not shown.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
Horizontal accuracy varies depending on the source of each boundary included in the National Park System Boundary Dataset. An accompanying Microsoft Word file, MAPSTATS.DOC, provides more information about the source of each boundary.
Quantitative_Horizontal_Positional_Accuracy_Assessment:
Horizontal_Positional_Accuracy_Value: unknown
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: Park or Regional GIS Coordinator
Publication_Date: Unknown
Title: Park GIS Boundary Layer
Publication_Information:
Other_Citation_Details:
Boundaries obtained in the given year from Park or Regional GIS Staff for the subject park.
Online_Linkage: <http://www.nps.gov/gis>
Source_Scale_Denominator: unknown
Type_of_Source_Media: disc
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: unknown
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: PGBL
Source_Contribution:
For parks that have active GIS or were covered by a Regional GIS coordinator, boundaries were obtained in digital GIS format and converted to the dataset's native format (ATLAS*GIS).
Source_Information:
Source_Citation:
Citation_Information:
Originator: NPS Regional Lands Divisions
Publication_Date: Unknown
Title: NPS Land Status Maps
Geospatial_Data_Presentation_Form: map
Type_of_Source_Media: paper
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: unknown
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: LSM
Source_Contribution:
For parks without GIS programs or Regional GIS coverage, boundaries were obtained by georeferencing and digitizing land status maps prepared by Regional Land Division staff. Georeferencing was accomplished by assigning coordinates from 7.5' U.S. Geological Survey quadrangles to points that also appeared on the land status maps covering a particular park.
Source_Information:
Source_Citation:
Citation_Information:
Originator: U.S. Geological Survey
Publication_Date: Unknown
Title: USGS 7.5' Quadrangles
Geospatial_Data_Presentation_Form: map
Other_Citation_Details:
Boundaries were digitized from 7.5' USGS quadrangles when they weren't available from park or regional GIS staff and where georeferencing land status maps wouldn't yield an increase in accuracy.
Source_Scale_Denominator: 24000
Type_of_Source_Media: paper
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: unknown
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: USGS 7.5' Quadrangle
Source_Contribution:
Park boundaries that weren't available from park or regional GIS staff that were clearly delimited on USGS 7.5' quadrangles were simply digitized.
Process_Step:
Process_Description:
This National Park Boundaries Dataset was compiled by combining park boundaries from a variety of sources: extant digital park-based GIS databases; analog U.S. Geological Survey 7.5' 1:24,000 quadrangles; analog NPS Park Land Status Maps; legal descriptions; etc. Digital boundaries from existing park GIS databases were converted to ATLAS*GIS format and thinned as necessary to reduce the number of points describing the boundary to a maximum of 4,096 (an ATLAS*GIS point/feature limitation at that time). No thinning took place on boundaries obtained in 2000 or later. Analog boundaries from the U.S. Geological Survey 7.5' 1:24,000 quadrangles and from NPS Park Land Status Maps were digitized in ATLAS*GIS and directly incorporated into the master dataset. The Bureau of Transportation Statistics (BTS) used the geospatial data provided by the National Park Service (NPS) in creating this shapefile for the National Transportation Atlas Databases (NTAD) 2002.
Process_Date: Unknown
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Bureau of Tansportation Statistics (BTS)
Contact_Address:
Address_Type: mailing and physical address
Address: Room 3430
Address: 400 Seventh Street, S.W.
City: Washington
State_or_Province: DC
Postal_Code: 20590
Country: USA
Contact_Voice_Telephone: 202-366_DATA
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: G-polygon
Point_and_Vector_Object_Count: 351
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Geographic:
Latitude_Resolution: 0.000001
Longitude_Resolution: 0.000001
Geographic_Coordinate_Units: Decimal degrees
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: park
Entity_Type_Definition: National Park System Unit Boundaries in GIS Format
Entity_Type_Definition_Source: National Park Service
Attribute:
Attribute_Label: FID
Attribute_Definition:
Internal feature number. A system-assigned sequential number uniquely identifying each record in the dataset.
Attribute_Definition_Source: ESRI and BTS
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 0
Range_Domain_Maximum: 350
Attribute_Units_of_Measure: Internal ArcView Feature IDs (0 to 350)
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition:
Feature geometry. The SHAPE attribute is a data attribute inherent to the ESRI shapefile format. It defines the vector data as a point, polyline, or polygon. For further information concerning the definition of SHAPE, consult ESRI documentation.
Attribute_Definition_Source: ESRI and BTS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Polygon
Enumerated_Domain_Value_Definition: Polygonal Shapes as defined by ArcView
Enumerated_Domain_Value_Definition_Source: ArcView Internal Attribute
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: VERSION
Attribute_Definition:
The VERSION is a 2-digit number that will be incremented for all records in the database whenever a new release is distributed. In this release the value is 03.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 00
Range_Domain_Maximum: 99
Attribute:
Attribute_Label: REVISION
Attribute_Definition:
REVISION is a 2-digit number that will be incremented individually for each record whenever a change is made to one of its fields. In this release the value is 00.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 00
Range_Domain_Maximum: 99
Attribute:
Attribute_Label: ID_
Attribute_Definition: Four character park code.
Attribute_Definition_Source: National Park Service
Attribute_Domain_Values:
Unrepresentable_Domain: Four Character Park Codes for Each National Park Unit.
Attribute:
Attribute_Label: NAME1_
Attribute_Definition: Park Name
Attribute_Definition_Source: National Park Service
Attribute_Domain_Values:
Unrepresentable_Domain: free text. Full Name for Each National Park Unit.
Attribute:
Attribute_Label: NAME2_
Attribute_Definition:
Boundary Source. The boundary source information provides the date, scale, and originator of the particular park boundary.
Attribute_Definition_Source: National Park Service
Attribute_Domain_Values:
Unrepresentable_Domain:
free text. Source for each of the boundaries included in the dataset.
Overview_Description:
Entity_and_Attribute_Overview:
Three basic attributes are assigned to each park boundary: (1) a unique four character code (ID_); (2) a full park name (NAME1_); and (3) boundary source information (NAME2_). The four character code is generally a combination of the first two letters of the first two words in a park's name (or the first four letters if the park has a one word name). For example, Yosemite National Park is YOSE while Rocky Mountain National Park is ROMO. The park's full name is the actual given name of the park. The boundary source information provides the date, scale, and originator of the particular park boundary.
Entity_and_Attribute_Detail_Citation:
Three basic attributes are assigned to each park boundary: (1) a unique four character code (ID_); (2) a full park name (NAME1_); and (3) boundary source information (NAME2_). The four-character code is generally a combination of the first two letters of the first two words in a park's name (or the first four letters if the park has a one word name). For example, Yosemite National Park is YOSE while Rocky Mountain National Park is ROMO. The park's full name is the actual given name of the park. The boundary source information provides the date, scale, and originator of the particular park boundary. More information about the park boundaries is provided in the MAPSTATS.DOC file that may be downloaded from the NPS website at: <http://www.nps.gov/gis/national_data.htm>
Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Bureau of Transportation Statistics (BTS)
Contact_Address:
Address_Type: mailing and physical address
Address: Bureau of Transportation Statistics (BTS)
Address: 400 Seventh Street, S.W.
City: Washington
State_or_Province: District of Columbia
Postal_Code: 20590
Country: USA
Contact_Voice_Telephone: 202-366-DATA
Contact_Facsimile_Telephone: 202-366-3640
Contact_Electronic_Mail_Address: answers@bts.gov
Resource_Description: National Transportation Atlas Database (NTAD) 2002
Distribution_Liability: None
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: ESRI Shapefile
Format_Version_Date: 2002
File_Decompression_Technique:
No compression applied. However, if using digital transfer online option, note access instructions.
Transfer_Size: 3.255
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: <http://www.bts.gov/gis/>
Access_Instructions:
Anyone with access to the World Wide Web may connect to the BTS server. To access a specific database, go to the address listed above in the Network Resource Name. The visitor can create a package of the dataset for download in a .zip format (i.e. MS-DOS zip archive). This archived package is stored in a temporary file that can then be copied to the visitor's home directory.
Offline_Option:
Offline_Media: CD-ROM
Recording_Capacity:
Recording_Density: 650
Recording_Density_Units: megabytes
Recording_Format: ISO 9660
Fees: None
Ordering_Instructions:
Call 202-366-DATA, fax 202-366-3640, or E-mail (answers@bts.gov) BTS to request the National Transportation Atlas Databases 2002 CD-ROM. This and other BTS products may be ordered from the BTS Internet website (<http://www.bts.gov/gis/>).
Technical_Prerequisites: Software that can process GIS files.
Available_Time_Period:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2002
Metadata_Reference_Information:
Metadata_Date: 25 April 2002
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Bureau of Transportation Statistics (BTS)
Contact_Address:
Address_Type: mailing and physical address
Address: Bureau of Transportation Statistics (BTS)
Address: Room 3430
Address: 400 Seventh Street, S.W.
City: Washington
State_or_Province: District of Columbia
Postal_Code: 20590
Country: USA
Contact_Voice_Telephone: 202-366-DATA
Contact_Facsimile_Telephone: 202-366-3640
Contact_Electronic_Mail_Address: answers@bts.gov
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Access_Constraints: None
Metadata_Use_Constraints: None
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Generated by mp version 2.7.3 on Wed May 08 14:37:26 2002