silas-warner
Uploaded by
16 SLIDES
282 VIEWS
160LIKES

Forecasting/Simulation Interface on I-694 Reconstruction from I-35E to I-35W

DESCRIPTION

This document details the reconstruction of I-694 from I-35E to I-35W, led by MnDOT, emphasizing the widening of the freeway, modification of five interchanges, and the importance of traffic demand modeling. It highlights critical aspects of simulation processes using CORSIM, including model calibration, driver behavior, and congestion dynamics. The analysis reveals challenges in merging forecasting with simulation, indicating the need for improved integration to address bottlenecks and enhance transportation planning. Key recommendations aim to refine data inputs for more accurate predictive modeling.

1 / 16

Download Presentation

Forecasting/Simulation Interface on I-694 Reconstruction from I-35E to I-35W

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. Forecasting/Simulation Interface on I-694 Reconstruction from I-35E to I-35W Mn/DOT Travel Demand Modeling Coordinating Committee December 12, 2005 Meeting Jaimie Sloboden

  2. I-694 Reconstruction from I-35E to I-35W • Widen I-694 from 4-lanes to 6-lanes • Modification/reconstruction of 5 interchanges • I-35W • TH 10/Snelling/Hamline • Lexington • Victoria St • Rice Street • Completes Un-weave the weave • I-35W not part of the “plan”

  3. Project Limits

  4. MN/DOT’s Freeway Simulation Process • CORSIM is the Current Simulation Program (being reviewed by Eil Kwon and U of M) • Field Observations • Base Model Development • Error Checking • Model Calibration • Driver Behavior • Alternatives Analysis • Final Report

  5. Simulation Limits (physical)

  6. Simulation Limits (Temporal) • Duration of Congestion in Metro Area is 3 to 5 hours per peak period • 1 hour simulation models in metro inadequate (Lake St Access Case Study proved this) • 15 minute data

  7. Simulation Limits vs. Project Limits • Extended Boundary Limits required to “Feed” Traffic into Project Area • Analysis of non-project elements “required” • Non-project elements in simulation model may or may not be part of TSP, TIP, STIP, TPP • Non-project elements may create a bottleneck impacting the analysis

  8. Forecasting Process • Mn/DOT Metro Guidelines • Reviewed and updated Land Use • Reviewed and updated Network Attributes • Screen line Evaluation • Post Processing applied • Base error applied to Future error • Reasonableness Checks

  9. Regional Model Network

  10. Forecast ProductPeak Hour & Daily

  11. Converting Forecasts to Simulation Inputs • Single Peak Hour (forecast) converted to 3-hour 15 minute data (simulation) • 694 model had 15,000 traffic volume inputs • Big Math Problem! • Two Approaches • Option 1: factor existing 15 minute data by peak hour ratio • Option 2: Forecast 15-minute data o-d (Crosstown model) • Option 1 used for I-694

  12. Sample Calculations • Existing 15-minute pattern duplicated • There are challenges with this process

  13. Origin-Destination Data

  14. Partial 15 minute Volume Data Base for Freeways

  15. System Origin-Destination Data

  16. Conclusions • Better interaction required between Forecasting and Simulation processes • Preparing 15-minute forecasts for simulations problematic • Forecasting process needs to catch up with Simulation • Qa/QC • Network coding errors • Systematic approach • Simulation exposes many issues with the “Plan”, dealing with these new issues

More Related