Utah AGRC: Mapping Support for Enterprise 911 Bert Granberg NGAC Meeting September 5, 2013

Mapping Resources for 911 – Find and validate incident locations – Assign response jurisdiction – Provide context – Post-incident analysis

Important Map Layers – Road Centerlines w/ Address Ranges – Site/Structure Address Points – Highway Mile Markers & Exits – Jurisdictional Boundaries: law, fire, EMS, state and federal agencies – Common Place names schools, parks, businesses, landmarks, trailheads, etc. – Base Maps and Aerial Photography – Cell towers – Water features – Utilities/Infrastructure

Map Data: Road Centerlines

Map Data: Address Points

Solve the Problem: “Ma'am, you’ll need to send someone out to the highway to guide the ambulance to your property”

Map Data: Jurisdictional Boundaries

Map Data: Common Places

Map Data: Base Maps

AGRC’s Activity – Statewide road centerline maintenance and coordination with Counties – Local Address System Updates – Address Point Dataset – Technical Mapping Support to PSAPs – Highway Reference System Milepost and Exits – Other GIS Framework Data enhancement – Detailed Annual Activity Report to 911 CommitteeDetailed Annual Activity Report to 911 Committee

Enterprise Approach 911 is the primary focus, but benefits are extended across emergency response: – 911 Call Routing – 911 Call Taking – Dispatching – Responders – Operations/Analysis Ideally, all use the same, quality map resources

Next Gen 911: GIS becomes a core/foundational part of 911 – GIS role starts at the routing of 911 calls to PSAPs – Map data must be highly available, connected, and interchangeable, just like the communications system

Conclusion 911 Mapping Resources: State of Utah is well-positioned Expectations of mapping will expand Data quality and currency Servers, processes, etc Continued support will be required to sustain current efforts and meet coming NG911 needs