Merging and DOT Data

Transcription

1 Merging and DOT Data Presented By: Ken Nelson - GIO - State of Kansas Patrick Melancon - Product Manager - GeoComm Date: Wednesday

2 Primary NG911 project goals Deploy an IP-based hosted call handling solution available to all Kansas PSAP s. Partner with local jurisdictions to develop the statewide, authoritative geographic data adhering to state and emerging national NG911 standards. Align telephone provider databases with geographic data and plan for migration to geospatial call routing. Transition PSAP s on the hosted call handling solution to a nationwide ESInet solution. Communicate, train, and support project partners throughout all phases of the program.

3 GIS Program Opportunities Coordination & collaboration opportunity across all levels of government and the private sector Develop and maintain statewide authoritative datasets that have been desired for many years: Road centerlines Address points High-resolution imagery Raise the profile of GIS among state and local government, and among our state legislature

4 GIS Data Requirements Statewide covering every county and PSAP Consistent common set of data layers, data model and implementation procedures Current regularly maintained Authoritative accurate and reliable Standardized adheres to applicable Kansas & national NG911 GIS standards, data models and implementation guidelines

5 Kansas NG911 Gap Analysis & Data Enhancement General process: GIS Data Gap Analysis (complete) GIS Data Enhancement (complete) GIS Data QA Audit (complete) Local GIS Data Maintenance (ongoing) Data Aggregation & Conflation (Iteration 1 complete) KDOT (GeoComm) Incorporate local geometry, conflate state (KDOT) attributes Support multiple state and federal requirements

6 GIS Data Maintenance Status 100% compliance with GIS Governance Policy 105 counties phone home via the Program Portal with 90% providing data updates each quarter Compliance hasn t waivered even with evolving data standard & requirements

7 GIS Standards & Policies Kansas NG911 GIS Data Model Provides a framework for consistent statewide data Public comment period with each data model update Adheres to draft NENA GIS specifications Used Tennessee data model and documentation as our starting point extremely well done and saved us a great deal of time Kansas NG911 GIS Governance Policy Kansas NG911 GIS Change Management Policy Coordination, education, & outreach: GIS Data Steward & Data Maintainer training classes offered across the state NG911 GIS User Group Airbus Vesta User Group

8 Kansas NG911 Program Portal NG911 Program Portal has become the centralized location for all content, documents, and data: Change Order Request GIS Data Submission GIS Data Request PSAP Security Audit PSAP Expenditure Reporting PSAP Outage Notification Telephone Service Provider (TSP) monthly reporting User profile & management GIS Data Submission Module GIS Data Submission Detail

9 Kansas NG911 Toolbox Provides a standardized set of tools to ensure data quality, consistency, and adherence with Kansas standard Approach: Deployed as an ArcGIS Desktop or ArcPro Toolbox Public domain tool kept in sync with the Kansas NG911 GIS data model and is available to all Data Maintainers (GitHub) Data Maintainers run tools locally prior to submission, open book test Same validations are run upon submission to the portal Tool categories: Adjustment Tools Comparison Tools Conversion Tools Enhancement Tools MSAG Tools Submission Tools Validation Tools

10 Generalized data flow AT&T host/airbus DataSync Local Maintenance DK MP SG AN BU CL NG911 Program Portal Data submission Data archival Data QA testing Data aggregation Data conversion DK SG Hosted PSAP s Vesta Locate MP ME WI KE BT AN C L SN RN JW RP LY HG RS Kansas Department of Transportation Aggregation Conflation (LRS) Support state & federal programs West Safety Services Transitional data services GeoMSAG creation SI/ECRF

11 KDOT Partnership We ve been working with KDOT for years on incorporating local geometry into their LRS database, but with little success The state was divided into the haves and have nots, but many of the haves had old data KDOT had a crew of drivers that mapped local roads, but they were retiring and not being replaced The NG911 program came along just a right time Clearly defined need Timeline Funding Easy to support

12 KDOT requirements incremental approach Grab the low(er) hanging fruit Create a process to develop & maintain statewide, standardized, authoritative data Watch out for scope creep Focus on NG911 project goals first Realize the low hanging fruit is still a big deal Expand requirements as needed Use, maintain, and improve Initial work set the stage for a long-term partnership Data provided to KDOT for conflation and integration into LRS KDOT will benefit from continual maintenance and refinement of local data, and has a voice in the conversation

13 When I say we Kansas 911 Coordinating Council: 911 Administrator 911 Technical Support Specialist Security Committee Technical Committee GIS Committee Training Committee Kansas Counties (105) GIS service providers: ATCi GeoComm Kimball Mapping R&S Digital Imagery: Surdex Hexagon Kansas Data Access & Support Center Service providers: AT&T ESINet & Data Centers Airbus DS Communications 911 Call Handling hardware & software platform West Safety Solutions Randall White Consulting program management

14 GeoComm s Workflow

15 Project Goals & Objectives The aggregation of NG9-1-1 GIS data into a statewide, seamless road network to support the following Federal Highway Reporting & Funding Highway Safety Improvement Program (HSIP) All Roads Network Linear-Referenced Data (ARNOLD) Highway Performance Monitoring System (HPMS) Compliance with Kansas One Map

16 Data Aggregation Data Aggregation Step 1 Region by Region data aggregation of Local Data Stitch points and lines generated between Counties Access was provided to KS imagery to ensure consistency Data Aggregation Step 2 Region to Region data aggregation of Local Data This will be integrated into Step 1 to reduce going back to local data provider with updated stitch points if boundaries are complete used stitch points from step 1 on step 2 when overlap happened

17 Custom DMS Conflation Methodology Nodes Comparison A Beginning of line End of line Azimuth Comparison Reversed directionality Consistent directionality Difference in directionality Length Comparison Intersection Comparison B Layer X vs Layer Y Layer Y vs Layer X Naming Comparison Levenshtein Methodology

18 Comparison Criteria Weighted Scoring System (flexible).025 Beginning Intersection Valence Compare.025 Ending intersection Compare.500 Azimuth Compare.050 Length Compare.200 Beginning/End Intersection Spatial Compare.200 Naming Compare

19 Conflation can be Messy Conflation Results Features from Layer X not in Layer Y Features from Layer Y not in Layer X

20 Review-Review-Review Review areas identified with unique characteristics Make any needed match adjustments Review all unmatched records Records unique to a dataset by location 1:M, 1:1, M:1 matches Records with conflicting geometric representation / poor spatial accuracy

21 Deliverables Statewide GIS Dataset containing the following layers: Street Centerlines State Highway Intersection Points Address Points Authoritative Boundaries Emergency Service Boundaries Emergency Services Zones Municipal Boundaries Stitch Points

22 Deliverables Regular status reports and conference calls Discrepancy geodatabase and discrepancy reports Report of KDOT roads not present in local data FGDC-complaint metadata for each statewide GIS data layer developed

23 Contact info Kenneth A. Nelson Kansas Geographic Information Officer State of Kansas Data Access & Support Center (DASC) Kansas Geological Survey (KGS) University of Kansas 1930 Constant Avenue Lawrence, KS (voice) (fax) Patrick Melancon Senior Product Manager Geo-Comm, Inc 601 West Saint Germain Street Saint Cloud, MN (voice) (cell)

24 Mapping the Future of Discussion