1. Michael Gurley / John Murner Oregon Office of Emergency Management October 14, 2015 GIS DATA PREPARATION

2. GIS Data “Issues” PSAP Jurisdiction Layer Layers Affecting Location Accuracy A Standard Data Model Data Improvement Techniques Looking Beyond Development…to Maintenance What this presentation WILL address

3. What is GIS What is NG9-1-1 Why is GIS critical in NG9-1-1 How a call is routed in NG9-1-1 What this presentation will NOT address

4. GIS is important in the current 9-1-1 Environment GIS will continue to be important in the NextGen Environment Our (collective) GIS data is not perfect Improving the data is time well spent Some Things We Can All (Hopefully) Agree On

5. GIS and Geospatial Technologies Key to Next Generation 9-1-1 “Most jurisdictions have adopted GIS data into their operations over recent years. But, the role of GIS has been as a supporting piece, not as a key component of the system. This change will require major rethinking of how GIS data is collected and managed for most 9-1-1 agencies.” (Thursday, September 29th 2011) Changing Role

6. GIS in NextGen

7. ISSUES In the past, good GIS data was a “nice to have” for 9-1-1 Authorities. For NG9-1-1, it is a baseline requirement. Most organizations do not have GIS data that meets the quality and content standards outlined by NENA. In some cases data is degrading. Attitude regarding data status should not be “Our data is good because so- and-so created it” but rather an objective assessment over subjective. More important/alarming is that many organizations do not have the resources and / or capacity to meet the GIS requirements for NG9-1-1 Staffing & Training Little to no time to review and update while still perform regular duties. Needed expertise is dropping with turnover. Too little or too much complexity in both procedures and software.

8. NG911 Study - Kentucky “The PSAP’s will continue to have a central focus on the geographical features with their jurisdiction…Their critical responsibility however, is to recognize that their datasets are no longer standalone – they are part of a much larger mosaic that collectively represents their state and/or region.” (The Commonwealth of Kentucky, August 1, 2009, NG9-1-1 Standards Report) We Are Not Alone

9. NG911 Study - Kentucky “Unlike the previous stages of 9-1-1 services that were centrally focused on the geography and operations of a single PSAP, NG9-1-1 necessitates the development and implementation of a seamless set of lines and polygons that span entire states and regions.” (The Commonwealth of Kentucky, August 1, 2009, NG9-1-1 Standards Report) We Are Not Alone

10. PSAP Jurisdiction Boundaries Critical for NextGen call routing In-demand dataset for wide range of emergency purposes Derived from Emergency Service Zones

11. PSAP Jurisdiction Boundaries ELIMINATE: Gaps Overlaps Duplicate Features PROCESS: Collect existing data Evaluate Identify issues Facilitate resolution Edit data

12. Road Centerlines Invalid or missing attribute values Duplicate line segment identification Route connectivity errors (vital for routing analysis) Overlapping address ranges within the same ESN Site Structure Address Points Invalid or missing attribute values Duplicate site identification – sites with the same address Parity address issues Site address does not match to ALI Database GIS Data Collection and Maintenance Standards NENA 02-014

13. Potential Ranges Not Split at PSAP Boundary PSAP APSAP B 500 501 598 599 Elm St Call comes in from 524 Elm St Location Accuracy

14. Potential Ranges Split at PSAP Boundary PSAP APSAP B 500 501 598 599 Elm St Call comes in from 524 Elm St 549 548550 551 Location Accuracy

15. Actual Ranges Split at PSAP Boundary PSAP APSAP B 500 501 528 529 Elm St Call comes in from 524 Elm St 519 518520 521 Location Accuracy

16. Actual Ranges Split at PSAP Boundary Address Points on structure PSAP APSAP B 500 501 528 529 Elm St Call comes in from 524 Elm St 519 518520 521 Location Accuracy

17. PSAP APSAP B 500 501 528 529 Location and Routing Elm St 519 518520 521 PSAP C Why is this important?

18. Location Accuracy Look familiar?

19. STANDARDIZATION

20. Road Centerlines Site Structure Address Points Emergency Service Zones PSAP Boundaries Road Alias Table GIS Data Model

21. Normalization of location data (addresses) GIS Data Model

22. DATA IMPROVEMENT NENA 71-501

23. DATA IMPROVEMENT Make sure the MSAG and ALI database are in sync with the GIS data.

24. DATA IMPROVEMENT ALI GIS (ROADS) MSAG GIS (ROADS) ALI GIS (ADDPTS)

25. DATA IMPROVEMENT 1.Standardize Address Components 2.Run Comparisons 3.Determine where “fallout” occurs 4.Investigate Discrepancies 5.Correct Errors

26. DATA IMPROVEMENT

27. MAINTENANCE “This is fun and all, but when can I get off the GIS Data Maintenance Merry-Go-Round?”

28. MAINTENANCE Spending a lot of time/money to develop data Letting the data degrade Reaching a point where data is flawed beyond acceptable level

29. MAINTENANCE

30. QA / QC Checks GIS Data Placed on-line in ECRF Incoming Discrepancy Reports (Requires GIS Corrections) GIS Base Data (Development & Maintenance)

31. DATA IMPROVEMENT

32. Prioritize Set achievable goals Don’t chase squirrels Break down the silos Be innovative Beg, Borrow, Steal

33. DATA IMPROVEMENT

34. QUESTIONS Michael Gurley 9-1-1 GIS Coordinator michael.gurley@state.or.us John Murner 9-1-1 GIS Database Analyst john.murner@state.or.us