WSDOT Upgrading Basemap Data The path to GIS maps, A Modern LRS System, and Local Roads Data

Transcription

1 WSDOT Upgrading Basemap Data The path to GIS maps, A Modern LRS System, and Local Roads Data Shawn Blaesing Thompson Washington State Department of Transportation GIS T T Nashville, TN March 27, 2007

2 Moving Towards Better Data /Maps in GIS WSDOT challenges of modernization and streamlining a transportation GIS. Challenge 1 Enhance our map series in GIS Challenge 2 Disciplining our LRS (Linear Referencing System) Challenge 3 Filling in the missing data, what about local roads? The Future What does it hold? 27 March

3 Why we are having challenges? Reason 1 Cumbersome Basemaps and Data WSDOT base map information was developed by digitizing 7.5 Minute quads into Microstation and is still being maintained in CAD 20 years later. Cartography office is still using CAD because our engineers do. The dual software platform is cumbersome, expensive and confusing. 27 March

4 Why we are having challenges? Reason 2 A Haphazard LRS First GIS Roads Layer An experiment with no rules on points, segments or measures No attributes other than measure, SRID Still being used after more than a decade Will not meet all of the required functionality needs Our Modern LRS is 24K and linked to a mainframe called TRIPS (which measures in the increasing direction only), while represented cartographically as a dual carriageway system. 27 March

5 Why we are having challenges? Reason 2 A Haphazard LRS Need to modernize the 24K that is linked to a mainframe called TRIPS (measures in the increasing direction only), while dual carriageway represented. Too cumbersome to efficiently maintain multiple representations (500K, 24K, GPS, dual and single carriage way) Need formality Rules of point and segment behavior, intersection determination Need to increase functionality of database supporting LRS (Functional Class, Networking, Addressing) 27 March

6 Making the (LRS) Data Do More Shortcomings with the current LRS include: Difficulty relating data to historical road alignments. Inability to attach our database to dualcarriageway in inc/dec directions Inability to accommodate multiple location types (SRMP, ARM, Addresses, Lat/Long.) Inability to perform transformation among location methods. (programming issues) 27 March

7 Why we are having challenges? Reason 3 Need to Incorporate Local Roads with WSDOT Data Investment in the Washington Transportation Framework project Estimated completion 2009 or later. Currently purchasing local roads data from TeleAtlas NA (TANA) Need more functionality that TANA provides with WSDOT data included (Networking, Addressing, the ability to attach Functional Class) 27 March

8 Dealing with the Challenges Challenge 1 Replacing the CAD base maps with GIS versions. Getting data from CAD converted to GIS Safe Software FME Build/maintain higher quality GIS data GIS based Statewide Hwy Map, and County Map Series (from existing 7.5 minute quad series in CAD) PLTS JTX and Map Atlas Pushing GIS data back into CAD 27 March

9 Develop Processes to Move Data to CAD back to GIS and Vise Versa This is a sample process using FME (Safe Software) to move data from GIS Geodatabase to CAD (Microstation). 27 March

10 Using ArcGIS Desktop PLTS Tools Implementation of PLTS JTX Job Tracker Assigning tasks, notifications, identifying workflows Map Atlas Map Series Creation Data Reviewer Manage and Update of GIS Data Layers 27 March

11 JTX Job Tracking Database 27 March

12 Map Atlas Map Management 27 March

13 Challenge 1 Rebuilding Maps and Data Issues being overcome allowing change to occur: Educating production team on new processes and how to use new tools. Designating one FTE to map development and several others for data/map support. Working with CAD community on data conversion processes. 27 March

14 Challenge 1 Rebuilding Maps and Data Potential benefits to change allows us to: Work in one software platform (GIS vs. CAD and GIS). Streamline data stewardship activities. Provide basemaps/ data in digital form through geodatabase feature datasets/layer files and/or a web based map library. Provide required information more easily to FHWA (digital rather than paper.) 27 March

15 Dealing with the Challenges Challenge 2 Ways we are disciplining the current LRS Quarterly Updates Instead of Yearly Development of a Data model and Segmentation Rules Implementation of Data Model and Segmentation Rules Challenges beyond today Dual Carriage Way 27 March

16 Dealing with the Challenges Challenge 2 Benefits to enhancing the current LRS Meet the needs of the WA Transportation Framework. Infuse discipline into the LRS (point/segment functionality.) Build a data model and databases that may carry over into an enterprise wide independent LRS system (more users.) Easier to maintain. 27 March

17 Data Model 27 March

18 Data Model 27 March

19 FME Workbench Process to segment LRS and move to model database 27 March

20 Dealing with the Challenges Challenge 3 Identifying Ways to Implement Local Roads Build and maintain roads in house from CAD data Look at current road data vendor to workout agreement to combine data Wait for WA Transportation Framework completion or, 2008 Census Roads Data 27 March

21 Eliminating the Stopgaps and Workarounds Challenge 3 Benefits to Implementing Local Roads with WSDOT data Reduction in unnecessary software tools being built on various systems Reduction in data deterioration Reduction in number of systems data must pass through Reduction in spending unnecessary time and money sorting it all out Reduction in Hodge Podge of data sets, tools, and accuracy mixing (see next diagram) 27 March

22 A Hodge-Podge Of Systems and Data Geometric Network 27 March

23 Overcoming Challenges Looking Towards the Future Challenge 3 One Option Being Pursued to Implement Local Roads with WSDOT data Working with TeleAtlas Providing a Segmented Version of the WSDOT LRS with measures based on model Build place event capabilities for Functional Class / HPMS / Freight and Goods into a local roads database 27 March

24 The Future What does it hold? A linear referencing system that is decoupled from feature description A system that efficiently provides functions: Establish de facto, accurate measures Event location stability and temporal persistence Location methods transformations (address to SRMP Dynamic segmentation Visual representation Metadata upkeep (layer and feature) 27 March

25 The Future What does it hold? A SQL based, modular system, readily accessible to other systems (CAD, Datamarts) A system with a linear datum, in order to relate measures to the real world A system capable of higher levels of accuracy (GPS friendly) A system that accommodates a dual carriageway A system that accommodates coincident routes A friendly, easy to use system 27 March

26 Data WSDOT CPMS WSDOT Data Warehouse CAPS TRAINS Labor Collection Cons. Inv. PDIS CLAS CAFM TRIPS CCIS EBASE Nightly Extraction, Transformation & Load (ETL) Data are reformatted for querying. Construction+G Proj. Schedules Labor Inventory Traffic Collision+G Roadway Facilities+G Numerous transactional databases various systems and technologies. Databases optimized for analysis & reporting compatible & integrated technologies. +G = includes GIS features. More to come. 27 March

27 In the Future We Must Accommodate: WA Transportation Framework Accommodate the dual carriageway and coincident routes (Need for increasing accuracy) Place Events (on Routes) WSDOT Business (dual and single carriageway) Functional Class (single carriageway) Freight and Goods (single carriageway) Collision/Traffic (dual carriageway) Handle multiple Cartographic Displays 27 March

28 Conclusions WSDOT is working within the GIS system to streamline our business processes. Enhance our map series in GIS Disciplining our LRS (Linear Referencing System) Filling in the missing data, what about local roads and enabling systems to become linked to GIS? 27 March

29 Thank you Any Questions? Shawn Blaesing Thompson WA Department of Transportation (360) March