How GIS will support Ng911 in Indiana 20 September 2016

Indiana Statewide 911 Board www.in911.net

https://transition. fcc. gov/pshs/docs/csric/CSRIC-WG4B-Final-Report

“NG9-1-1 utilizes GIS data for 9-1-1 Emergency Call Routing Functions and Location Validation Functions (ECRF/LVF)” NATIONAL 9-1-1 MAP DATABASE, GeoComm / Esri Whitepaper, May 13, 2016

ECRF The Emergency Call Routing Function (ECRF) accurately routes 9-1-1 calls to the appropriate PSAP based on the caller’s location and in a NG9-1-1 system, the ECRF along with the Location Validation Function (LVF) replace the current Master Street Address Guide (MSAG). http://www.geo-comm.com/industries/ng9-1-1/ng911gis/

Public safety answering point (psap) A PSAP is an answering location for E9-1-1 calls originating in a specified area.

Master street address guide (msag) An MSAG is a compressed listing of every street name, house number range, community, and Emergency Service Number (ESN) for a community. The MSAG defines all possible valid address locations within the 9-1-1 service area. The MSAG enables proper routing of E9-1-1 calls and display of appropriate emergency response agencies to the PSAP call taker.

Why use gis for ecrf? Geospatial call routing enables more accurate call routing than traditional E9-1-1 systems and can reduce the number of 9-1-1 call transfers due to misrouted 9-1-1 calls. This in turn can help reduce emergency response times and save more lives and property.

Location validation function (LVF) In addition to being used when routing 9-1-1 calls, NG9-1-1 systems use GIS data before a 9-1-1 call is placed to see if the address is valid for 9-1-1. The GIS data provisioned to the LVF is identical to the GIS database provisioned to the ECRF.

Benfits of ng911 Ability to receive voice, video, text, or data sent over IP networks from various communications devices (e.g., wireline, wireless, VoIP, sensors, etc.) – making 9-1-1 more accessible for all users Automatic and advanced data sharing between all public safety responders, PSAPs, emergency management, traffic operations, etc. – The ESInet has been designed as an Emergency Services network, not just a “9-1-1 network”. This network can provide access to public safety databases, remote systems, provide transport for Radio over IP (RoIP), etc. – Data is shared from the caller to PSAP to dispatch to responders and beyond – NG9-1-1 is designed to be flexible, open, non-proprietary (standards-based), and a secure interoperable internetwork (a “system of systems”) Advanced call handling processing and dynamic routing of callers based on caller’s geographic location and most appropriate PSAP – Rule-based configurability and control for PSAPs and 9-1-1 Authorities

Status map of ng911 infrastructure deployment as of 9-5-2016

What is the role of GIS in NG911?

Is the role of GIS in NG 911 one of providing location data or one of geospatial analysis, or both? A. The role of GIS in NG911 is to provide accurate location data to support Call Routing Functions and Location Validation Functions Required Data Address points Road centerlines PSAP boundaries ESA boundaries Orthoimagery Optional Data Local Administrative Boundaries Land Parcels Structures (Strong need for structures on “campuses”

Address Points Currently part of voluntary Data Sharing Initiative Address point locations vary by county Who maintains the data? Varies. Usually the PSAP director maintains the MSAG, required updates in 24 to 48 hours. Only updated when a range needs extended, or new street, or street name change. Kinds of address points: Access to property from road/highway Center of dwelling Center of parcel Which is most useful to NG 911?  Dwelling is first choice, but the ESRI community data model has place for both dwelling and entrance points that share same address. Can all be of use if we document what it is? Yes. Multiple residences in one location (example: apartment building, or college dorms) handled differently county-by- county.  ESRI model places stacked points.

Road Centerlines How will centerlines be used? 2nd level of data for address matching? Yes Routing? Yes (for dispatch, not NG911) Address ranges needed Currently part of voluntary data sharing initiative Address ranges and attributes differ by county Updates are performed at different intervals

PSAP Boundaries Does this data exist in either paper or GIS form? Not statewide. 126 Indiana PSAPs State Police boundary overlap other PSAP boundaries but are mostly around major roads

Emergency service area Boundaries Does this data exist in either paper or GIS form? No. Kosciusko has 40 or 50 of these.

Orthoimagery Currently being updated for State Base product: 1 foot resolution, 4- band, leaf off About 1/3 of counties will buy-up to 6” resolution

Optional data sets Political Boundaries Land Parcels Structures

Other considerations Liability for inaccurate data “National 9-1-1 Map Database participation must not increase liability of participants. There must be a legal framework for managing and mitigating liability risks for GIS software and service providers, and authoritative sources of map information fed into the National 9-1-1 Map Database, otherwise fear of liability and lawsuits may prevent authoritative sources and vendors alike from participating.”  Legislation needed? 

Other considerations Availability of Required Data Address points, road centerlines, and local administrative boundaries are part of current data sharing initiative. Sufficient? Building PSAP boundary data is manageable (126 PSAPs) Do you have Emergency Service Areas mapped? Future orthoimagery funding is not certain. Structures? What is business case? (Ortho + LiDAR + processing + QC)

Other considerations Requirements of GIS Databases “The National 9-1-1 Map Database must support NG9-1-1 PSAP mapping systems (GIS data contained in the database must be downloadable and consumable by 9-1-1 PSAPs) and must be capable of providing NG9-1-1 Location to Service Translation queries…” NATIONAL 9-1-1 MAP DATABASE, GeoComm / Esri Whitepaper, May 13, 2016

Other considerations Finish by 2020 Timing Clean-up data Complete data Share data Aggregate and prepare data Address legal issues Finish by 2020

Wrap up and takeaways

Indiana Geographic Information Officer Jim Sparks Indiana Geographic Information Officer jsparks@iot.in.gov gio.in.gov 317-234-5889