1. How GIS will support Ng911 in Indiana
20 September 2016

2. Indiana Statewide 911 Board

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

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

6. ECRF
The Emergency Call Routing Function (ECRF) accurately routes 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).

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

8. 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 service area. The MSAG enables proper routing of E9-1-1 calls and display of appropriate emergency response agencies to the PSAP call taker.

9. 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 call transfers due to misrouted calls. This in turn can help reduce emergency response times and save more lives and property.

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

11. 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 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 Authorities

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

13. What is the role of GIS in NG911?

14. 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”

15. 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.

16. 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

17. 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

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

19. 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

20. Optional data sets
Political Boundaries
Land Parcels
Structures

21. Other considerations Liability for inaccurate data
“National 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 Map Database, otherwise fear of liability and lawsuits may prevent authoritative sources and vendors alike from participating.” 
Legislation needed? 

22. 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)

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

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

26. Wrap up and takeaways

27. Indiana Geographic Information Officer
Jim Sparks
Indiana Geographic Information Officer
gio.in.gov