Roads and Highways Implementation at WVDOT Project Update Emiko Hori Geospatial Transportation Information (GTI) Section Geographic Information System (GIS) Unit
Agenda 1. Development History 2. Roads and Highways Implementation 3. Challenges 4. What s Next 5. Q & As
1. Development History a) Pre Roads and Highways (R&H) b) System Integration c) Project Goal
1. Development History a) Pre Roads and Highways (R&H) One Linear Referencing System (LRS) Was completed in 2008 Countywide Linear Referencing Method (LRM) Had been maintained using ArcGIS Desktop, ArcSDE and MS SQL Server Included only state maintained routes Shapefile/web service is available Issues A Statewide LRS Network Non state maintained routes to be included No system integration available, but other systems can use a snapshot of the LRS Need for accessibility
1. Development History b) System Integration Enterprise Resource Planning (ERP) Government wide projects at the state of West Virginia Implement a Statewide ERP system Facilitate standardization and timely access to information System wvoasis (Our Advanced Solution with Integrated Systems) AgileAssets Asset Management System R&H implementation as solution Transcend Spatial
1. Development History c) Project Goal Needs Multi LRMs support, system integration, improvement of accessibility Goal Develop an enterprise LRS for WVDOT & external users Tabular Databases / Files Example) Bridge, Pavement, Roadway Inventory Log Spatial Databases / Files Example) LRS Network, GIS data Roads and Highways Web Server Service Desktop Service Users Read Only, Edit, Data Access Users Admin, Edit, Data Access, Analysis
2. R&H Implementation a) Project Overview b) System Architecture c) Comprehensive LRS Modeling d) ALRS Supporting Two LRMs e) Route Identifier f) LRS Management g) Tools h) Roadway Characteristics Editor (RCE) i) Workshop j) Testing
2. R&H Implementation a) Project Overview Phase 1 System Design and Data Mapping Aug. 2013 Feb. 2014 Architecture Design Comprehensive LRS Modeling Prototyping Phase 2 Deployment in Test Environment Mar. 2014 Oct. 2014 Version 10.2 to 10.2.2 Desktop Service Web based Service Testing Phase 3 Deployment in Production Environment Improvement & System Integration Current Version 10.3 to 10.3.1 External Data Enhancement Customized Tools Training
2. R&H Implementation b) System Architecture Route Dom Mgr LRM Intersection Mgr R&H Desktop RCE Validation Assistant Road Analyzer ALRS RC Events External Query Visualization & Query Systems Analysis Tools GeoRIL Transaction Environment R&H Geodatabase ALRS RC Events Publication Environment Various GIS Layers Data Layers TBD Various Asset Layers Road Analyzer TM Map Portals Data A Data B Data C Various External Data Sources
2. R&H Implementation c) Comprehensive LRS Modeling Before R&H Implementation One LRS Network Countywide LRM Only statemaintained routes No system integrations After Phase 1 and 2 One ALRS with 2 LRS Networks Countywide LRM Statewide LRM State maintained routes and non state maintained routes RouteID as a route identifier System integrations wvoasis AgileAssets System Road Inventory Log (RIL) Official Roadway Measure Source External data source
West Virginia Department of Transportation Only State Maintained Routes All Public Roads Charleston, WV Huntington, WV
2. R&H Implementation d) ALRS Supporting Two LRMs Complete Roadways Dataset o Dual carriageways o State maintained railroads o State maintained trails All public roads State maintained routes Non statemaintained routes Ramps o Crossovers Countywide LRM/LRS Network Measures are reset at county boundaries for all routes except for Interstates, railroads, and trails whose measures are continuous across the state. Statewide LRM/LRS Network Measures are continuous for all routes across the state.
2. R&H Implementation e) Route Identifier Concatenated route identifier RouteID Extensible Coded Domain Countywide LRS network ex) 20201190017NB County Code = 20 Sign System = 2 Route = 0119 Subroute = 00 Supp. Code = 17 Direction = NB Statewide LRS network ex) 2011900 20NB17 US119 North Bound Ramp In Kanawha County
2. R&H Implementation Cont. Route Identifier Coded Domain County List Sign System 01 Barbour 20 Kanawha 39 Preston 1 Interstate 02 Berkeley 21 Lewis 40 Putnum 2 US 03 Boone 22 Lincoln 41 Raleigh 3 WV 04 Braxton 23 Logan 42 Randolph 4 CO 05 Brooke 24 McDowell 43 Ritchie 5 N/A 06 Cabell 25 Marion 44 Roane 6 State Park and Forest Road 07 Calhoun 26 Marshall 45 Summers 7 FANS 08 Clay 27 Mason 46 Taylor 8 HARP 09 Doddridge 28 Mercer 47 Tucker 9 Other 10 Fayette 29 Mineral 48 Tyler 0 MNS (Municipal Non State) 11 Gilmer 30 Mingo 49 Upshur R Railroad (WV State Rail Authority) 12 Grant 31 Monongalia 50 Wayne T Trail 13 Greenbrier 32 Monroe 51 Webster U USFR (United State Forest Road) 14 Hampshire 33 Morgan 52 Wetzel 15 Hancock 34 Nicholas 53 Wirt 16 Hardy 35 Ohio 54 Wood 17 Harrison 36 Pendleton 55 Wyoming 18 Jackson 37 Pleasants 99 Reserved for Other 19 Jefferson 38 Pocahontas Statewide Continuous features Supplemental Code 00 Not Applicable 01 Alternate 02 Wye 03 Spur 04 North 05 South 06 East 07 West 08 Business 09 North Bound (Business) 10 South Bound (Business) 11 East Bound (Business) 12 West Bound (Business) 13 Truck Route 14 Bypass 15 Loop 16 Toll 17 Ramp 18 Other 19 City Street Non State 20 Road Under Construction 21 Footbridge 22 Historical Bridge 23 Connector 24 New/Proposed 25 Crossover (btw dual geometry) 26 Emergency Crossover 27 Left Turn Lane 28 Right Turn Lane 51 Rail Trail 99 Abandoned
2. R&H Implementation Cont. Route Identifier RouteID Input
2. R&H Implementation f ) LRS Management Catalog window Create, load, add, remove, etc. Configuration Table Of Contents
2. R&H Implementation g) Tools Editing tools Select a network Extend, realign, retire, etc. Edit routes Geoprocessing tools Convert data Detect routes errors
User Interface Desktop Location LRM RouteID Measure Min Max A Statewide 2006000 MLEB00 32.332 0 175.81 Countywide 06200600000EB 26.732 0 26.79 B Statewide 2006000 MLEB00 32.445 0 175.81 Countywide 40200600000EB 0.055 0 9.01
2. R&H Implementation h ) Roadway Characteristics Editor (RCE) Web application Event data edits Redline Accessibility for different tiers of users
User Interface RCE Select network, route, and perform edits on event data Configurable result grid
2. R&H Implementation i) Workshop LRS Editors ArcGIS Desktop service with R&H extension GIS Analysts, cartographers, etc. Experienced in route editing with LRS network Perform route edits RCE Editors ArcGIS Server service (RCE) Traffic specialists, programmers, HPMS coordinators, etc. Some are new to GIS; some have experiences Perform event data edits Classroom session (Transcend Spatial) 20 attendees Each attendee had her/his own laptop to interact
2. R&H Implementation j) Testing LRS Editors route editing on ArcMap Centerline Create new route, realign, reassign, retire, etc. Date filter RCE Editors event editing on RCE How to explore web based GIS map Add a new event, update existing event, merge, etc. (line and point) View Date tool Issues found Configuration Re configure for phase 3 deployment Route related Plan data clean up sessions in phase 3 Software related Communicate with Esri
3. Challenges a) ERP System Integration b) Route Dominance c) Training
3. Challenges a) ERP System Integration
3. Challenges a) Cont. ERP System Integration Communication between two secured systems WVDOT Enterprise System wvoasis Enterprise System R&H VPN LRS Interface VPN AgileAssets System Potential technical issues Testing plan AgileAssets System version 7.1 R&H version 10.3.1
3. Challenges b) Route Dominance Concurrency rule Sign System 1 Interstate 2 US 3 WV 4 CO 5 N/A 6 State Park and Forest Road 7 FANS 8 HARP 9 Other 0 MNS (Municipal Non State) R Railroad (WV State Rail Authority) T Trail U USFR (United State Forest Road) Different sign system The lower sign system value (WV 92 / US 250 ) Same sign system The lower route value (WV 55 / US 219 / US 250) Exception Interstate 64 / Interstate 77 / US 60 Customized tool deployment in phase 3
3. Challenges c) Training Phase 2 Workshop LRS Editors Route edits vs event data RCE Editors Tabular data to spatial data Phase 3 Training Smaller groups More hands on experiences Workflow managers
4. What s Next a) Deployment in Production Environment Workflow Orchestration Customized Tools Electronic Straight Line Diagram Road Analyzer b) Training c) Data Improvement d) External Data Enhancement
Questions? Thank you Emiko Hori GIS Programmer Analyst II West Virginia DOT, Division of Highways, Planning Section GTI Section, GIS Unit Phone: (304) 558 7448 E mail: Emiko.Hori@wv.gov