1 / 15

NENA WG Update & Preparing GIS Data for NG9-1-1

NENA WG Update & Preparing GIS Data for NG9-1-1. Concerns Over NG9-1-1 GIS Data Development. The Changing Role of GIS Data In the past, good GIS data was a “supplement” rather than a requirement for 9-1-1 Authorities . GIS data is a baseline requirement for NG9-1-1 .

giulia
Download Presentation

NENA WG Update & Preparing GIS Data for NG9-1-1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NENA WG Update & Preparing GIS Data for NG9-1-1

  2. Concerns Over NG9-1-1 GIS Data Development The Changing Role of GIS Data • In the past, good GIS data was a “supplement” rather than a requirement for 9-1-1 Authorities. • GIS data is a baseline requirementfor NG9-1-1. • ‘Attended’ (past) vs. ‘Automated’ (future) GIS data usage roll. • Representation of Reality! • Incorrect / conflicting GIS data could result in improper or even default call routing. What We’re Getting In To • Developing / Maintaining NG 9-1-1 ready GIS data is complex (Format, Projection, etc.). • New data requirements and attributes to support (NENA Data Model: RCL-41, AP-36, ESZ/PSAP-12) • Many organizations do not have GIS data meeting NENA quality and content standards. • Thorough QA / QC checks must be performed on all data before it goes ‘live’. • GIS data changes will need to be tracked and accounted for, as ALI / MSAG changes are today. • Upcoming discrepancy reporting from LIS / LVF / ECRF etc. will require timely, local response. This document is intended only for the use of 911 Datamaster, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. 04/29/13

  3. NENA GIS Related Workgroups • Site Structure Address Point (SSAP) Workgroup • Richard Kelly • Cheryl Benjamin • Data Management Workgroup • Kathy Liljequist • Ira Pyles • GIS Data Model Workgroup • Marc Berryman This document is intended only for the use of 911 Datamaster, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. 04/29/13

  4. Site / Structure Address Point (SSAP) Workgroup • Following NDC 2012 NENA formed a workgroup on AP creation. • ‘Informational Document’ and initial scope developed July 2012. • Workgroup formed August 2012 with goal of creating a NENA guide for the development of site/structure address points in a GIS. • Concerns to be addressed in document or guide: • What makes an address valid or invalid? • If / when a driveway access point is needed? • If / when should more than one driveway access point be represented? • If / when should more than one structure access point be represented? • Jurisdictional boundary lines intersecting a parcel, site, or structure. • Using a hierarchical addressing system. • Spatial accuracy recommendations for placement. This document is intended only for the use of 911 Datamaster, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. 04/29/13

  5. Five Major Sections • Purpose & Scope • Acronyms/Abbreviations • Site/Structure Address Point Usage in Public Safety Applications • Address Points vs. Access Points • Address Point Placement Guidelines - Methodology: • Placement of an Address Point Based on a Parcel • Placement of an Address Point Based on Property Access • Placement of an Address Point Based on a Structure • Placement of an Address Point Based on a Group of Structures • Placement of an Address Point Based on an Exterior Structure Entry • Placement of an Address Point Based on Interior Locations Within a Structure • Geocoding Addresses off of Road Centerlines • 3.3 Accuracy This document is intended only for the use of 911 Datamaster, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. 04/29/13

  6. Standard for NG9-1-1 Data Management WG • Reports are broken down into two categories: • DISCREPANCY REPORTS – 17 • PERFORMANCE REPORTS – 7 • Reports related directly to GIS data: • “Spatial Information Function (SIF) Operator to the 9-1-1 Authority on provisioning GIS data.” • “Emergency Call Routing Function/ Location Validation Function/ (ECRF/LVF) Operator to SIF Operator on GIS data provisioning” • “ECRF/LVF Operator to Subscribers on GIS Geographic Information Systems (GIS) gaps and overlaps” • “PSAP /Entity to 9-1-1 Authority on misroute to their PSAP/Entity” [where GIS related] • “PSAP to the GIS Provider when issues found within GIS data in the map display” • “Provisioning Performance Report related to GIS Data” This document is intended only for the use of 911 Datamaster, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. 04/29/13

  7. Typical Report Contents • Title • Description • Table • Where is the report created • Who is responsible to produce the report • What is being reported • Turn around time to produce report • Who should receive the report • Responsible entity for resolution • Turn around time for resolve or refer • Minimum Content Requirements This document is intended only for the use of 911 Datamaster, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. 04/29/13

  8. NG9-1-1 GIS Data Model Workgroup • The GIS Data Model: • Supports NENA NG9-1-1 systems, databases, call routing, call handling, and related processes. • Designed to support PIDF-LO as conveyance method. • Both the LVF and the ECRF will use this new NG9-1-1 GIS database model to function properly. • Minimum GIS layers needed for NG 9-1-1 (of 13): • Road Centerlines • PSAP and Emergency Services Boundaries • Wireless Points / Polygons (under consideration) • Site / Structure Address Points (recommended) • GIS Data Model Projection = WGS 84 / Lat Long / Geographic (‘Z’ value?). This document is intended only for the use of 911 Datamaster, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. 04/29/13

  9. Site/Structure Address FieldPIDF-lo Element LabelData Example State A1 TX County A2 ORANGE Municipality A3 West Orange Municipality Division A4 Neighborhood A5 Turtle Creek Address Number Prefix HNP W Address Number HNO 105 Address Number Suffix HNS S Street Pre-modifier PRM Old Prefix Street Direction PRD N Street Name RD Franklin Street Post-modifier POM Service Street Type Suffix STS St Street Suffix Direction POD S ESN ESN 105 Postal Community Name PCN Orange County Postal Code/ZIP Code PC 75216 Building BLD A Unit UNIT 7 Floor FLR 2 Room ROOM 701 Seat SEAT 2 Landmark LMK Additional Location Information LOC In alley off corner Place Type PLC Business Longitude -86.77791 Latitude 32.20912 Elevation NENA NG9-1-1 GIS Data Model An Example: This document is intended only for the use of 911 Datamaster, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. 04/29/13

  10. NG 9-1-1 GIS Data Development / Management Process • NENA’s GIS Standards: • GIS Data Collection and Maintenance Standards (NENA 02-014) • GIS Database to MSAG & ALI Synchronization Process (NENA 71-501), with NENA goal of 98% match. • UpcomingNG9-1-1 GIS Data Model (NENA 71-003) includes many additional data fields (AP-36, RCL-41, ESZ/PSAP-12) • UpcomingNENA Standard for Next Generation 9-1-1 Data Management includes seventeen (17) discrepancy reports. • GIS Data Placed on-line in ECRF QA / QC Checks • Incoming Discrepancy Reports • (Requires GIS Corrections) GIS Base Data (Development & Maintenance) This document is intended only for the use of 911 Datamaster, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. 04/29/13

  11. Spatial Data Use In NG9-1-1 SIF ‘Validated’ GIS Data ESINet • RCLs • APs • Boundaries Validated GIS Data ‘Validated’ GIS Data Updates to ALI / MSAG LVF / ECRF MSAG & USPS MSAG ESRP PIDF_lo Location Information 9-1-1 Caller PSAP This document is intended only for the use of 911 Datamaster, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. 04/29/13

  12. For NG9-1-1 GIS Data Development Top 10 SpatialStation considerations for 9-1-1 oriented GIS QA / QC tools: • Support GIS related NENA standards (02-014, 71-501, 71-003). • Identify GIS database attribution and topologyproblems (33). • Correlate Road Centerlines to MSAG (NENA goal of 98% match). • Correlate ALI to Address Points. • Cross check between APs, RCLs and Emergency Service Zones (ESZs). • Recommend missing data ‘fill-ins’ and visually cue user to incorrect entries. • Support cross jurisdiction analysis and coordination, including data export. • Provide GIS data metrics compilation and status reporting. • Integrate QA / QC checks and balances when provisioning LVF / ECRF. • Support ArcGIS v10.0, v10.1 and future releases ( ). This document is intended only for the use of 911 Datamaster, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. 04/29/13

  13. This document is intended only for the use of 911 Datamaster, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. 04/29/13

  14. Metrics Reporting As with traditional tabular databases today, GIS data modifications must be trackable and reportable. • Log potential ‘Topological’ and ‘Attribution’ validation check errors. • Provide comparison results between GIS and traditional tabular. • Monitor GIS activity and health over time. • Log user modification activity within GIS data such as inserts, deletes or changes. This document is intended only for the use of 911 Datamaster, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. 04/29/13

  15. Questions Richard Kelly RichardK@911Datamaster.com 512.331.0633

More Related