1. OKI/MVRPC Travel Demand Model:
PT Transit Model
Futura 2009
Andrew Rohne
Travel Modeling Department Manager
Ohio-Kentucky-Indiana
Regional Council of Governments
Cincinnati, Ohio
3. Introduction - Current Model
Current Model uses TranPlan transit... issues
Difficult to interpret input & output files
Built GIS Tools to assist... imperfect solution
Old tools, no maintenance, no 64-bit capable
upgrade
No customization of some key items (wait times, etc)
Old file formats (conversions....)
Goals
Fewer Inputs
Geodatabase Inputs
Keep in mind: Census, HHTS, and TOBS next year
5. OKI/MVRPC Model by the Numbers
11 County Model Area - 3,924 Square Miles
3 States, 2 MPOs, 2 CBDs (Cincinnati and Dayton)
2.7 Million People (2005) (1.9 Cincinnati, 0.8 Dayton)
5 Fixed Route Transit Services (with different fares,
etc.)
6 Different Flat-Rate Fares (Local vs. Express)
1 Zone Fare Structure (5 Zones)
Differing transfer prices within and among some
systems
7. The Transit Model
8 User Classes, not always used - Needed for Mode
Choice
Local Bus Walk and Drive (classes 1 and 2)
Express Bus Walk and Drive (classes 3 and 4)
Light Rail Walk and Drive (classes 5 and 6)
Inter-city Rail Walk and Drive (classes 7 and 8)
GIS Based Inputs Where Possible
Lines
Stations and Park-N-Ride Lots
Walking Barriers
Customized Walk Access using Python
On-The-Fly Percent Walk Computation using Python
37. Create Final Transit Network
Create Final Transit
Network
Runs Twice - Peak and
Off-Peak
7 Fare Structures
6 Flat-Rate
1 Zone Structure
8 Factors files
Local Bus Walk & Drive
Express Bus Walk &
Drive
Light Rail Walk & Drive
38. Conclusion
Not Reinventing the Wheel
Quick Rebuild of Old semi-functional Transit Model
Reduced potential for error from not updating files
Transit On-Board Survey Fall 2010
GPS-Based Household Travel Survey Right Now!
Actual implementation later this year...