{ "currentVersion": 11.2, "cimVersion": "3.2.0", "serviceDescription": "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. \n\nThe 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. \n\nUltimately, 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.", "hasVersionedData": false, "hasArchivedData": false, "hasBranchVersionedData": false, "supportsDisconnectedEditing": false, "supportsDatumTransformation": true, "supportsReturnServiceEditsOption": true, "returnServiceEditsHaveSR": true, "supportsQueryDataElements": true, "datesInUnknownTimezone": false, "supportsRelationshipsResource": true, "syncEnabled": false, "supportedExportFormats": "sqlite,filegdb,shapefile,csv,geojson", "extractChangesCapabilities": { "supportsReturnIdsOnly": false, "supportsReturnExtentOnly": false, "supportsReturnAttachments": false, "supportsLayerQueries": false, "supportsGeometry": false, "supportsFeatureReturn": false, "supportsReturnHasGeometryUpdates": false, "supportsFieldsToCompare": false, "supportsServerGens": false }, "supportedQueryFormats": "JSON", "maxRecordCount": 10000, "maxRecordCountFactor": 1, "capabilities": "Query,Extract", "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. \n\nThe 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. \n\nUltimately, 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.", "copyrightText": "National Park Service", "advancedEditingCapabilities": { "supportsSplit": false, "supportsReturnServiceEditsInSourceSR": true, "supportsAsyncApplyEdits": true, "supportsApplyEditsbyUploadID": true, "supportedApplyEditsUploadIDFormats": "JSON", "supportsMultipatchOptionForServiceEdits": true, "supportedApplyEditsOptions": {"supportedEditingOptions": 0} }, "spatialReference": { "wkid": 4269, "latestWkid": 4269, "xyTolerance": 8.983152841195213E-9, "zTolerance": 0.001, "mTolerance": 0.001, "falseX": -400, "falseY": -400, "xyUnits": 1.125899906842624E13, "falseZ": -100000, "zUnits": 10000, "falseM": -100000, "mUnits": 10000 }, "initialExtent": { "xmin": -86.48756936602706, "ymin": -64.94805770039338, "xmax": 61.491829047743494, "ymax": 119.32028152580008, "spatialReference": { "wkid": 4269, "latestWkid": 4269, "xyTolerance": 8.983152841195213E-9, "zTolerance": 0.001, "mTolerance": 0.001, "falseX": -400, "falseY": -400, "xyUnits": 1.125899906842624E13, "falseZ": -100000, "zUnits": 10000, "falseM": -100000, "mUnits": 10000 } }, "fullExtent": { "xmin": -215.35277521199998, "ymin": -14.285511887999974, "xmax": 145.72530260300005, "ymax": 68.14305600000006, "spatialReference": { "wkid": 4269, "latestWkid": 4269, "xyTolerance": 8.983152841195213E-9, "zTolerance": 0.001, "mTolerance": 0.001, "falseX": -400, "falseY": -400, "xyUnits": 1.125899906842624E13, "falseZ": -100000, "zUnits": 10000, "falseM": -100000, "mUnits": 10000 } }, "allowGeometryUpdates": false, "allowTrueCurvesUpdates": false, "onlyAllowTrueCurveUpdatesByTrueCurveClients": false, "supportsApplyEditsWithGlobalIds": false, "supportsTrueCurve": true, "units": "esriDecimalDegrees", "documentInfo": { "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. \n\nThe 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. \n\nUltimately, 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" }, "supportsQueryDomains": true, "supportsQueryContingentValues": true, "layers": [ { "id": 0, "name": "Points of Interest", "parentLayerId": -1, "defaultVisibility": true, "subLayerIds": null, "minScale": 0, "maxScale": 0, "type": "Feature Layer", "geometryType": "esriGeometryPoint" } ], "tables": [], "relationships": [], "enableZDefaults": false, "allowUpdateWithoutMValues": false, "supportsVCSProjection": true, "datumTransformations": [ { "geoTransforms": [ { "wkid": 108190, "latestWkid": 108190, "transformForward": true, "name": "WGS_1984_(ITRF00)_To_NAD_1983" } ] }, { "geoTransforms": [ { "wkid": 108190, "latestWkid": 108190, "transformForward": false, "name": "WGS_1984_(ITRF00)_To_NAD_1983" } ] } ], "referenceScale": 0 }