Integrating EMME/2TM into the GIS World

“TerraLogic GIS “RoadLink” Interoperability Customized Solution RoadLink

Contributors Public Works, Lewis County, Washington  Mark Cook – Director, Project Manager  Matt Hyatt & Stearns Wood – GIS Consultants  Michael Booth, Perteet Inc. - Project Manager  Robert Tung, PhD, RST International – Modeler  Jin Ren, Consultant – Modeler  Bin Lee, Perteet Inc. – Model Support  Chris Hansen, TerraLogic GIS – Application Development Manager  Richard Chase, TerraLogic GIS – Senior Application Developer

GIS Objectives  Interoperability of Road Networks GIS EMME/2 Maintenance/ Mgmt Street Assets

GIS Method Highlights Route# 275 Arterial Name Dubuque Rd. FTRP Intersect Name 131 st Ave. SE Measure st Ave. SE Relational Database Measure 3.5 Event Theme Database Connect Dubuque Rd 131 st Ave. SE 135 st Ave. SE Measure 7.75

Project Scope - Client  Lewis County Public Works Department in Washington State, USA Lewis County, WA

Project Scope - Need  Integrated system to view transportation modeling results from EMME/2 in a GIS ArcMap environment Lewis County, WA

Project Scope – The Challenge Data Conceptual  Converting Model data to Map data

Data Representation Typical Link representation of road network  Link data vs. Road data EMME/2 Link Road Data

EMME/2 data concerns  Non-Ideal Situation Ideal if nodes all placed precisely on existing road polylines 1033 EMME/2 Link

EMME/2 data concerns  Non-Ideal Situation Ideal if intersection nodes at exact intersection locations they represent 1055

EMME/2 data concerns  Non-Ideal Situation Ideal if each link falls neatly onto a single route

EMME/2 data concerns  Non-Ideal Situation Ideal if more nodes are used Work-around to place node at half way point Move Node to here

Node Data Concerns  Node Placement Nodes not placed close enough to actual road Nodes not placed accurately at intersections Sometimes one node used for two intersections  Solution Pre-conditioning of Nodes is required For 1000 nodes this can be done manually

Road data concerns State Road Data County Road Data City Road Data Lack of unified road route system

Route systems & Linear Referencing  Creating Routes allows events to be mapped to a subsection of the route using linear referencing Point events happen at single point location Linear events occur along a linear section

Road data concerns County Routes + EMME2 Links, missing are state roads and city roads Roads change names as direction changes Roads change names as they enter cities Road sections shared by more than one route Complexity Level – High Solution: Create new unified route system

New Unified Route System  County can continue using existing route system for all current administrative needs  New Route system for correlating EMME2 data with county/state/city roads only  Challenges include Accurate Node Placement Creating Sufficient Route system Improving Efficiency

Automate the Process 1. Automate as much as possible! 1. Route Creation using ArcMap tools 2. Place nodes on Routes using ArcMap tools 3. Correlate link records with node route data using TerraLogic GIS “RoadLink” admin tool 2. Manual Edit Nodes if necessary 3. Manual Edit Roads “Alias” field if necessary 4. Repeat

Set up – may take multiple iterations Create RoutesLocate Nodes on Routes Transfer Node data to Link records “RoadLink” Road data ArcMap Locate Links as Linear Road events ArcMap QA/QC Link Events and Revise Road data accordingly

Road Data FIDShape … NEW FULLNAME ALIAS 0 Polyline …… 0 Main St Main St 1 Polyline …… 0 Main St Main St 2 Polyline …… 0 State Route 6 State Route 6 3 Polyline …… 0 State Route 6 State Route 6

Create Routes FIDShape ALIAS 0 Polyline Main St 1 Polyline State Route 6 3 Polyline 1 st St State Route 6Main St 1st St

Locate Nodes FIDShape RID MEAS NODE_ID …. 0 Point M Main St Point M 1 st St Point M State Rt State Route 6Main St 1st St 753

Transfer Node Event Data To Link Records Link Data Link_idFromNode ToNode RouteID FromMeasure ToMeasure Data1 Data HOV HOV 21.0 FromNode data set NodeID RouteId Measure ToNode data set NodeID RouteId Measure “RoadLink”

Locate Links as Linear Events

QA/QC issues This case shows a situation where the linear event cannot be made because the link spans more than one route. The solution is to rename the “Alias” attribute of the Main St. road section to State Route 6 and then complete the cycle again. 752 State Route 6Main St 1st St 753 Link Data Link_id FromNode ToNode RouteID FromMeasure ToMeasure Data1 Data HOV 21.0

Set up – may take multiple iterations Create RoutesLocate Nodes on Routes Transfer Node data to Link records “RoadLink” Road data ArcMap Locate Links as Linear Road events ArcMap QA/QC Link Events and Revise Road data accordingly Pre-Edited Node data

TerraLogic GIS “RoadLink” Tools  Administrative Tool Coordinates Node events with Link records  General User Tool Allows direct import of EMME/2 model data into DBaseIV table and adds route data

“RoadLink” Administrative Tool

“RoadLink” General User Tool

“RoadLink” Benefits  Showing the EMME2 data on the Map Create linear event table from DBaseIV table and show labels Actual

“RoadLink” Benefits  A user can, with relative ease, take the results of an EMME/2 model run and display the results in a typical GIS mapping environment  Data such as daily traffic volume can be seen on the map associated with the roads that will actually carry the traffic and not as just a vague connection between destinations  Data to be conveyed visually in a much more informative and intuitive manner than by using the link lines alone.  The decision to show or hide the actual link sections is up to the GIS map user.  Interoperability with EMME/2 AND other road networks (pavement management, street asset inventory, etc.)

For More Information…    Project Contributors: Mark Cook, Lewis County Public Works, Washington Michael Booth, Perteet, Inc. Dr. Robert Tung, RST International Jin Ren, PE, Jin Ren Consulting RoadLink Interoperability Customized Solution