National Park Service GIS Data Services Directory
JSON | SOAP

NationalDatasets/NPS_Public_POIs (FeatureServer)

View In:   ArcGIS Online Map Viewer

View Footprint In:   ArcGIS Online Map Viewer

Service Description: The purpose of creating and utilizing a spatial data standard is to consolidate spatial data and integrate the existing feature attribute information into a national database for reporting, planning, analysis and sharing purposes. The primary benefit of using a spatial data standard remains the organization and documentation of data to allow users to share spatial data between parks, regions, programs, other federal agencies, and the public, at the national level. Ultimately, the point of interest container will go through a formal data standard development process. This will lead to wider use and more comprehensive access to all of our available point of interest data and provide a more integrated approach to point of interest data management across the NPS and at all levels: park, region, program, and national. Until then, the point of interest spatial data container will serve as a pseudo-standard and enable data stewards to begin standardizing point of interest data.

All Layers and Tables

Has Versioned Data: false

MaxRecordCount: 10000

Supported Query Formats: JSON

Supports Query Data Elements: true

Layers: Description: The purpose of creating and utilizing a spatial data standard is to consolidate spatial data and integrate the existing feature attribute information into a national database for reporting, planning, analysis and sharing purposes. The primary benefit of using a spatial data standard remains the organization and documentation of data to allow users to share spatial data between parks, regions, programs, other federal agencies, and the public, at the national level. Ultimately, the point of interest container will go through a formal data standard development process. This will lead to wider use and more comprehensive access to all of our available point of interest data and provide a more integrated approach to point of interest data management across the NPS and at all levels: park, region, program, and national. Until then, the point of interest spatial data container will serve as a pseudo-standard and enable data stewards to begin standardizing point of interest data.

Copyright Text: National Park Service

Spatial Reference: 102100  (3857)


Initial Extent:
    XMin: -1.670008064072256E7
    YMin: -7355599.336511599
    XMax: 1.3917563927899914E7
    YMax: 1.63934481615834E7
    Spatial Reference: 102100  (3857)

Full Extent:
    XMin: -1.9001897194E7
    YMin: -1606992.2201999985
    XMax: 1.62220659278E7
    YMax: 1.0489640562200002E7
    Spatial Reference: 102100  (3857)

Units: esriMeters

Document Info:
    Title: National Park Service Public Points of Interest
    Author:
    Comments: The purpose of creating and utilizing a spatial data standard is to consolidate spatial data and integrate the existing feature attribute information into a national database for reporting, planning, analysis and sharing purposes. The primary benefit of using a spatial data standard remains the organization and documentation of data to allow users to share spatial data between parks, regions, programs, other federal agencies, and the public, at the national level. Ultimately, the point of interest container will go through a formal data standard development process. This will lead to wider use and more comprehensive access to all of our available point of interest data and provide a more integrated approach to point of interest data management across the NPS and at all levels: park, region, program, and national. Until then, the point of interest spatial data container will serve as a pseudo-standard and enable data stewards to begin standardizing point of interest data.
    Subject: National Park Service Public Points of Interest
    Category:
    Keywords: National Park Service, NPS, Points of Interest, POIs
    AntialiasingMode: null
    TextAntialiasingMode: null
Enable Z Defaults: false

Supports ApplyEdits With Global Ids: false

Support True Curves : true

Only Allow TrueCurve Updates By TrueCurveClients : false

Supports Return Service Edits Option : true

Supports Dynamic Layers: false

Child Resources:   Info   Query Data Elements   Relationships

Supported Operations:   Query   Query Contingent Values   QueryDomains   Extract Changes