{ "currentVersion": 10.81, "cimVersion": "2.6.0", "serviceDescription": "Since 2015, the Public Service Communication Board, VITA Integrated Services Program staff, and staffs\nfrom public safety answering points (PSAPs) have been planning and implementing the deployment of\nNext Generation 9-1-1 (NG911) for the Commonwealth. Transitioning from the legacy\ntelecommunication network provides numerous benefits and flexibility looking towards the future. As\nthe emergency services internet protocol network (ESInet) is deployed, geospatial call routing uses\ngeographic information system (GIS) data and the 911 caller\u2019s location information to identify which\nPSAP will receive the call.\n\nThe process of geospatial call routing relies on the civic address layers (address points and road center\nline maintained by the localities) and a GIS layer representing PSAP boundaries for the operations area\nfor each PSAP. The PSAP boundary file must ensure that every square foot of the Commonwealth is\nassigned to one and only one PSAP. There can be no gaps or overlaps. PSAPs sharing boundaries with\nneighboring states must also meet this same rigor to ensure efficient and consistent delivery of every\n911 call initiated.", "hasVersionedData": false, "hasArchivedData": false, "hasBranchVersionedData": false, "supportsDisconnectedEditing": false, "supportsDatumTransformation": true, "supportsReturnServiceEditsOption": true, "returnServiceEditsHaveSR": true, "supportsQueryDataElements": true, "supportsRelationshipsResource": true, "syncEnabled": false, "extractChangesCapabilities": { "supportsReturnIdsOnly": false, "supportsReturnExtentOnly": false, "supportsReturnAttachments": false, "supportsLayerQueries": false, "supportsGeometry": false, "supportsFeatureReturn": false }, "supportedQueryFormats": "JSON", "maxRecordCount": 2000, "maxRecordCountFactor": 1, "capabilities": "Query", "description": "Since 2015, the Public Service Communication Board, VITA Integrated Services Program staff, and staffs\nfrom public safety answering points (PSAPs) have been planning and implementing the deployment of\nNext Generation 9-1-1 (NG911) for the Commonwealth. Transitioning from the legacy\ntelecommunication network provides numerous benefits and flexibility looking towards the future. As\nthe emergency services internet protocol network (ESInet) is deployed, geospatial call routing uses\ngeographic information system (GIS) data and the 911 caller\u2019s location information to identify which\nPSAP will receive the call.\n\nThe process of geospatial call routing relies on the civic address layers (address points and road center\nline maintained by the localities) and a GIS layer representing PSAP boundaries for the operations area\nfor each PSAP. The PSAP boundary file must ensure that every square foot of the Commonwealth is\nassigned to one and only one PSAP. There can be no gaps or overlaps. PSAPs sharing boundaries with\nneighboring states must also meet this same rigor to ensure efficient and consistent delivery of every\n911 call initiated.", "copyrightText": "Virginia Geographic Information Network (VGIN)", "advancedEditingCapabilities": { "supportsSplit": false, "supportsReturnServiceEditsInSourceSR": true }, "spatialReference": { "wkid": 102746, "latestWkid": 2283, "xyTolerance": 0.003280833333333333, "zTolerance": 2, "mTolerance": 0.001, "falseX": -110512500, "falseY": -88858000, "xyUnits": 3.6916142964165E7, "falseZ": 0, "zUnits": 1, "falseM": -100000, "mUnits": 10000 }, "initialExtent": { "xmin": 1.0813360088760983E7, "ymin": 6298352.49108252, "xmax": 1.2315877032890458E7, "ymax": 7399666.855966105, "spatialReference": { "wkid": 102746, "latestWkid": 2283, "xyTolerance": 0.003280833333333333, "zTolerance": 2, "mTolerance": 0.001, "falseX": -110512500, "falseY": -88858000, "xyUnits": 3.6916142964165E7, "falseZ": 0, "zUnits": 1, "falseM": -100000, "mUnits": 10000 } }, "fullExtent": { "xmin": 1.0963168949750975E7, "ymin": 6481009.7051294, "xmax": 1.2166068171900466E7, "ymax": 7217037.788516477, "spatialReference": { "wkid": 102746, "latestWkid": 2283, "xyTolerance": 0.003280833333333333, "zTolerance": 2, "mTolerance": 0.001, "falseX": -110512500, "falseY": -88858000, "xyUnits": 3.6916142964165E7, "falseZ": 0, "zUnits": 1, "falseM": -100000, "mUnits": 10000 } }, "allowGeometryUpdates": false, "allowTrueCurvesUpdates": true, "onlyAllowTrueCurveUpdatesByTrueCurveClients": true, "supportsApplyEditsWithGlobalIds": false, "supportsTrueCurve": true, "units": "esriFeet", "documentInfo": { "Title": "PSAP Polygons (State Plane North)", "Author": "", "Comments": "Since 2015, the Public Service Communication Board, VITA Integrated Services Program staff, and staffs\nfrom public safety answering points (PSAPs) have been planning and implementing the deployment of\nNext Generation 9-1-1 (NG911) for the Commonwealth. Transitioning from the legacy\ntelecommunication network provides numerous benefits and flexibility looking towards the future. As\nthe emergency services internet protocol network (ESInet) is deployed, geospatial call routing uses\ngeographic information system (GIS) data and the 911 caller\u2019s location information to identify which\nPSAP will receive the call.\n\nThe process of geospatial call routing relies on the civic address layers (address points and road center\nline maintained by the localities) and a GIS layer representing PSAP boundaries for the operations area\nfor each PSAP. The PSAP boundary file must ensure that every square foot of the Commonwealth is\nassigned to one and only one PSAP. There can be no gaps or overlaps. PSAPs sharing boundaries with\nneighboring states must also meet this same rigor to ensure efficient and consistent delivery of every\n911 call initiated.", "Subject": "The intended use of this data layer is for publishing a PSAP polygon as deemed mandatory by the National Emergency Number Association (NENA).", "Category": "", "Keywords": "VGIN,NGSB,NG9-1-1,NENA,PSAP" }, "supportsQueryDomains": true, "supportsQueryContingentValues": true, "layers": [ { "id": 0, "name": "NG911_VA_StatePlaneNorth_NAD83_PSAP_Polygon", "parentLayerId": -1, "defaultVisibility": true, "subLayerIds": null, "minScale": 0, "maxScale": 0, "type": "Feature Layer", "geometryType": "esriGeometryPolygon" } ], "tables": [], "relationships": [], "enableZDefaults": false, "allowUpdateWithoutMValues": false, "supportsVCSProjection": true, "referenceScale": 0 }