Boundary FAQ Metadata
Frequently-anticipated questions:
- Title: Fort Larned National Historic Site Vegetation Mapping Project - Park Boundary
- 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.
- How should this data set be cited?
National Park Service, Water Resources, 199904, fols_bndry: National Park Service, Water Resources, Fort Collins, Colorado.
Online Links:
- What geographic area does the data set cover?
- West_Bounding_Coordinate: -103.435694
- East_Bounding_Coordinate: -103.416880
- North_Bounding_Coordinate: 38.049704
- South_Bounding_Coordinate: 38.027160
- Description_of_Geographic_Extent: Fort Larned National Historic Site
- What does it look like?
- Does the data set describe conditions during a particular time period?
- Calendar_Date: Depends on source document used for
- Currentness_Reference: Source boundary dates
- 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):
- What coordinate system is used to represent geographic features?
- 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 coordinates are encoded using coordinate pair
Abscissae (x-coordinates) are specified to the nearest 0.000004
Ordinates (y-coordinates) are specified to the nearest 0.000004
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?
- fols_bndry
- Shapefile Attribute Table
(Source: ESRI)
- FID
- Internal feature number.
(Source: ESRI)
Sequential unique whole numbers that are automatically generated.
- Shape
- Feature geometry.
(Source: ESRI)
Coordinates defining the features.
- AREA
- Area of the polygon in square meters
(Source: Originator)
| Range of values |
|---|
| Minimum: | 180952.09 |
|---|
| Maximum: | 2670254 |
|---|
| Units: | unknown |
|---|
- PERIMETER
- software computed value
(Source: Originator)
| Range of values |
|---|
| Minimum: | 1797.278 |
|---|
| Maximum: | 7959.652 |
|---|
| Units: | unknown |
|---|
- PARKPOLC_
- Unknown
(Source: NPS)
Unknown.
- PARKPOLC_I
- Unknown
(Source: NPS)
Unknown.
- ID
- String
(Source: NPS)
Park acronym name.
- NAME
- String
(Source: NPS)
Park full name.
- NAME2
- String
(Source: NPS)
Information about the source, scale, and date of the boundary.
- 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.
- Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
- National Park Service, Water Resources
- Who also contributed to the data set?
- To whom should users address questions about the data?
National Park Service, Water Resources Division
GIS Specialist
1201 Oak Ridge Drive, Suite 250
Fort Collins, Colorado 80525
USA
Unknown (voice)
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.
- From what previous works were the data drawn?
- NPSWRDPARKBDYSVer.2 (source 1 of 1)
-
National Park Service, Water Resources Division., various, National Park System Boundary Dataset.
- Other_Citation_Details:
-
Information for this element varies for each park included in the dataset. See the boundary-specific WordPerfect file: MAPSTATS.DOC.
- Type_of_Source_Media: Unknown
- Source_Scale_Denominator: varies
- Source_Contribution: National park unit designated boundaries
- How were the data generated, processed, and modified?
- Date: Ranges from 1992 to 1999 (process 1 of 3)
-
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.
Data sources used in this process:
- Date: Unknown (process 2 of 3)
-
The boundary for Fort Larned NHS was selected and exported into shapefile format.
- Date: Unknown (process 3 of 3)
-
Metadata imported.
Data sources used in this process:
- What similar or related data should the user be aware of?
- How well have the observations been checked?
Attribute accuracy was tested by manual comparison o the source with hard copy printouts. Attributes were further verified by visual inspection.
- How accurate are the geographic locations?
- How accurate are the heights or depths?
- Where are the gaps in the data? What is missing?
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.
- How consistent are the relationships among the observations, including topology?
Tests for logical consistency are performed by digitizing software (ATLAS*GIS).
Are there legal restrictions on access or use of the data?
- 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.
- 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
- Availability in digital form:
- Cost to order the data: None
- Dates:
- Last modified: 12-Mar-2008
Last Reviewed: 24-May-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 Mon May 24 09:39:59 2010
Return to USGS Vegetation Characterization Program at Fort Larned National Historic Site
|
Biological Informatics Program 
U.S. Department of the Interior |
U.S. Geological Survey
