GRID. Geospatial Roadway Inventory Database. Michael Chamberlain, TxDOT. TPP Planning Conference Houston, TX

Transcription

1 GRID Geospatial Roadway Inventory Database Michael Chamberlain, TxDOT TPP Planning Conference Houston, TX

2 Topics History (pre GRID) 3-6 GIS Resources 7-8 The Project 9-11 Assets and the LRS GRID Design Roadway Updates Lessons Learned Next Steps 29 2

3 Pre GRID Texas Reference Marker System (TRM) Development began in 1988 and went live in 1995 Only On System Highways Reference Marker LRM (did not incorporate control section mile points or distance from origin LRMs) Non-spatial Limited business rules and data validation Off System maintained in a different system (County Roads and City Streets) Data maintainers worked in a temporary space and IT analysts wrote custom programs to submit changes to the system 3

4 Pre GRID 4

5 Pre GRID Network issues All similarly named route segments were parallel Frontage road lengths matched roadbed lengths Inner loop and outer loop segment lengths were the same Data errors cascaded from the error point to the end of the route (sometimes hundreds of miles) 5

6 Pre GRID Route Directions Increasing Length Error In Texas almost all routes run North to South and West to East Interstates run South to North and West to East Increasing Length Error 6

7 GIS Resources Data in the GIS system Roadbed linework (313K miles) One model for on system and off system (including local streets) Event tables routed by DFO Control sections Concurrencies Bridges Off-system inventory data Basemap layers 7

8 GIS Resources GIS Editing Matrix On System Digitize Feature Feature Attributes Calculate Measures FC Linework Departmental Map Control Section Map County Mapbook Statewide Planning Map (z0-z6) State Railroad Map RTE Concurrent RTE CG RTE Control Section Add Road x x x x x x x x x x x x x Remove Road x x x x x x x x x x x Modify Road x x x x x x x x x x Realign Road x x x x x x x x x x x x Change Name x x x x x x x x x x x Change Route Class x x x x x x x x x x x Grade Separated Connector x x x x x x Off System Digitize Feature Feature Attributes Calculate Measures FC Linework Departmental Map Control Section Map County Mapbook Statewide Planning Map (z0-z6) State Railroad Map RTE Concurrent RTE CG RTE Control Section Add Road x x x x x x x Remove Road x x x x x Modify Road x x x x x x Realign Road x x x x x x Change Name x x x x Change Route Class x x x x x x x x x City Limits Digitize Feature Feature Attributes Calculate Measures FC Linework Departmental Map Control Section Map County Mapbook Statewide Planning Map (z0-z6) Add City x x x x x x Remove City x x x x x Modify City x x x Change Name x x x x x Railroad Linework Digitize Feature Feature Attributes Calculate Measures FC Linework Departmental Map Control Section Map County Mapbook Statewide Planning Map (z0-z6) Add Rail line x x x x x Remove Rail line x x x x Modify Rail line x x x x Realign Rail line x x x x Change Name x x x x Change Rail Class x x x x Railroad Crossings Digitize Feature Feature Attributes Calculate Measures FC Linework Departmental Map Control Section Map County Mapbook Statewide Planning Map (z0-z6) Add Crossing x x Remove Crossing x x Modify Crossing x x Change Name x x Change Class x x State Railroad Map State Railroad Map State Railroad Map RTE Concurrent RTE Concurrent RTE Concurrent RTE CG RTE CG RTE CG RTE Control Section RTE Control Section RTE Control Section Bridge Bridge Bridge Bridge Bridge RTE Subfiles Subfiles Subfiles Subfiles Subfiles Mileage Tracking Mileage Tracking Mileage Tracking Mileage Tracking Mileage Tracking 8

9 The Project GRID Concepts GIS based Multiple LRM s (and remove old systems) DFO, Markers, Control Section Mile Points, Lat, Long Coordinates Latitude and Longitude Coordinates determine event locations Normalized data model One table per attribute Business rules engine Simplified workflow No secondary team of IT folks to write the data back to the DB 9

10 The Project Timeline Project began in August 2009 Reviewed multiple proposals including Roads and Highways Selected a custom solution (Geospatial Roadway Inventory Database) 2010 Project design and system requirements 2011 Project redesign and system requirements 2012 System requirements 2013 Initial components and data migration 2014 Project consolidation, data migration, and testing 2015 Project went live September 1 st 10

11 Users of GRID Highway Performance Monitoring System (HPMS) Pavement Management Information System (PMIS) Maintenance Division Bridge Division Right of Way Division Crash Records Information System (CRIS) Traffic Operations TxDOT Administration and Planners UTP Project Scoring Top 100 Most Congested Ad hoc requestors (public, legislature and government entities) 11

12 GRID Assets 12

13 GRID Assets Assets are attributes which describe the characteristics of a route Point Assets: Assets that have a singular location (Point X, Point Y) Culverts Cattle Guard Litter Barrel Line Assets: Assets that have a begin point and an end point (From X,Y To X,Y) Speed Limits Number of Through Lanes Roadbed Surface 13

14 GRID Assets and the Linear Referencing System (LRS) Characteristics of an LRS Linear feature with unique identifier and built-in measurement system Can have attributes applied to it without splitting the line Contains x, y, and m values 14

15 Visualizing GRID Asset 15

16 GRID Linear Referencing Methods (LRMs) Reference Markers On-system asset management DFOs GIS Roadway linework Off-system asset management Control Section Milepoints Construction Project Management system CSM CSM CSM CSM 24 DFO 100 RM = DFO = CSM = 15.7 DFO

17 GRID Design GRID System Web app Hosted in the Amazon cloud Oracle Spatial DB ArcGIS Server mapping component Flex user interface 17

18 GRID Design GRID Administration 18

19 GRID Design GRID Maintenance Application 19

20 GRID Design GRID Map 20

21 GRID Design GRID Asset Basic table model for 120+ assets Asset Type Begin Lat Begin Long End Lat End Long Shape 21

22 GRID Design GRID Asset and LRM options 22

23 Roadway Updates Extract, Transform, and Load (ETL) Interface between GIS and GRID Bulk load operations Update base map Update roadbed line work and route definitions Add Replace Retire 23

24 Roadway Updates Replace Assets within 53 tolerance are snapped to the new alignment Realignment process applied to 120+ assets 24

25 Lessons Learned Data Migration What people think it looks like What it really looks like 25

26 Lessons Learned Data Migration Stats 2 GIS Analysts 116 total scripts 4,000 hours 513 gallons of coffee 65 pounds of candy 340 data tables 8.2 million records migrated 8,675, s and 90 s pop culture references 26

27 Lessons Learned User Acceptance Testing 19 testers Over 200 requirements tested Over 500 validation rules tested 27

28 Lessons Learned High Level More involvement in vendor day-to-day decisions and development meetings Establish this pattern early and stick to it Staff or IT should review vendor scripts, code, and processes Requirements gathering process should include prototypes or labs Get the entire team involved early in the process Delays are inevitable, but you need to have a clear escalation path for issues Technical Concept of working within an assigned job has limitations Developers should work as staff member for a few weeks to completely understand the concepts and role of the data maintainers Data Migration required vast resources 28

29 Next Steps Continued Improvement and Sharing Create an HTML 5 based UI (replaces the FLEX viewer) Publish GRID data to the enterprise data warehouse Refine the business rules Finish the data extraction component Help other business units utilize the new data structure in their systems MPPM interface for planned projects 29

30 QUESTIONS? Michael Chamberlain Director TPP- Data Management Texas Department of Transportation (512) TPP Planning Conference Houston, TX