These ESRI shape files are of National Park Service tract and boundary data that was created by the Land Resources Division. Tracts are numbered and created by the regional cartographic staff at the Land Resources Program Centers and are associated to the Land Status Maps. This data should be used to display properties that NPS owns and properties that NPS may have some type of interest such as scenic easements or right of ways.

This service depicts National Park Service tract and boundary data that was created by the Land Resources Division. NPS Director's Order #25 states: "Land status maps will be prepared to identify the ownership of the lands within the authorized boundaries of the park unit. These maps, showing ownership and acreage, are the 'official record' of the acreage of Federal and non-federal lands within the park boundaries. While these maps are the official record of the lands and acreage within the unit's authorized boundaries, they are not of survey quality and not intended to be used for survey purposes." As such this data is intended for use as a tool for GIS analysis. It is in no way intended for engineering or legal purposes. The data accuracy is checked against best available sources which may be dated and vary by location. NPS assumes no liability for use of this data. The boundary polygons represent the current legislated boundary of a given NPS unit. NPS does not necessarily have full fee ownership or hold another interest (easement, right of way, etc...) in all parcels contained within this boundary. Equivalently NPS may own or have an interest in parcels outside the legislated boundary of a given unit. In order to obtain complete information about current NPS interests both inside and outside a unit’s legislated boundary tract level polygons are also created by NPS Land Resources Division and should be used in conjunction with this boundary data. To download this data directly from the NPS go to https://irma.nps.gov Property ownership data is compiled from deeds, plats, surveys, and other source data. These are not engineering quality drawings and should be used for administrative purposes only. The National Park Service (NPS) shall not be held liable for improper or incorrect use of the data described and/or contained herein. These data and related graphics 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. The related graphics are intended to aid the data user in acquiring relevant data; it is not appropriate to use the related graphics as data. 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.

National parks and other protected areas are important for preserving landscapes and biodiversity worldwide. An essential component of the mission of the United States (U.S.) National Park Service (NPS) requires understanding and maintaining accurate inventories of species on protected lands. We describe a new, national-scale synthesis of amphibian species occurrence in the NPS system. Many park units have a list of amphibian species observed within their borders compiled from various sources and available publicly through the NPSpecies platform. However, many of the observations in NPSpecies remain unverified and the lists are often outdated. We updated the amphibian dataset for each park unit by collating old and new park-level records and had them verified by regional experts. The original version of this dataset contained occurrence records for 292 of the 424 NPS units and includes updated taxonomy, international and state conservation rankings, hyperlinks to a supporting reference for each record, specific notes, and related fields which can be used to better understand and manage amphibian biodiversity within a single park or group of parks. This version of the dataset (Version 1.4) now contains amphibian occurrence records for 336 of the 431 NPS units as of publication in 2024.

The US National Park Service manages 84.4 million acres that include the United States" 63 national parks, many national monuments, and other conservation and historical properties. These lands range from the 13 million acre Wrangell-St. Elias National Park and Preserve in Alaska to the 0.02 acre Thaddeus Kosciuszko National Memorial in Pennsylvania.Dataset SummaryPhenomenon Mapped: Administrative boundaries of U.S. National Park Service landsGeographic Extent: 50 United States, District of Columbia, Puerto Rico, US Virgin Islands, Guam, American Samoa, and Northern Mariana IslandsData Coordinate System: WGS 1984Visible Scale: The data is visible at all scalesSource: NPS Administrative Boundaries of National Park System Units layerPublication Date: April, 2025This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Park Service lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "national park service" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "national park service" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

The US National Park Service manages 84.4 million acres that include the nation's 59 national parks, many national monuments, and other conservation and historical properties. These lands range from the 13 million acre Wrangell-St. Elias National Park and Preserve in Alaska to the 0.02 acre Thaddeus Kosciuszko National Memorial in Pennsylvania.Dataset SummaryPhenomenon Mapped: Administrative boundaries of units in the United States National Park Service system. Not all lands within the administrative boundaries are owned by the National Park Service.Coordinate System: Web Mercator Auxiliary SphereExtent: 50 United States, District of Columbia, Puerto Rico, US Virgin Islands, Guam, American Samoa, and Northern Mariana IslandsVisible Scale: The data is visible at all scalesSource: NPS Administrative Boundaries National Park System Units layerPublication Date: January 2024This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Park Service lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this layer? This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "national park service" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "national park service" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.

This service depicts National Park Service tract and boundary data that was created by the Land Resources Division. NPS Director's Order #25 states: "Land status maps will be prepared to identify the ownership of the lands within the authorized boundaries of the park unit. These maps, showing ownership and acreage, are the 'official record' of the acreage of Federal and non-federal lands within the park boundaries. While these maps are the official record of the lands and acreage within the unit's authorized boundaries, they are not of survey quality and not intended to be used for survey purposes." As such this data is intended for use as a tool for GIS analysis. It is in no way intended for engineering or legal purposes. The data accuracy is checked against best available sources which may be dated and vary by location. NPS assumes no liability for use of this data. The boundary polygons represent the current legislated boundary of a given NPS unit. NPS does not necessarily have full fee ownership or hold another interest (easement, right of way, etc...) in all parcels contained within this boundary. Equivalently NPS may own or have an interest in parcels outside the legislated boundary of a given unit. In order to obtain complete information about current NPS interests both inside and outside a unit’s legislated boundary tract level polygons are also created by NPS Land Resources Division and should be used in conjunction with this boundary data. To download this data directly from the NPS go to https://irma.nps.gov Property ownership data is compiled from deeds, plats, surveys, and other source data. These are not engineering quality drawings and should be used for administrative purposes only. The National Park Service (NPS) shall not be held liable for improper or incorrect use of the data described and/or contained herein. These data and related graphics 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. The related graphics are intended to aid the data user in acquiring relevant data; it is not appropriate to use the related graphics as data. 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.

OPEN Data View service. The Wildland Fire Risk Assessment project was developed by the National Park Service's Fire and Aviation Management program as a response to the devastating 2011 wildfire season. This project developed a consistent assessment method that has been applied to NPS units nationwide regardless of variations in climate, fuels, and topography.The assessment, based on Firewise® assessment forms, evaluates access, surrounding environment, construction design and materials, and resources available to protect facilities from wildland fire. The data collected during the assessment process can be used for:Identifying, planning, prioritizing and tracking fuels treatments at unit, regional and national levels, and Developing incident response plans for facilities and communities within NPS units.The original spatial data for the assessments comes from a variety of sources including the NPS Buildings Enterprise Dataset, WFDSS, NPMap Edits, manually digitized points using Esri basemaps as a reference at various scales, and GPS collection using a multitude of consumer and professional grade GPS devices. The facilities that have been assessed and assigned a facility risk rating have been ground-truthed and field verified. (In some rare occasions, facilities have been verified during remote assessments. Those that have been remotely assessed are marked as such). The resulting data is stored in a centralized geodatabase, and this publicly available feature layer allows the user to view that data.The NPS Facilities feature layer includes the following layers and related tables:Facility - A facility is defined by the NPS as an asset that the NPS desires to track and manage as a distinct identifiable entity. In the case of wildland fire risk assessments, a facility is most often a structure but in special instances, a park unit may wish to identify and assess other at-risk features such as a historic wooden bridge or an interpretive display. The facilities are assessed based on access, the surrounding environment, construction design, and protection resources and limitations, resulting in a numerical score and risk adjective rating for each facility. These ratings designate the likelihood of ignition during a wildland fire. The facilities are symbolized by their respective risk rating.Community - A community is a group of five or more facilities, a majority of which are within 600 feet of each other, that share common access and protection attributes. The community concept was developed to facilitate data collection and entry in areas with multiple facilities and where it made sense to apply treatments and tactics at a scale larger than individual facilities. Most of the community polygons are created using models in ArcMap, but some may have been created or edited in the field using a Trimble GPS unit. *The NPS Facilities layer is updated continually as new wildfire risk assessments are conducted and the Wildland Fire Risk Assessment project progresses. The assessment data contained here is the most current data available.*More information about the NPS Wildland Fire Risk Assessment Project, and the NPS Facilities data itself, can be found at the New Wildland Fire Risk Assessments website. This site provides information on the data collection process, additional ways to access the data, and how to conduct assessments yourself (for both NPS and non-NPS facilities).FACILITY ATTRIBUTES
Unit_ID NWCG Unit ID, Two letter state code and three letter unit abbreviation, for example UTZIP for Zion National Park in Utah.

Fire_Bldg_ID User maintained unique ID for Facility layer.

Building ID Unique Id from the NPS Enterprise Buildings dataset.

FMSS ID Unique ID for the facility in the NPS FMSS database.

Community ID Unique ID linking facility to a community

Assess Scale Indicates if the facility is part of a community/ will be included in a community assessment. Communities are pre-defined by regional GIS staff and visible in this map as a blue perimeter.
Answer "Yes" if you are adding a facility point within a predefined community.

Common Name Name of the structure. In most cases, the name comes from the NPS FMSS database.

Map Label Numerical label used for mapping purposes.

Owner Indicates who owns the structure being assessed.

Facilty Type Indicates the facility type OR if the facility has been REMOVED, DESTROYED, has NO WILDLAND RISK, is PRIVATE - NO SURVEY REQUIRED or DOES NOT REQUIRE A SURVEY (because it is planned for removal).

Facility Use What is the primary use of the facility?

Building Occupied Is the building occupied?

Community Name Name of the community the facility is located within, if any.

Field Crew Field crew completing the assessment.

Last Site Visit Date Date which the facility was visited and assessment data reviewed/updated.

Location General location within the unit – may use FMUs, watersheds, or other identifier. One location may contain multiple communities and individual facilities. Locations are used to filter data for reports and map products.

PrimaryAccess Primary method of accessing the facility.

IngressEgress Number of routes into and away from the facility.

AccessWidth Width of the road or driveway used to access the facility.

AccessCond Grade and surface material of the road or driveway used to access the facility.

BridgeCond Condition, based on load limits and construction.

Turnaround Describes how close can a fire apparatus drive to the facility and once there, whether it can turnaround.

BldgNum Is the facility clearly signed or numbered?

FuelLoad Fuel loading within 300 ft of the facility (see appendix D of the Wildfire Risk Assessment User Guide)

FuelType Predominant fuel type within 300 ft of the facility.

DefensibleSpace Amount of defensible space around the facility, see criteria for evaluating defensible space in the Wildfire Risk Assessment User Guide.

Topography Predominant slope within 300 ft of facility.

RoofMat Roofing material used on the facility.

SidingMat Siding material used on the facility.

Foundation Describes the facility’s foundation.

Fencing Indicates presence of any wooden attachments, fencing, decking, pergola, etc. and fuels clearance around those attachments.

Firewood Firewood distance from facility.

Propane Inidicates if a propane tank exists within 200 feet of a structure and if there is any fuels clearance around the propane tank(s).

Hazmat List of hazmat existing on the site.

WaterSupply Water supply available to the facility.

OverheadHaz Identifies the presence of overhead hazards that will limit aerial firefighting efforts.

SafetyZone Identifies the presence of any potential safety zones.

SZRadius Radius of any potential safety zones.

Obstacles Additional obstacles, not already included in assessment, that will limit firefighting efforts- to include items such as UXO, hazmat,etc. If there are additional obstacles, be sure to comment in Assessment Comments or Tactic descriptions where appropriate.

TriageCategory Refer to IRPG for descriptions of each category. This information will be displayed in the NIFS Structure Triage layer for incident response.

Score Sum of attribute values for all assessment elements including access, environment, structure and protection portions of the assessment.

Rating Wildland fire risk rating based on score. Ratings are No Wildland Risk, Low, Moderate and High. Rating indicates likelihood if facility igniting if a wildland fire occurs.

ProtectionLevel Inidcates structures which are priority for protection during a wildfire. For Alaska Region data, indicates identified protection level for structure. For lower 48, enter ‘Unknown’ unless specified by local unit.

ProtLevelApprovalName Name of person who designated Protection Level

ProtLevelApprovalDate Date Protection Level Designated

ResourcesOfConcern Indicates if it is necessary to contact park staff before engaging in suppression activities because special resources (natural, cultural, historic) of concern are present?

AssessComments Explain any aspects of the assessment that require extra detail.

RegionCode NPS Region Code - AKR, IMR, NER, NCR, MWR, PWR or SER

UnitCode

NPS Unit Code

ReasonIncluded Why is the point in the dataset – NPS owned, Treatment Planning, Protection Responsibility, Planning (other than treatments). Intent of the dataset is to document wildfire risk for NPS owned structures. Other structures or facilities may be included at the discretion of the unit's fire management staff.

Restriction How can the data be shared – Unrestricted, Restricted - No Third Party Release, Restricted – Originating Agency Concurrence, Restricted – Affected Cultural Group Concurrence, Restricted - No Release, Unknown. Only unrestricted data is included in this dataset.

Local_ID Field which can be used to store unique ids linking back to any local datasets.

RevisitInterval How many years will it take for the fuels to change significantly enough to change the score and rating for this facility?

IsVisited Use this field to keep track of what you have done during a field session. Filter on this field to see what has been assessed and what still needs visited during a field data collection session.

DeleteThis Users enter yes if this is this a duplicate or was no facility found.
If you know the facility was REMOVED or DESTROYED, go back to Facility Type and enter that information there.

Data_Source

FirewiseZone1 List of treatments needed to

Trail data are used for many purposes including planning and management, mapping and condition assessment, routing and navigation, public information, emergency response, and research. A current, accurate representation of park trails is needed for national reporting and a variety of mapping requirements at all levels of the National Park Service and the general public. A National-level dataset allows the NPS to communicate a consistent and high-quality trails database to NPS staff, partners, visitors, and entities that produce maps and location-based services of park units. The collection, storage, and management of trail-related data are important components of everyday business activities in many Federal and State land-managing agencies, trail organizations, and businesses. From a management perspective, trail data must often mesh closely with other types of infrastructure, resource, and facility enterprise data. For the public using paper maps, the internet, GPS or other instrumentation, standard data formats enable users to consistently and predictably identify specific trails and a core set of corresponding information. Today, digital trail data are a necessity throughout a trail data management life-cycle, from trail planning through design, construction, operation, and maintenance. Automating, sharing, and leveraging trail data through this widely accepted standard can provide a variety of important benefits: Efficiency - creating and gathering trail data that are standardized and readily usable. Compatibility - compiling data from one project or discipline that can be compatible with other applications; Consistency - using the same standards, meshing data produced by one organization with that developed by another; Speed - hastening the availability of data through a reduction in duplicative efforts and lowered production costs (Applications can be developed more quickly and with more interoperability by using existing standards-compliant data); Conflict resolution - resolving conflicting trail data more easily if compliant to the same standards; Reliability - improving the quality of shared trail data by increasing the number of individuals who find and correct errors; and Reusability - allow maximum reuse across agencies and support objectives of EGovernment (E-Gov) initiatives and enterprise architecture.IRMA Data Store Reference

This dataset contains the current trail network within Glacier National Park, Montana. These data represent the latest revision to official and mapped hiking trails in Glacier. The dataset is based on the initial USGS 7.5 minute topographic mapping that was published in 1968. However, beginning in 1997 Glacier National Park staff have re-mapped (and continue to improve the mapping of) much of Glacier's 700+ mile trail network using Global Positioning Systems (GPS) and high-resolution imagery. Specific data sources employed in mapping trail segments is documented in the source information contained in this metadata.

© Glacier National Park GIS Program

This layer is a component of Glacier National Park.

This map service provides layers covering a variety of different datasets and themes for Glacier National Park. It is meant to be consumed by internet mapping applications and for general reference. It is for internal NPS use only. Produced November 2014.

© Denver Service Center Planning Division, IMR Geographic Resources Division, Glacier National Park

These ESRI shape files are of National Park Service tract and boundary data that was created by the Land Resources Division. Tracts are numbered and created by the regional cartographic staff at the Land Resources Program Centers and are associated to the Land Status Maps. This data should be used to display properties that NPS owns and properties that NPS may have some type of interest such as scenic easements or right of ways.

These ESRI shape files are of National Park Service tract and boundary data that was created by the Land Resources Division. Tracts are numbered and created by the regional cartographic staff at the Land Resources Program Centers and are associated to the Land Status Maps. This data should be used to display properties that NPS owns and properties that NPS may have some type of interest such as scenic easements or right of ways.

These ESRI shape files are of National Park Service tract and boundary data that was created by the Land Resources Division. Tracts are numbered and created by the regional cartographic staff at the Land Resources Program Centers and are associated to the Land Status Maps. This data should be used to display properties that NPS owns and properties that NPS may have some type of interest such as scenic easements or right of ways.

These ESRI shape files are of National Park Service tract and boundary data that was created by the Land Resources Division. Tracts are numbered and created by the regional cartographic staff at the Land Resources Program Centers and are associated to the Land Status Maps. This data should be used to display properties that NPS owns and properties that NPS may have some type of interest such as scenic easements or right of ways.

These data depict Road Segment Centerlines and attributes for roads that are managed and maintained by the National Park Service. Road data are used for many purposes including planning and management, mapping and condition assessment, routing and navigation, public information, emergency response, and research. A current, accurate representation of park roads is needed for national reporting and a variety of mapping requirements at all levels of the National Park Service and the general public. A National-level dataset allows the NPS to communicate a consistent and high-quality roads database to NPS staff, partners, visitors, and entities that produce maps and location-based services of park units. The collection, storage, and management of road-related data are important components of everyday business activities in many Federal and State land-managing agencies, road organizations, and businesses. From a management perspective, road data must often mesh closely with other types of infrastructure, resource, and facility enterprise data. For the public using paper maps, the internet, GPS or other instrumentation, standard data formats enable users to consistently and predictably identify specific trails and a core set of corresponding information. Today, digital road data are a necessity throughout a road data management life-cycle, from road planning through design, construction, operation, and maintenance. Automating, sharing, and leveraging road data through this widely accepted standard can provide a variety of important benefits: Efficiency – creating and gathering road data that are standardized and readily usable. Compatibility – compiling data from one project or discipline that can be compatible with other applications; Consistency – using the same standards, meshing data produced by one organization with that developed by another; Speed – hastening the availability of data through a reduction in duplicative efforts and lowered production costs (Applications can be developed more quickly and with more interoperability by using existing standards-compliant data); Conflict resolution – resolving conflicting road data more easily if compliant to the same standards; Reliability – improving the quality of shared road data by increasing the number of individuals who find and correct errors; and Reusability – allow maximum reuse across agencies and support objectives of EGovernment (E-Gov) initiatives and enterprise architecture.

These ESRI shape files are of National Park Service tract and boundary data that was created by the Land Resources Division. Tracts are numbered and created by the regional cartographic staff at the Land Resources Program Centers and are associated to the Land Status Maps. This data should be used to display properties that NPS owns and properties that NPS may have some type of interest such as scenic easements or right of ways.

These ESRI shape files are of National Park Service tract and boundary data that was created by the Land Resources Division. Tracts are numbered and created by the regional cartographic staff at the Land Resources Program Centers and are associated to the Land Status Maps. This data should be used to display properties that NPS owns and properties that NPS may have some type of interest such as scenic easements or right of ways.

This report documents the acquisition of source data, and calculation of land cover summary statistics datasets for four National Park Service Greater Yellowstone Network park units and six custom areas of analysis: Bighorn Canyon National Recreation Area, Grand Teton National Park, John D. Rockefeller Jr. Memorial Parkway, Yellowstone National Park, and the six custom areas of analysis. The source data and land cover calculations are available for use within the National Park Service (NPS) Inventory and Monitoring Program. Land cover summary statistics datasets can be calculated for all geographic regions within the extent of the NPS; this report includes statistics calculated for the conterminous United States. The land cover summary statistics datasets are calculated from multiple sources, including Multi-Resolution Land Characteristics Consortium products in the National Land Cover Database (NLCD) and the United States Geological Survey’s (USGS) Earth Resources Observation and Science (EROS) Center products in the Land Change Monitoring, Assessment, and Projection (LCMAP) raster dataset. These summary statistics calculate land cover at up to three classification scales: Level 1, modified Anderson Level 2, and Natural versus Converted land cover. The output land cover summary statistics datasets produced here for the four Greater Yellowstone Network park units and six custom areas of analysis utilize the most recent versions of the source datasets (NLCD and LCMAP). These land cover summary statistics datasets are used in the NPS Inventory and Monitoring Program, including the NPS Environmental Settings Monitoring Protocol and may be used by networks and parks for additional efforts.

These ESRI shape files are of National Park Service tract and boundary data that was created by the Land Resources Division. Tracts are numbered and created by the regional cartographic staff at the Land Resources Program Centers and are associated to the Land Status Maps. This data should be used to display properties that NPS owns and properties that NPS may have some type of interest such as scenic easements or right of ways.

These ESRI shape files are of National Park Service tract and boundary data that was created by the Land Resources Division. Tracts are numbered and created by the regional cartographic staff at the Land Resources Program Centers and are associated to the Land Status Maps. This data should be used to display properties that NPS owns and properties that NPS may have some type of interest such as scenic easements or right of ways.

The Digital Geohazard-GIS Map of the Mesa Verde National Park, Colorado is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (meve_geohazard.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (meve_geohazard.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (meve_geohazard.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (meve_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (meve_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (meve_geohazard_metadata_faq.pdf). Please read the meve_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (meve_geohazard_metadata.txt or meve_geohazard_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:50,000 and United States National Map Accuracy Standards features are within (horizontally) 25.4 meters or 83.3 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).