National Park System Boundary Dataset

Metadata also available as - [Outline] - [SGML] - [XML]

Frequently-anticipated questions:


What does this data set describe?

Title: National Park System Boundary Dataset
Abstract: National Park Service unit boundaries.
  1. How should this data set be cited?

    Service, National Park , and Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS), 2006, National Park System Boundary Dataset: Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS), Washington, DC.

    Online Links:

    This is part of the following larger work.

    Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS), 2006, National Transportation Atlas Databases (NTAD) 2006: Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS), Washington, DC.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -167.535478
    East_Bounding_Coordinate: -66.106411
    North_Bounding_Coordinate: 68.655385
    South_Bounding_Coordinate: 18.464150

  3. What does it look like?

    <URL:national_parks_boundaries_BTS_2006.gif> (GIF)

  4. Does the data set describe conditions during a particular time period?

    Calendar_Date: Mar-2006
    Currentness_Reference: publication date

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      This is a Vector data set. It contains the following vector data types (SDTS terminology):

      • G-polygon (555)

    2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.000001. Longitudes are given to the nearest 0.000001. Latitude and longitude values are specified in Decimal degrees.

      The horizontal datum used is D_WGS_1984.
      The ellipsoid used is WGS_1984.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257224.

  7. How does the data set describe geographic features?

    parks
    National Park System Unit Boundaries in GIS Format (Source: RITA/BTS)

    REVISION
    REVISION is a 2-digit number that will be incremented individually for each record whenever a change is made to one of its fields. (Source: RITA/BTS)

    Range of values
    Minimum:00
    Maximum:99

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    PARKNAME
    Park Name (Source: NPS)

    Character Value

    DESIGNATIO
    Designation of National Park (Source: NPS)

    Character Value

    ALPHACODE
    Four Letter code to Describe National Park (Source: NPS)

    Character Value

    STABBR
    U.S. Postal Service two letter state abbreviation for the additional states (Source: NPS)

    Formal codeset
    Codeset Name:Official List of State Postal Abbreviations
    Codeset Source:U.S. Postal Service

    STFIPS
    State FIPS code (Source: RITA/BTS)

    Formal codeset
    Codeset Name:Federal Information Processing Standard
    Codeset Source:National Institute of Standards and Technology (NIST)

    Shape_Area
    Area of feature in internal units squared. (Source: ESRI)

    Positive real numbers that are automatically generated.

    VERSION
    The VERSION is a 2-digit number that will be incremented for all records in the database whenever a new release is distributed. (Source: RITA/BTS)

    Range of values
    Minimum:00
    Maximum:99

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape_Leng

    Entity_and_Attribute_Overview:
    Attributes are as follows: Alphacode (4 letter code, unique to each park), ParkName, Designation, State, St FIPS


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

    National Park Service

  3. To whom should users address questions about the data?

    National Park Service (NPS)
    c/o Tennille Williams
    GIS Specialist
    12795 W. Alameda Pkwy
    Denver, CO 80225
    USA

    970.225.3569 (voice)
    tennille_williams@nps.gov

    Hours_of_Service: M-F 8-5 Mountain Time


Why was the data set created?

Service wide boundary set for display and general analysis purposes. 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.


How was the data set created?

  1. From what previous works were the data drawn?

    (source 1 of 3)
    Dean Tucker, Water Resource Division, Unpublished Material, NPSUnits.

    Other_Citation_Details:
    Park boundaries collected and digitized for the Horizon Project.

    (source 2 of 3)
    David Duran, GIS Division, Unknown, ParkDave.

    Other_Citation_Details: Park boundaries collected from Parks and Regions in 2001.

    (source 3 of 3)
    Johnson, Roger, Unknown, unit classification boundaries.

    Other_Citation_Details:
    Land Rersources Division has been creating hardcopy segment maps containing boundary data since the 1960's. This data is currently being converted to a digital vector format and added to the collection as it become available. Additionally as existing boundary data is modified and/or new parks units units are acquired they are added to the collection.

  2. How were the data generated, processed, and modified?

    Date: 01-Jun-2005 (process 1 of 5)
    Boundaries for eighty units were replaced with verified versions from the Lands Resources Division according to the procedures defined in the Lands Acquisition Procedures Manual Chapter 5. As boundary data from the Land Resources Division has separate polygons for individual types of units like Denali National Park and Denali National Preserve, there are currently one hundred and two total Lands records in the dataset that can be identified by querying for [GIS_Notes] = "Lands" in the attribute table. These parks include: Alagnak Wild River (ALAG), Aniakchak National Monument and Preserve (ANIA), Antietam National Battlefield (ANTI), Appomattox Court House National Historical Park (APCO), Arches National Park (ARCH), Arlington House - Robert E. Lee Memorial (ARHO), Bering Land Bridge National Preserve (BELA), Black Canyon of the Gunnison National Park (BLCA), Brices Cross Roads National Battlefield Site (BRCR), Buffalo National River (BUFF), Carl Sandburg Home (CARL), Cape Krusenstern National Monument (CAKR), Capulin Volcano National Monument (CAVO), Carlsbad Caverns National Park (CAVE), Castillo de San Marcos National Monument (CASA), Cedar Creek and Belle Grove (CEBE), Chiricahua National Monument (CHIR), Clara Barton National Historic Site (CLBA), Cumberland Gap National Historical Park (CUGA), Denali National Park (DENA), Devils Tower National Monument (DETO),Florissant Fossil Beds (FLFO), Fort Bowie National Historic Site (FOBO), Fort Sumter National Monument (FOSU), Gates of the Arctic National Park (GAAR), Greenbelt Park (GREE),George Washington Memorial Parkway (GWMP), Gila Cliff Dwellings National Monument (GICL), Glacier Bay National Park (GLBA), Golden Gate National Recreation Area (GOGA), Grant-Kohrs Ranch National Historic Site (GRKO), Great Sand Dunes National Park and Preserve (GRSA), Harpers Ferry National Historical Park (HAFE), Herbert Hoover National Historic Site (HEHO), Homestead National Monument (HOME), Hubbell Trading Post National Historic Site (HUTR), Jimmy Carter National Historic Site (JICA), Katmai National Park (KATM), Kenai Fjords National Park (KEFJ), Kings Canyon National Park (KICA), Klondike Gold Rush National Historical Park (KLGO), Kobuk Valley National Park (KOVA), Lake Clark National Park (LACL), Lake Mead National Recreation Area (LAME), Little Bighorn Battlefield National Monument (LIBI), Lyndon Baines Johnson Memorial Grove (LYBA), Mammoth Cave National Park (MACA), Manassas National Battlefield Park (MANA), Martin Luther King Jr. National Historic Site (MALU), Mojave National Preserve (MOJA), Monocacy National Battlefield (MONO), Natchez National Historical Park (NATC), National Capital Parks (NACA), Noatak National Preserve (NOAT), Organ Pipe Cactus National Monument (ORPI), Petrified Forest National Park (PEFO), Pictured Rocks National Lakeshore (PIRO), Piscataway Park (PISC), Point Reyes National Seashore (PORE), Santa Monica Mountains National Recreation Area (SAMO), Sand Creek Massacre National Historic Site (SAND), Scotts Bluff National Mounment (SCBL), Sequoia National Park (SEQU), Sitka National Historical Park (SITK), Theodore Roosevelt Island National Memorial (THIS), Timpanogos Cave National Monument (TICA), Tumacacori National Historical Park (TUMA), Tupelo National Battlefield (TUPE), Tuskegee Airmen National Historic Site (TUAI), Tuzigoot National Monument (TUZI), Valley Forge National Historical Park (VAFO), Washita Battlefield National Historic Site (WABA), White Sands National Monument (WHSA), Whitman Mission National Historic Site (WHMI), Wolf Trap Farm Park (WOTR), Wrangell-St. Elias National Park (WRST), Wupatki National Monument (WUPA), Yosemite National Park (YOSE), Yucca House National Monument (YUHO), Yukon-Charley Rivers (YUCH)

    Person who carried out this activity:

    National Park Service
    Land Resources Division Chief Cartographer
    301 S. Howes Street Suite 208
    Fort Collins, CO 80522
    USA

    PPFL_LandsNET@NPS.GOV

    Hours_of_Service: M-F 7:30-5:00 Mountain Time
    Date: 2002 (process 2 of 5)
    Two sets of boundaries were collected and compared. The main set was obtained from David Duran, who collected boundaries from each region in the summer of 2001. The second set was obtained from Dean Tucker, who digitized boundaries for the Horizon Project. The main set from David Duran was determined to contain the most recent boundary information. Parks missing from David's set were added from Deans set. Those parks are..........Antietam NB Arlington House,Benjamin Franklin NMEM, Big Hole NB, Catoctin Mountain Park, Chesapeake and Ohio Canal NHP, Chimney Rock NHS, Fort Point NHS, Fredericksburg NC, George Washington Memorial Parkway, Green Springs, Harpers Ferry NHP, International Peace Garden, John F. Kennedy Center for the Performing Arts, Kalaupapa NHP, Manassas NBP, McLoughlin House NHS, Monocacy NB, National Capital Parks - Central and East, Olympic NP, Prince William Forest Park, Rock Creek Park, San Francisco Maritime NHP, Thaddeus Kosciuszko NMEM, and Wolf Trap Farm Park for the Performing Arts. Park/Region staff were consulted for parks with major differences between the two sets.

    Person who carried out this activity:

    National Park Service
    GIS Specialist/Cooperator
    1201 Oakridge Drive Suite 200
    Fort Collins, CO 80525
    USA

    970.225.3569 (voice)
    970.225.3585 (FAX)
    waso-nrpc_nrgis@nps.gov

    Hours_of_Service: M-F 8-5 Mountain Time
    Date: 2006 (process 3 of 5)
    Downloaded the national parks shapefile from <http://www.nps.gov/gis/national_data.htm>. Converted the shapefile to a coverage so that every polygon would have unique ID. Used ArcGIS Geoprocessing tools to intersect with the state layer and dissolve using state name and park name. Completed the QC using ArcGIS for topological and attribute verification.

    Person who carried out this activity:

    Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
    c/o Geospatial Information Program
    400 7th Street, S.W.
    Washington, DC 20590

    202-366-DATA (voice)
    202-366-3640 (FAX)
    answers@bts.gov

    (process 4 of 5)
    Dataset moved.

    Data sources used in this process:

    • data\land_use_cover\national_parks_boundaries\national_parks_boundaries_BTS

    (process 5 of 5)
    Dataset copied.

    Data sources used in this process:

    • data\land_use_cover.mdb

  3. What similar or related data should the user be aware of?

    Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS), 2006, National Transportation Atlas Databases (NTAD) 2006: Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS), Washington, DC.

    Online Links:

    This is part of the following larger work.

    .


How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

    RITA/BTS quality checks the attributes after the shapefile was downloaded. RITA/BTS quality checks were to cross reference the place dataset with the state dataset, to determine that the spatial data and attribute data were accurate. Several records have no state listed in the state column, have inaccurate states associated to the polygon, or their polygons were associated to the wrong state. RITA/BTS found these errors and contributed with building the dataset. RITA/BTS went through the US territories and updated the FIPS code.

  2. How accurate are the geographic locations?

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

    Dataset is believed to be 100% complete. Please contact originator with corrections and updates.

    The data set is complete but subject to continual updates to reflect boundary amendments, legislation, and acquisitions, and improved processing techniques. The data is being regularly updated with verified boundaries from NPS Land Resources Division. Please contact the data originator with corrections and update suggestions.

  5. How consistent are the relationships among the observations, including topology?

    Tests for logical consistency are performed by digitizing software (ATLAS*GIS). Each park unit is comprised of one or more polygons.


How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints: None
Use_Constraints:
To be used for display and general analysis purposes only. 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 Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS) National Transportation Atlas Database 2006 would be appreciated in products derived from these data.

  1. Who distributes the data set? (Distributor 1 of 2)

    Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
    c/o Geospatial Information Program
    400 7th Street, SW Room 4117
    Washington, DC 20950
    USA

    202-366-DATA (voice)
    202-366-3640 (FAX)
    answers@bts.gov

  2. What's the catalog number I need to order this data set?

    National Transportation Atlas Database (NTAD) 2006

  3. What legal disclaimers am I supposed to read?

  4. How can I download or order the data?

  5. What hardware or software do I need in order to use the data set?

    Must have access to GIS software such as ESRI's ArcView or ArcINFO, or other compatible software to view the data


  1. Who distributes the data set? (Distributor 2 of 2)

    Louisiana Oil Spill Coordinator's Office
    c/o David Gisclair
    Technical Assistance Program (TAP) Director

    (225) 219-5800 (voice)
    (225) 219-5802 (FAX)
    david.gisclair@la.gov

  2. What's the catalog number I need to order this data set?

  3. What legal disclaimers am I supposed to read?

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: 05-Apr-2006
Metadata author:
Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
c/o Geospatial Information Program
Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)
Washington, DC 20590
USA

202-366-DATA (voice)
202-366-3640 (FAX)
answers@bts.gov

Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:


This page is <http://lagic.lsu.edu/data/losco/national_parks_boundaries_bts_2006_faq.html>
LA Geographic Information Center (LAGIC)
Generated by mp version 2.9.2 on Mon Oct 01 15:03:12 2007