It Starts at Home: Why local GIS, mapping and data are the building blocks for location success! RICHARD KELLY 911 DATAMASTER

Transcription

1 It Starts at Home: Why local GIS, mapping and data are the building blocks for location success! RICHARD KELLY 911 DATAMASTER

2 NG9-1-1 Concepts to Keep in PIDF-LO (Presence Information Data Format-Location Object) - Replaces ALI with more location information that needs to match GIS: Civic Address has more detailed location elements than ALI Geodetic Location refers to coordinates for latitude and longitude (X / Y) LVF validates all civic locations in data prior to inclusion in a LIS, ALI or LDB. ECRF provides real time routing instructions for all call types: When presented with a valid location, will deliver the next hop in call delivery Requires data which facilitates that next hop, such as a URI The same data should be used for both LVF and ECRF Mind for Today

3 GIS Data Needs for NG9-1-1

4 NENA GIS Data Related CLDXF Civic Local Data Exchange Format (NENA-STA ) i3 Architecture STA-010 (previously NENA ) PC Review Development of Site Structure Address Point GIS Data for (NENA-INF ) Released Last Week! Provisioning and Maintenance of GIS data to ECRF / LVF Workgroup (STA) Completed w Adoption Next NG9-1-1 Data Management (NENA-REQ ) ) Completed w Adoption Next NG9-1-1 GIS Data Model (STA) Public Review Soon Documents

5 STA-010 (formerly ) NENA Detailed Functional and Interface Standards for the NENA i3 Solution A selection of GIS related points of interest: Appendix B schema vs. NG9-1-1 GIS Data Model schema Near real time rather than Real time requirements Replication distribution authorization: SI or ECRF control? Map Database Service Polygon gap determination thresholds Data beyond jurisdiction marked with Informative attribute for ECRF/LVF to ignore? ECRF\LVF ignore value for data

6 NG9-1-1 Call Routing Location & Service Location & PSAP PIDF-LO + Service URN: urn:service:sos Service URN (Uniform Resource Name) Is the IP reference to the type of service. Location + Service URN LVF / ECRF ESINet Location + PSAP URI PIDF-LO + PSAP URI: sos@psap.austin.tx.us PSAP URI (Uniform Resource Identifier) Is the identifier of the PSAP to connect the call to. ESRP PRF Location Validation Query PIDF_LO Caller Dials LIS PSAP

7 Example 1: Geodetic location (X, Y coordinates) is compared to the Polygon layer representing PSAPs to route to. (X,Y) (Civic) Example 2: Civic location is geocoded to RCL layer then compared to the Polygon layer representing PSAPs to route to. PSAP A PSAP B

8 NG9-1-1 GIS Data Model Provides GIS database structure for NG9-1-1 NG9-1-1 GIS Data Model database schemas for: o o o o o o o Road Centerlines (required) Emergency Service Boundaries such as PSAP and Responder (required) Street Name Alias Table State, County, Municipal Division Boundaries Site / Structure Address Points Cell Sites and Sectors Others Authoritative designation (boundary vs attribute) Effective and Expiration dates Landmarks included

9 Tabular Data and the ECRF It doesn t have to all be only GIS data all the time (Data it Data is Data). Tabular searching = Faster searching. Top issues we see in traditional databases (MSAG): o o o o o o Concatenated address elements in street name field MSAG communities that only make sense to the LEC Buffered ranges Non-standard (or inconsistent) taxonomy (i.e. sometimes it is US 71, then US-71, then Hwy- 71, etc.) Implied data. Example, in some telco MSAG s the street type ST it is omitted Non-standard abbreviations (BV instead of BLVD)

10 The Spatial Interface SI Spatial Interface (SI) - Provides for layer replication between an authoritative copy of GIS data and functional elements (ex. LVF / ECRF). ATOM protocol replication feed identified within OGC r2 uses WFS for Insert, Update and Delete actions. WGS84 Transformation Some design considerations: o What serves as the centralized data repository for multiple entities? o Where is the best location to perform edge matching between jurisdictions? o How to support different local government access needs and data formats?

11 NG9-1-1 SI Example LVF / ECRF Forest Guide The Goal: Get Spatial Data to where it needs to go, in the correct format in needs to be in!

12 GIS Data Quality Concerns

13 Where to Start Condition of many GIS data sources today GIS data does not meet the quality and content standards outlined by NENA. In some cases data is degrading (with and without sites knowing it). Many sites don t know what problems their data has because it s only been used for one purpose. Opinions on GIS data status Our data is good because so-and-so created it. Objective assessment over subjective is a must! No substitute for comprehensive analysis. GIS staffing & training limitations Little to no time to review and update while still performing regular duties. Needed expertise is dropping with turnover. Too little or too much complexity in both procedures and software.

14 Priority Checks for Routability QC data both internally and externally. Fix the issues below first before comparing to ALI / MSAG. GIS data matching ALI/MSAG does not ensure routability! Polygons (Initial Effort) 1. Empty (Null) Geometry 2. Geometry Overlaps PSAP Responders 3. Geometry Gaps PSAP Responders 4. Missing Required Field Values* Road Centerlines (Secondary Effort) 5. Empty (Null) Geometry 6. Address Range Overlaps 7. Address Ranges Zero* 8. Not in a Polygon PSAP Responders 9. RCL to Polygon Attribute Mismatch* 10. No USPS Standard Match

15 Polygons

16 Polygon Alignment with Other Jurisdictions Inaccurate boundary lines may cause routing issues. Polygon boundaries should be a #1 priority for review / updating.

17 Polygons with Simplified or Changing Boundaries

18 Valid or Unnecessary? Zero gaps/overlaps on this one. 2.5 miles away from main polygon. Valid! Site has phone service through a different phone company necessitating it its own ESN.

19 Should RCLs Split This Polygon?

20 Road Centerlines (RCLs)

21 Road Centerline Splitting Affects Attributes PSAP Boundaries PSAP A X PSAP B X Road Intersections County Lines X City Limits X

22 Valid or Unnecessary? Zero gaps or overlaps were detected for this one. Potential problems can t always be found by software!

23 RCL Address Ranges and NG9-1-1 Where should 1103 geocode? Longhorn Rd ESN 333 ESN Buffered Addressing (continuous, exhaustive, hypothetical, padded, or theoretical) vs. Actual Addressing Longhorn Rd ESN 333 ESN

24 RCL Gaps Over time, RCLs may experience drop out (loss or corruption) for a variety of reasons. Nothing can substitute for the occasional visual QC.

25 Even if You Can t See it You Still Need to Fix It! Overlapping feature geometry is often invisible. And this happens with polygons as well!

26 Where should geometry be adjusted and/or attribution? How Far is Too Far?

27 Automated GIS Cleanup Induced Geometry Issues Some automated cleanup tools can cause more problems than they solve. For example, when using tools such as Esri s Snap Geoprocessing to automate editing, users must keep in mind what is set for the distance tolerance. Example T intersection

28 Common GIS Attribution Issues How are empty attributes represented? Looks good, right? PreDirectional Street Name Street Suffix Walnut Blvd Walnut Blvd Walnut Blvd Walnut Blvd Upon closer inspection, not so good! PreDirectional Street Name Street Suffix <NULL> Walnut Blvd Walnut Blvd Walnut Blvd Walnut Blvd

29 Street Names vs. Aliases Unique street names in the Alias field while Name field entries are not unique. The result is duplicate overlapping RCL segment address ranges.

30 Automated GIS Cleanup Induced Attribution Issues Common attribution mistakes with automated attribute processing: Automated cleanup of attribute data can lead to problems if not closely monitored and verified. Software settings can not replace local knowledge and decision making.

31 Synchronizing GIS with ALI/MSAG NENA Information Document for Synchronizing Geographic Information System databases with MSAG & ALI (pg.8 NENA ): the synchronization process will never yield a 100 percent match rate. It is recommended that a minimum match rate of 98% be set prior to using the GIS data should be part of an ongoing and continuous process to ensure that the databases remain current and synchronized. For GIS RCLs in this process, Actual address ranges should be used. Standardization and quality control processing must take place on the GIS street centerline data and the MSAG data prior to comparing the two data sets GIS RCLs should contain all valid addressing information present in the MSAG. Attribute fields should be fully parsed out per the NG9-1-1 GIS Data Model.

32 Synchronizing GIS with ALI/MSAG Standardization of the GIS road centerline data and the MSAG data should incorporate the following (pg.9 of NENA ): - N, S, E, W, NE, NW, SE, or SW as the only directionals used. - Directionals abbreviated when not part of the actual street name. - Punctuation should be avoided and special characters removed (ex. dashes). - Use only whole numbers in the house number fields. - Use complete spelling of the legal street name as assigned. - Spell out the complete MSAG and Postal Community name. - Standardize street name components according USPS Publication No. 28. Attribute fields should be fully parsed out per the NG9-1-1 GIS Data Model.

33 GIS Standardization Example Required step in following NENA Information Document for Synchronizing Geographic Information System databases with MSAG & ALI (NENA ). Before After Prefix Street Post Prefix Street Post Street Name Street Name Directional Suffix Directional Directional Suffix Directional North Elm St N Elm St N Grand W Parkway N Grand West Pkwy Barton Trail Barton Trl Cana Road Cana Rd Stockyard's PKY Stockyards Pkwy Mary's Place S S Marys Pl S Market Plaza Market Plz M.L.K. BV M L K Blvd W 9 W 9th Av J Avenue JJ St Albans Ln Saint Albans Ln M. D. Anderson Blvd M D Anderson Blvd E R. Jones Road E R Jones Rd

34 Legacy Addressing How do you deal with inconsistent AP to RCL addressing? In this case a small segment with a completely different address range to facilitate an out of sync addressing assignment. 1947

35 ESNs Used During Transition Are Still Part of the Equation ESN Boundaries shown in white for: Now look at the RCL ESN attributes noted on each RCL label (760 for all three). 760

36 To Driveway or Not Used if addressed structure is not visible or is more than 500 feet from road. Many unnamed roads/driveways require extensive line work. 3 or more addressed structures, should be considered for naming.

37 Annexations Change Boundaries Frequently

38 Site Structure Address Points (APs)

39 NENA Information Document for Development of Site/Structure Address Point GIS Data for Guide for placement of address points in GIS. (NENA-INF ) Site / Structure Address Point usage in public safety applications NG9-1-1 Validation NG9-1-1 Call Routing Map Display Computer Aided Dispatch (CAD) Vehicle Routing Emergency Notification Sections include: Address Points vs. Access Points Placement methodologies based on: Parcels, Property Access, Structures, Sites, Geocoding Address Point Placement for Subaddresses Best Practices Data Quality Considerations Metadata References

40 105 PSAP A PSAP B

41 NG9-1-1 Data Model Example Site / Structure Address Point (partial list) Site/Structure Address Field M/C/O Data Example Source of Data M Hulk County Date Updated M 12/01/2012 Effective Date O 01/01/2013 Expiration Date O 12/31/2015 Site Unique ID M 05673@hulk911.tx.us Country M US State M Texas County M Hulk Additional Code C Additional Data URI C Incorporated Municipality M West Lake Hollow Unincorporated Community O Neighborhood Community O Address Number Prefix C Address Number C 105 Address Number Suffix C S Street Name Pre Modifier C Old Street Name Pre Directional C N Street Name Pre Type C Street Name Pre Type Separator C Street Name C Franklin Street Name Post Type C St Street Name Post Directional C S Street Name Post Modifier O Bypass

42 NG9-1-1 Data Model Example Site / Structure Address Point (partial list) Site/Structure Address Field M/C/O Data Example ESN C 105 MSAG Community C Hulk Postal Community Name C West Lake Hollow Postal Code C ZIP Plus 4 O Building O A Floor O 2 Unit O 7 Room O 701 Seat O 2 Additional Location Information O On drive off main road Landmark Name Part O Complete Landmark Name O Milepost C Place Type O Business Placement Method O Entrance Longitude O Latitude O Elevation O

43 The Need for Unique IDs A globally unique ID for all GIS features is required in the NENA NG9-1-1 GIS Data Model (proposed name of NUGID - NENA Universally Global ID) to facilitate but not be limited to: o Importation in to a centralized database o Data exchange o Feature identification A globally unique ID can be generated by taking local Unique ID numbers and concatenating them with the providers domain. o Example: = @MYCOUNTY.TX.US Who should be logging/tracking domains? Esri Object IDs or Feature IDs may only be unique to a single table whereas globally unique IDs for NG must be unique across ALL data, from everywhere. Problems occur today in live systems, when IDs are not universally unique (even multiple GUIDs).

44 What s Next?

45 Wireless Location Now NENA E9-1-1 Wireless Maintenance Call Routing & Testing Validation Standard (NENA ) Phase I location accuracy: Local jurisdictions and carriers working together on routing (tower/sector) Phase II location accuracy: Network solution = Handset solution = 67% within 150 meters 90% within 300 meters 67% within 50 meters 90% within 150 meters Latitude & Longitude estimate provided along with confidence and uncertainty, with data accuracy left to service providers (proprietary). Calls can arrive without Phase II and with less accuracy than in earlier years (more wireless indoors?).

46 New Location Accuracy Requirements Coming February 23rd, 2015 FCC released FCC15-9 detailing new wireless and E911 location accuracy requirements (applicable to PSAPs) covering: o o o o o o Outdoor location accuracy Indoor location accuracy Vertical accuracy Defines Dispatchable Location Timeline for implementation National Emergency Address Database (NEAD) PSAPs have to be ready to accept the data and CPE must be capable of supporting new data fields.

47 Defined in FCC15-9 (pg16 of 116) as: What is a Dispatchable Location? the civic address of the calling party plus additional information such as floor, suite, apartment or similar information that may be needed to adequately identify the location of the calling party. FCC15-9 notes that while all dispatchable addresses are necessarily civic addresses, not all civic addresses are dispatchable, e.g., P.O. Boxes, diplomatic or armed forces pouch addresses, etc. Wireless GIS layers will be needed for and will likely require assignment, by the MSAG/GIS Coordinator, of a dispatchable location for every cell tower and sector, as received from a wireless service provider in a call routing spreadsheet. GIS will need the granularity needed to support this (i.e. subaddressing)

48 Timeline of Requirements Year 2, 40% of wireless calls must be accurate to within 50 meters for both outdoor and indoor wireless call locations. Year 3, this requirement goes up to 50% and adds uncompensated barometric pressure determination of elevation. Year 5, this requirement goes up to 70% of wireless calls. Year 6, this requirement goes up to 80% of wireless calls, with movement in to 25% of calls having Dispatchable Locations (top 25 areas) and/or Z value. Year 8, 80% of wireless calls must have an associated dispatchable location (top 50 areas) and/or Z value.

49 Vertical or Z Values in NG9-1-1 Representing elevation / height Already included in both the NG9-1-1 GIS Data Model and the Provisioning and Maintenance of GIS data to ECRF / LVF standards Measuring elevation in feet / meters, above ground / sea level, floors, or barometric pressure How can Z value be used most effectively to convey location to users in a display? Developing / Maintaining data representing elevation Some organizations already taking steps to develop data with base values

50 NENA NG9-1-1 Data Management Requirements Standards to Requirements document with 17 discrepancy and 7 performance reports. Several relate directly to GIS data: o o o o o o SI Operator to the Authority on provisioning GIS data ECRF / LVF Operator to SI Operator on GIS data provisioning ECRF / LVF Operator to DR Subscribers on GIS gaps and overlaps PSAP / Entity to Authority on misroute to their PSAP/Entity [where GIS related] PSAP to the GIS Provider when issues found in map display Forest Guide Operator to Contributing ECRF Node Operator on provisioning coverage data Discrepancy reporting requirements are integrated in to STA-010. A new Data Operations Management standard may be created to cover how discrepancies should be processed / worked

51 Final Thoughts Standardizing your GIS data and resolving geometry & attribution issues now, will mitigate problems in the future and improve its use in systems today. This is an unattended system utilizing the best available data for automated decision making. Elevation and improved accuracy of location information will impact GIS needs later. Plan for rapid turn around of GIS data corrections and updating. Watch for NENA document public review times. New NENA workgroup NENA Next Generation GIS Data Compilation and Stewardship You are responsible for NG9-1-1 Data Preparation and Integrity!

52 Thank You R I C H A R D K E L LY V P E N T E R P R I S E G E O S PAT I A L S O L U T I O N S D ATA M A S T E R R I C H A R D D ATA M A S T E R. C O M