220 likes | 345 Vues
The November 2007 update provides an overview of the FSUTMS Transit Modeling Framework's current status and planned enhancements. Key developments include finalized documentation, training workshops, and updates to external programs. The framework has been successfully implemented in METROPLAN Orlando, with ongoing developments for CFRPM and Miami-Dade transit models. Planned enhancements aim to simplify model development and improve mode choice features, with a focus on flexibility and user input. Resources are available on the FSUTMSOnline website.
E N D
FSUTMS Transit Modeling Framework:Status Update November 28th, 2007
Topics • Framework status & update • Planned enhancements for Framework
Framework Timeline (1 of 2) • Winter 2006 • Introduced at MTF • Finalized summary documentation • Spring 2007 • Finalized external programs • Developed path-building setups • Developed training workbook
Framework Timeline (2 of 2) • Summer 2007 • Developed FAQ • Updated external programs & documentation • Fall 2007 • Scripted REWALK program
Outreach • Framework web page on FSUTMSOnline • Frequently Asked Questions document • 3-day training workshops • June 2007 (Orlando) • November 2007 (Clearwater) • April 2008 (Orlando) • Technical support
Web Resources • Documents • Theoretical & applied summaries • FAQ list • Training workbook • Instructions for external programs • Programs/Scripts • Auto-access connector • Assignment reporting • Percent walk/walk connector coordination • Path-building setups (Tiers A & B/C) • Training model All these resources are available on FSUTMSOnline.net
Transit Modeling Web Page • http://www.fsutmsonline.net/index.php?/transit_modeling/comments/new_fsutms_transit_modeling_framework
Framework Implementations • Successfully implemented for METROPLAN Orlando model • Tranplan → Voyager conversion • No other major changes to transit model other than transition to new Framework • Under development • CFRPM • Tranplan → Voyager conversion • Transition to new Framework only major change to transit model • Miami-Dade – only task is to implement Framework • NERPM – tasks include: • Incorporating Framework • Making transit model compliant with known FTA New Starts modeling guidance • Validate to 2005 base year • Incorporate latest travel data (on-board, speeds)
Framework ImplementationsIssues • Required modifications to existing mode choice models due to Framework not explicitly described • Resulted in Transit Framework FAQ • Minor adjustments needed to AUTOCON & TAREPORT • Handling decimal node coordinates (AUTOCON) • Handling separate peak/off-peak networks (TAREPORT) • Corrected bug in TAREPORT program that incorrectly reported route-level Pax-Mi and Pax-Hr calculations
Framework ImplementationsImpressions • Overall Framework holding up well; no changes • Framework not applicable to areas with unique markets • Example: Fringe parking in Jacksonville • Expecting AUTOCON & TAREPORT to need minor changes as more models are converted to new Framework • Available information may not be sufficient for easy conversion
Planned Enhancements for Framework… • Short-Term
Develop Transit Model Application (1 of 2) • Virtually complete transit model, includes connectors, path-building, mode choice & assignment steps • Benefits • Simplified model development, with reduced time & cost • Consistency within all elements • Two setups • Tier A – no percent walks, simplified transit paths • Tiers B/C – percent walks, expanded transit paths
Develop Transit Model Application (2 of 2) • Mode choice features • Written in Voyager script • Auto-calibration routine • Ability to create data files for Summit • Non-included elements • Transit networks • Percent walks • Transit speed methodology and computations • Description & instructions how to incorporate into model will be documented
Other Short-Term Enhancements • Script transit assignment reporting program • Conversion from FORTRAN • Consistent with goal of eliminating external programs • Enhance AUTOCON with ability to read Voyager matrices • Existing version requires conversion of skims to Tranplan-format
Other Short-Term Enhancements • Review transit path-building parameters • Review transit surveys conducted across the state within the past 5-10 years • Suggest possible changes in connector- and path-building logic, with emphasis on auto-access connectors
Planned Enhancements for Framework… • Medium-Term
Generic Mode Choice Model (1 of 2) • Objective • To provide flexible scripts similar to existing generalized nested logit program • Key issues • Voyager script not as flexible as program • Could be implemented in at least three ways: • External program used to develop script(s) or • PILOT script to create a script • Generic script • More variety of structures likely available via external program or PILOT script
Generic Mode Choice Model (2 of 2) • Key issues (cont’d) • Is it necessary if transit model application is already available? • Would like input from Transit Committee on priority
Other Medium-Term Enhancements • Script auto-access connector program, AUTOCON • Will fulfill goal of eliminating all external programs • Cannot be completed without additional features, specifically with GENERATE control statement • Revise transit modeling workshop • Focus on correct use of transit model application • Simplify technical elements
Planned Enhancements for Framework… • Long-Term
Long-Term Enhancements • Research multi-path approaches • Key objectives • Adds value beyond existing single-path/nested logit mode choice approach • Consistent with New Starts guidance • Continue testing began in 2006 • Investigate possibility of computing percent walks within model stream • Would eliminate offline GIS computations & file preparations • Depends on future versions of Voyager