a multi-resolution modeling approach for supporting bus ......•network coding: export vs. manual...
TRANSCRIPT
TRANSPORTATION SOLUTIONS
A Multi-Resolution Modeling Approach for Supporting Bus Rapid Transit Design Randy Johnson, P.E., PTOE
Sai Sirandas, E.I.T.
DKS Associates
Source: Lane Transit District
Source: C-Tran
Presentation Outline
• Multi-resolution modeling overview
• Modeling for design support
• Introduce projects
• Model development and calibration
• Project design elements evaluated
• Lessons learned
Multi-Resolution Modeling
MACRO MESO MICRO
Regional Flows
Forecasting Concept Screening
Refined Forecasts
Corridor Operations Alternative Testing
Multimodal Impacts Corridor Operations
• Choose the right tools • Use the right data • Demonstrate the right solutions
Modeling for BRT Design Support EA LPA Final Design
Respond to design team questions
• Geometric Design Refinement
• Signal Operations and Design
• Transit signal priority
LTD West Eugene EmX Extension (WEEE)
Source: West Eugene EmX Extension Environmental Assessment, FTA
∽ 90 intersections
∽ 50 signals
C-Tran Fourth Plan BRT
Source: C-Tran
∽ 30 intersections
Macro
• Regional model subarea export (EMME -> VISUM)
Meso
• NAVTEQ street network
• Geometry and control
• Connector loading
• OD matrix estimation
Micro
• Export to Vissim 5.4 (complete static OD routes)
• Post-export clean-up (geometry, conflict areas etc.)
• Apply volume peaking profile
• Vissim adaptive import for future scenarios
• Parking, transit etc.
Model Development: WEEE
Micro
• Vissim 7 model with complex geometry, control, parking etc.
Meso
• Vissim -> Visum
• OD matrix estimation
• Synchro -> Vissim for signal controller files
• Vistro -> HCM roundabout analysis
Micro
• Import OD matrix from Visum to Vissim
• Parking lots (zones)
• Dynamic traffic assignment
• Convert to Static OD Routes -> Add peaking profile
Model Development: C-Tran
• Volumes
• Travel Times
• Queues
• Lane Utilization
• Visual inspection*
Model Calibration: WEEE & C-Tran
Key Inputs for Supporting Design Transit
• Vehicle model (length, operating speeds)
• Station dwell time distributions
• Transit schedule
Advanced Signal Timing
• Detector lengths/locations/settings
• Volume/density functions
• Signal Coordination
• Controller hardware/software constraints
Design Treatments General
• Two-way street conversion
• Roundabout vs. traffic signal
Design Treatments General
• Two-way street conversion
• Roundabout vs. traffic signal
Design Treatments Pedestrian
• Ped clearance
• Ped overlaps
• Ped Signal
Design Treatments Transit
• Business Access Transit (BAT) Lanes
• Queue Jump
• Near-side and far-side stops
• Transit Signal Priority
• How much priority?
• Check-in location
• BRT exclusive lanes and phases
• In-lane and pull out
Design Treatments Transit
• Business Access Transit (BAT) Lanes
• Queue Jump
• Near-side and far-side stops
• Transit Signal Priority
• How much priority?
• Check-in location
• BRT exclusive lanes and phases
• In-lane and pull out
Design Treatments Transit
• Business Access Transit (BAT) Lanes
• Queue Jump
• Near-side and far-side stops
• Transit Signal Priority
• How much priority?
• Check-in location
• BRT exclusive lanes and phases
• In-lane and pull out
Measures of Effectiveness • Concurrent vs. conflicting movement delay
• TSP calls vs. events
• BRT travel time and travel time reliability
• Build vehicle travel time
• Queues (storage length)
• 3D Videos
Lessons Learned • Multi-resolution modeling a cost effective approach
• Stakeholder involvement key to success
• ODOT Simulation protocol
• Check-in points with agency
• Network coding: export vs. manual Vissim
• Demand Development: Export to static routes vs. Export to Matrix + Vissim DTA
• Vissim 5.4 vs. 7
• Simulation controller vs. actual controller features
TRANSPORTATION SOLUTIONS
Questions? Randy Johnson, P.E., PTOE
Sai Sirandas