1 / 33

Integrating EMME/2TM into the GIS World

Integrating EMME/2TM into the GIS World. “TerraLogic GIS “ RoadLink ”. Interoperability. RoadLink. Customized Solution. Contributors. Public Works, Lewis County, Washington Mark Cook – Director, Project Manager Matt Hyatt & Stearns Wood – GIS Consultants

arella
Download Presentation

Integrating EMME/2TM into the GIS World

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Integrating EMME/2TM into the GIS World

  2. “TerraLogic GIS “RoadLink” Interoperability RoadLink Customized Solution

  3. 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

  4. GIS Objectives • Interoperability of Road Networks GIS Maintenance/Mgmt Street Assets EMME/2

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

  6. Project Scope - Client • Lewis County Public Works Department in Washington State, USA Lewis County, WA

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

  8. Project Scope – The Challenge • Converting Model data to Map data Data Conceptual

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

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

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

  12. EMME/2 data concerns • Non-Ideal Situation • Ideal if each link falls neatly onto a single route. 1087 1088

  13. 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

  14. 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

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

  16. 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

  17. 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

  18. 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

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

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

  21. Road Data FID Shape … 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

  22. Create Routes FID Shape ALIAS 0 Polyline Main St 1 Polyline State Route 6 3 Polyline 1st St 1st St State Route 6 Main St

  23. Locate Nodes FID Shape RID MEAS NODE_ID …. 0 Point M Main St 14441.25 752 1 Point M 1st St 1271.33 752 2 Point M State Rt 6 12121.22 753 1st St State Route 6 Main St 753 752

  24. Transfer Node Event DataTo Link Records ToNode data set NodeID RouteId Measure 22 634 2.88 22 289 1.12 22 238 7.23 22 355 0.00 FromNode data set NodeID RouteId Measure 11 234 12.345 11 289 3.678 “RoadLink” • Link Data • Link_id FromNode ToNode RouteID FromMeasure ToMeasure Data1 Data2 • 11 22 289 3.678 1.12 HOV 11.3 • 752 753 HOV 21.0

  25. Locate Linksas Linear Events

  26. Locate Linksas 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. • Link Data • Link_id FromNode ToNode RouteID FromMeasure ToMeasure Data1 Data2 • 752 753 HOV 21.0 1st St State Route 6 Main St 753 752

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

  28. 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

  29. “RoadLink” Administrative Tool

  30. “RoadLink” General User Tool

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

  32. “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.)

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

More Related