| ArcGIS REST Services Directory |
| Home > services > City_of_Richmond_NG911_Boundaries_WFL1 (FeatureServer) > All Layers and Tables | | API Reference |
This feature class is a polygon representation of the Provisioning area that was defined by the following entities: City of Richmond, Henrico County, and Chesterfield County. The Provisioning polygon is the area in which a locality is responsible for providing GIS data to the NextGen (ESInet) system.
This boundary determines what 9-1-1 calls are routed to a PSAP to be answered in an NG9-1-1 i3 environment. PSAP boundaries answer the question “who gets the 9-1-1 call.” Boundaries cannot have gaps or overlap, as these would result in a 9-1-1 call not being routed most efficiently. The PSAP for the City of Richmond is the Department of Emergency Communications (DEC). DEC is the primary PSAP for the City of Richmond and all calls made within the City of Richmond are routed to DEC. These features represent portions of Richmond's PSAP boundary coverage that fall inside of Henrico County's Provisioning boundary. This multipart polygon feature was created to provide Henrico County specific data to submit Richmond's portion of their PSAP boundary to the ESInet. No data can be submitted from outside of a locality's Provisioning Boundary. This feature will be integrated by Henrico County in their PSAP boundary submittal in order to provide full coverage for the extent of Richmond's PSAP boundary in the ESInet.
This boundary determines what 9-1-1 calls are routed to a PSAP to be answered in an NG9-1-1 i3 environment. PSAP boundaries answer the question “who gets the 9-1-1 call.” Boundaries cannot have gaps or overlap, as these would result in a 9-1-1 call not being routed most efficiently. The PSAP for the City of Richmond is the Department of Emergency Communications (DEC). DEC is the primary PSAP for the City of Richmond and all calls made within the City of Richmond are routed to DEC. This geographic area was defined by the following entities: City of Richmond, Henrico County, and Chesterfield County.
The reason sections of Henrico and Chesterfield PSAP boundaries appear as additional polygons in the Richmond PSAP feature class is because no data can be submitted from outside of a locality's Provisioning Boundary. Therefore, each of the surrounding counties clipped their PSAP Boundary with Richmond's shared Provisioning Boundary line. Those exterior pieces were provided to Richmond to be imported into the PSAP boundary feature class as additional polygons to be submitted on their behalf within Richmond's Provisioning area. The City of Richmond performed the same steps and supplied Henrico and Chesterfield with the polygons that lay outside of Richmond's Provisioning area for them to submit on Richmond's behalf.
These features represent portions of Richmond's EMS (Emergency Medical Services) boundary coverage that fall inside of Henrico County's Provisioning boundary. This multipart polygon feature was created to provide Henrico County specific data to submit Richmond's portion of their EMS boundary to the ESInet. No data can be submitted from outside of a locality's Provisioning Boundary. This feature will be integrated by Henrico County in their EMS boundary submittal in order to provide full coverage for the extent of Richmond's EMS boundary in the ESInet.
This feature class is a polygon representation of the EMS service area that was defined by the following entities: City of Richmond, Henrico County, and Chesterfield County. This polygon is geographically contiguous with the corresponding PSAP polygon for the City of Richmond .The data within this EMS boundary will be served by RAA (Richmond Ambulance Authority). Note that RAA is a secondary PSAP, but all calls initially route through DEC (Department of Emergency Communications). RAA is already on the ESInet as of June 2020 and has their own URI.
The reason sections of Henrico and Chesterfield EMS boundaries appear as additional polygons in the Richmond EMS feature class is because no data can be submitted from outside of a locality's Provisioning Boundary. Therefore, each of the surrounding counties clipped their EMS Boundary with Richmond's shared Provisioning Boundary line. Those exterior pieces were provided to Richmond to be imported into the EMS boundary feature class as additional polygons to be submitted on their behalf within Richmond's Provisioning area. The City of Richmond performed the same steps and supplied Henrico and Chesterfield with the polygons that lay outside of Richmond's Provisioning area for them to submit on Richmond's behalf.
These features represent portions of Richmond's Fire (Fire Department service) boundary coverage that fall inside of Henrico County's Provisioning boundary. This multipart polygon feature was created to provide Henrico County specific data to submit Richmond's portion of their Fire boundary to the ESInet. No data can be submitted from outside of a locality's Provisioning Boundary. This feature will be integrated by Henrico County in their Fire boundary submittal in order to provide full coverage for the extent of Richmond's Fire boundary in the ESInet.
This feature class is a polygon representation of the Fire service area that was defined by the following entities: City of Richmond, Henrico County, and Chesterfield County. This polygon is geographically contiguous with the corresponding PSAP polygon for the City of Richmond. The data within this Fire boundary will be served by RFD (Richmond Fire Department). RFD is not on the ESInet as of June 2020.
The reason sections of Henrico and Chesterfield Fire boundaries appear as additional polygons in the Richmond Fire feature class is because no data can be submitted from outside of a locality's Provisioning Boundary. Therefore, each of the surrounding counties clipped their Fire Boundary with Richmond's shared Provisioning Boundary line. Those exterior pieces were provided to Richmond to be imported into the Fire boundary feature class as additional polygons to be submitted on their behalf within Richmond's Provisioning area. The City of Richmond performed the same steps and supplied Henrico and Chesterfield with the polygons that lay outside of Richmond's Provisioning area for them to submit on Richmond's behalf.
These features represent portions of Richmond's Law (Police Department) boundary coverage that fall inside of Henrico County's Provisioning boundary. This multipart polygon feature was created to provide Henrico County specific data to submit Richmond's portion of their Law boundary to the ESInet. No data can be submitted from outside of a locality's Provisioning Boundary. This feature will be integrated by Henrico County in their Law boundary submittal in order to provide full coverage for the extent of Richmond's Law boundary in the ESInet.
This feature class is a polygon representation of the Law (Police) area that was defined by the following entities: City of Richmond, Henrico County, and Chesterfield County. This polygon is geographically contiguous with the corresponding PSAP polygon for the City of Richmond. The data within this Law boundary will be served by RPD (Richmond Police Department). RPD is not on the ESInet as of June 2020.
The reason sections of Henrico and Chesterfield Law boundaries appear as additional polygons in the Richmond Law feature class is because no data can be submitted from outside of a locality's Provisioning Boundary. Therefore, each of the surrounding counties clipped their Law Boundary with Richmond's shared Provisioning Boundary line. Those exterior pieces were provided to Richmond to be imported into the Law boundary feature class as additional polygons to be submitted on their behalf within Richmond's Provisioning area. The City of Richmond performed the same steps and supplied Henrico and Chesterfield with the polygons that lay outside of Richmond's Provisioning area for them to submit on Richmond's behalf.