USGS:Biology Biological Informatics Program Vegetation Characterization Program Fort Larned National Historic Site Boundary Metadata

Boundary Metadata

Metadata also available as - [Questions & Answers] - [Text] - [Adobe Acrobat pdf file]

Metadata:

• Identification_Information
• Data_Quality_Information
• Spatial_Data_Organization_Information
• Spatial_Reference_Information
• Entity_and_Attribute_Information
• Distribution_Information
• Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator: National Park Service, Water Resources

Publication_Date: 199904

Title: fols_bndry

Geospatial_Data_Presentation_Form: vector digital data

Publication_Information:

Publication_Place: Fort Collins, Colorado

Publisher: National Park Service, Water Resources

Online_Linkage:

\\INPSOPN34233\SOPN_GIS\GIS_Data\NPS_data\BEOL\data\basedata\boundary\beol_bound.shp

Online_Linkage:

<http://biology.usgs.gov/npsveg/fols/index.html>

Description:

Abstract:

This dataset contains 340 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 the parks are located north of the equator in the western hemisphere; although a couple parks are south of the equator or in the eastern hemisphere. The dataset was compiled (and edited) from a variety 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 georeferenced to the Latitude-Longitude (NAD27-Clarke 1866) coordinate system. The ID field contains the unique 4 character park code identifying each park. The NAME 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 System's Research Institute's ATLAS*GIS software and is currently maintained in this software. This dataset was created using ATLAS*GIS' Ver. 4.0 Export to ShapeFile command. The ShapeFile was then imported into PC ARC/INFO (SHAPEARC) to create a coverage. The coverage was then exported to NPSUNITS.E00. 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: Depends on source document used for

Currentness_Reference: Source boundary dates

Status:

Progress: Complete

Maintenance_and_Update_Frequency: Irregular

Spatial_Domain:

Description_of_Geographic_Extent: Fort Larned National Historic Site

Bounding_Coordinates:

West_Bounding_Coordinate: -103.435694

East_Bounding_Coordinate: -103.416880

North_Bounding_Coordinate: 38.049704

South_Bounding_Coordinate: 38.027160

Keywords:

Theme:

Theme_Keyword_Thesaurus: none

Theme_Keyword: national park boundaries

Theme_Keyword: federal lands

Place:

Place_Keyword_Thesaurus: None

Place_Keyword: Range includes all 50 states,

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 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 consistent 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 are directly acquired from an NPS server 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 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. Acknowledgement of the NPS Water Resources Division would be appreciated in products derived from these data.

Point_of_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: National Park Service, Water Resources Division

Contact_Position: GIS Specialist

Contact_Address:

Address_Type: mailing and physical address

Address: 1201 Oak Ridge Drive, Suite 250

City: Fort Collins

State_or_Province: Colorado

Postal_Code: 80525

Country: USA

Contact_Voice_Telephone: Unknown

Native_Data_Set_Environment:

Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.0.1324

Data_Quality_Information:

Attribute_Accuracy:

Attribute_Accuracy_Report:

Attribute accuracy was tested by manual comparison o the source with hard copy printouts. Attributes were further verified by visual inspection.

Logical_Consistency_Report:

Tests for logical consistency are performed by digitizing software (ATLAS*GIS).

Completeness_Report:

Dataset contains boundaries for only 340 of 375 park units. The missing units are typically very small (an acre or less) and don't show up 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.

Lineage:

Source_Information:

Source_Citation:

Citation_Information:

Originator: National Park Service, Water Resources Division.

Publication_Date: various

Title: National Park System Boundary Dataset

Geospatial_Data_Presentation_Form: map

Other_Citation_Details:

Information for this element varies for each park included in the dataset. See the boundary-specific WordPerfect file: MAPSTATS.DOC.

Source_Scale_Denominator: varies

Type_of_Source_Media: Unknown

Source_Time_Period_of_Content:

Time_Period_Information:

Single_Date/Time:

Calendar_Date: Unknown

Source_Currentness_Reference: Unknown

Source_Citation_Abbreviation: NPSWRDPARKBDYSVer.2

Source_Contribution: National park unit designated boundaries

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. 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.

Source_Used_Citation_Abbreviation: NPSWRDPARKBDYSVer.2

Process_Date: Ranges from 1992 to 1999

Process_Step:

Process_Description:

The boundary for Fort Larned NHS was selected and exported into shapefile format.

Process_Date: Unknown

Process_Step:

Process_Description: Metadata imported.

Process_Date: Unknown

Source_Used_Citation_Abbreviation: c:\Temp\xml51.tmp

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: 2

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Grid_Coordinate_System:

Grid_Coordinate_System_Name: Universal Transverse Mercator

Universal_Transverse_Mercator:

UTM_Zone_Number: 14

Transverse_Mercator:

Scale_Factor_at_Central_Meridian: 0.999600

Longitude_of_Central_Meridian: -99.000000

Latitude_of_Projection_Origin: 0.000000

False_Easting: 500000.000000

False_Northing: 0.000000

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 0.000004

Ordinate_Resolution: 0.000004

Planar_Distance_Units: meters

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: fols_bndry

Entity_Type_Definition: Shapefile Attribute Table

Entity_Type_Definition_Source: ESRI

Attribute:

Attribute_Label: FID

Attribute_Definition: Internal feature number.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Sequential unique whole numbers that are automatically generated.

Attribute:

Attribute_Label: Shape

Attribute_Definition: Feature geometry.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Coordinates defining the features.

Attribute:

Attribute_Label: AREA

Attribute_Definition: Area of the polygon in square meters

Attribute_Definition_Source: Originator

Attribute_Domain_Values:

Range_Domain:

Range_Domain_Minimum: 180952.09

Range_Domain_Maximum: 2670254

Attribute_Units_of_Measure: unknown

Attribute:

Attribute_Label: PERIMETER

Attribute_Definition: software computed value

Attribute_Definition_Source: Originator

Attribute_Domain_Values:

Range_Domain:

Range_Domain_Minimum: 1797.278

Range_Domain_Maximum: 7959.652

Attribute_Units_of_Measure: unknown

Attribute:

Attribute_Label: PARKPOLC_

Attribute_Definition: Unknown

Attribute_Definition_Source: NPS

Attribute_Domain_Values:

Unrepresentable_Domain: Unknown.

Attribute:

Attribute_Label: PARKPOLC_I

Attribute_Definition: Unknown

Attribute_Definition_Source: NPS

Attribute_Domain_Values:

Unrepresentable_Domain: Unknown.

Attribute:

Attribute_Label: ID

Attribute_Definition: String

Attribute_Definition_Source: NPS

Attribute_Domain_Values:

Unrepresentable_Domain: Park acronym name.

Attribute:

Attribute_Label: NAME

Attribute_Definition: String

Attribute_Definition_Source: NPS

Attribute_Domain_Values:

Unrepresentable_Domain: Park full name.

Attribute:

Attribute_Label: NAME2

Attribute_Definition: String

Attribute_Definition_Source: NPS

Attribute_Domain_Values:

Unrepresentable_Domain:

Information about the source, scale, and date of the boundary.

Overview_Description:

Entity_and_Attribute_Overview:

Three basic attributes are assigned to each park boundary: (1) a unique four character code; (2) a full park name; and (3) boundary source information. 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: Unknown.

Distribution_Information:

Distributor:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: USGS Center for Biological Informatics

Contact_Position: USGS-NPS Vegetation Mapping Program Coordinator

Contact_Address:

Address_Type: mailing and physical address

Address:

United States Geological Survey, Center for Biological Informatics

Address: MS 302, Bldg 810, Room 8000

Address: Denver Federal Center

City: Denver

State_or_Province: Colorado

Postal_Code: 80225

Country: USA

Contact_Voice_Telephone: 303 202-4220

Contact_Facsimile_Telephone: 303 202-4219

Contact_Facsimile_Telephone: 303 202-4229

Contact_Electronic_Mail_Address: gs-b-npsveg@usgs.gov

Resource_Description: Downloadable Data

Distribution_Liability:

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.

Standard_Order_Process:

Digital_Form:

Digital_Transfer_Information:

Format_Name: HTML

Digital_Transfer_Option:

Online_Option:

Computer_Contact_Information:

Network_Address:

Network_Resource_Name:

<http://biology.usgs.gov/npsveg/fols/index.html>

Access_Instructions: Internet Access

Fees: None

Standard_Order_Process:

Digital_Form:

Digital_Transfer_Information:

Format_Name: ARC/INFO

Transfer_Size: 0.134

Digital_Transfer_Option:

Online_Option:

Computer_Contact_Information:

Network_Address:

Network_Resource_Name: National Park Service GIS Web Site; http:/www.nps.gov/gis

Access_Instructions: Internet Access

Fees: None

Metadata_Reference_Information:

Metadata_Date: 20080312

Metadata_Review_Date: 20080814

Metadata_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: USGS-NPS Vegetation Mapping Program Coordinator

Contact_Address:

Address_Type: mailing and physical address

Address:

U.S. Geological Survey, Center for Biological Informatics, MS 302,
Room 8000, Building 810, Denver Federal Center

City: Denver

State_or_Province: Colorado

Postal_Code: 80225

Country: USA

Contact_Voice_Telephone: (303) 202-4220

Contact_Facsimile_Telephone: (303) 202-4219

Contact_Electronic_Mail_Address: gs-b-npsveg@usgs.gov

Metadata_Standard_Name:

FGDC-STD-001.1-1999 Content Standard for Digital Geospatial Metadata, 1998 Part 1: Biological Data Profile, 1999

Metadata_Standard_Version: FGDC-STD-001-1998

Metadata_Extensions:

Online_Linkage:

<http://metadata.nbii.gov/portal/community/Communities/Toolkit/Metadata/FGDC_Metadata/>

Profile_Name: Biological Data Profile FGDC-STD-001.1-1999