FSUTMS Transit Model Template Web Presentation

1
FSUTMS Transit Model Template Web Presentation

• Florida Department of Transportation
• Systems Planning Office
• 605 Suwannee Street, MS 19
• Tallahassee, FL 32339-0450

May 29, 2009
1
2
Instructors/Support

• Instructors
• David Dave Schmitt
• Senior Consulting Manager, AECOM
• 2800 Corporate Exchange Drive, Ste 300
• Columbus, OH 43231
• Phone [phone]
• Email david.schmitt_at_aecom.com
• Ashutosh Ashu Kumar
• Lead Consultant, AECOM 2800 Corporate Exchange
  Drive, Ste 300
• Columbus, OH 43231
• Phone [phone]
• Email ashutosh.kumar_at_aecom.com

• Support
• Terry Corkery
• FDOT Systems Planning Office 605 Suwannee
  Street, MS 19
• Tallahassee, FL 32399
• Phone [phone]
• Email terrence.corkery_at_dot.state.fl.us
• Diana Fields
• FDOT Systems Planning Office 605 Suwannee
  Street, MS 19
• Tallahassee, FL 32399
• Phone [phone]
• Email diana.fields_at_dot.state.fl.us

2
3
Topics

• Introducing the transit model template (TMT)
• Installing the TMT
• Walking through the TMT
• Calibrating the TMT
• There will be a brief Q/A Session between topics

3
4
Introducing the TMT
4
5
What is the Transit Model Template?

• A package consisting of
• A Cube-Voyager application
• Application Guide
• Development Guide
• Two versions of the template
• One for cities with modest transit services
• Another for cities with more substantial services
• The guides are applicable to both versions
• The package is available for download at
  http//www.fsutmsonline.net/index.php?/transit_mod
  eling/comments/new_fsutms_transit_modeling_framewo
  rk

6
The TMT Includes

• All scripts, executables, applications and sample
  files needed to install and set up the transit
  model
• Application and development documentation
• A built-in routine for calibrating the mode
  choice model
• Several reports for transit model calibration and
  validation purposes

6
7
Why Develop the TMT?

• To provide a ready to install template fully
  consistent with the new statewide transit
  modeling standards
• No readily-available tool for end users since the
  development of new statewide standards
• Benefits
• Streamlined transit model development efforts
• Reduced documentation development
• Reduced model development costs

7
8
Who Can Use the TMT?

• Anyone!
• Some likely candidates
• MPOs looking to add a transit model to their
  existing highway-only model
• MPOs with an existing transit model in Tranplan
• MPOs with an existing transit model not
  consistent with new statewide standards

9
TMT Limitations

• It is not calibrated and validated to any
  particular location the template
• Is not intended to be plug-and-run software
• Does not know anything about your modeling area
• Does not automatically calibrate and validate to
  the travel behavior of the area
• It does not replace the need
• To collect transit data
• To calibrate the mode choice model
• To validate the transit model
• It does not improve the existing model

9
10
Transit Model Application Guide

• Chapter 1 Instructions for importing the transit
  model into a travel demand model
• Chapter 2 Descriptions of the model procedure
• Chapter 3 Descriptions of the catalog key, input
  files and output files of the transit model
• Chapter 4 Descriptions of the scripts that must
  be modified by the user to customize the transit
  model application to fit the model at hand
• This document can be used as a reference in the
  Technical Report 3 (Model Application Guidelines)
  prepared for FSUTMS models

11
Transit Model Development Guide

• Chapter 1 Describes the elements of the transit
  network, including the transit lines, modes,
  operators, fares, speeds, and access connectors
• Chapter 2 Describes the transit paths
• Chapter 3 Reviews at the mode choice model used
  and explains the structure and utility equations
• Chapter 4 Summarizes the transit assignment
  process and the transit assignment reports
• This document can be used as a reference in the
  Technical Report 1 (Data Development)

12
Where Does TMT Fit in the Overall FSUTMS Modeling
Process?
GENERATION
NETWORK
DISTRIBUTION
TRANSIT MODEL
OVERALL FSUTMS MODEL FLOW
TIMEOFDAY
ASSIGNMENT
Olympus Model without Transit Components
REPORTING
12
13
Transit Model Template imported into the Olympus
Training Model
13
14
New Transit Model Standards

• Standards originally developed in 1980s for
  original FSUTMS system were updated in 2006 for
  FSUTMS-Voyager System
• The following documents discusses the standards,
  guidelines, parameters and settings
• FSUTMS-Cube Transit Model Application
  Framework, FDOT, May 2007
• FSUTMS-Cube Transit Model Theoretical
  Framework, FDOT, May 2007
• FSUTMS New Standards and Enhancements A user
  oriented approach, FDOT, January 2006
• Transit Modeling FAQs, FSUTMS Online website

All documents are available at www.fsutmsonline.ne
t
14
15
Transit Model Framework

• The transit modeling guidance alters depending on
  the amount of the transit service
• Tier A guidance for areas with modest transit
  service and modeling needs
• Tier B/C guidance for areas with intermediate
  transit service and modeling needs
• Tier D guidance for area with substantial
  transit service and modeling needs
• Information about the modeling framework is
  available on FSUTMS Online at http//www.fsutmson
  line.net/index.php?/transit_modeling/comments/new_
  fsutms_transit_modeling_framework/

15
16

• Questions?

17
Installing the TMT
17
18
Steps to Install the TMT

• Step 1 Create a copy of the TMT in the existing
  highway-only model
• Step 2 Link all the output files from the
  highway model required as input by the transit
  model template (see next slide for screenshot)
• Step 3 Make necessary changes to the script and
  catalog keys in the model in order to customize
  it for the modeling area
• Step 4 Install the AUTOCON program (refer to
  readme.txt file in the model folder)

Detailed step-by-step procedure is described in
the Application Guide to the Transit Model
Template
18
19
Link TMs Input and Output Files
These files are outputs of the transit model and
the are input to the final highway assignment
These files are outputs of the highway model and
they should be linked to the right input boxes
Input Files to the Transit Model
Output Files of the Transit Model
19
20
Key Input Files

• Highway networks (Unloaded and Preassigned
  networks)
• Highway skims (free flow and congested skims)
• Person trip table by purpose
• Production trip rate file (GRATES) and dwelling
  unit weights file (DUWEIGHTS)
• Zonal data file
• Transit line file/system data file/fares
  file/percent walk file
• Transit coefficients file/mode choice
  constant/mode choice targets

20
21
Key Output Files

• Highway vehicle trip table for the final highway
  assignment
• Person trip tables
• Transit assignment summary reports
• Station activity report

21
22
Required Changes to the Scripts

• Default transit speeds are set to the auto speeds
  on the streets on which the buses run
• User should apply necessary logic to define and
  calibrate the transit speeds
• Any new transit mode other than already defined
  in the system data file will require changes to
  PT scripts where TRANTIMExx for xx mode are
  defined

Please see the Application Guide to the Transit
Model Template for details
22
23
Customizing the Template for Your Area

• Step 1 Review the default values of the catalog
  keys used in the model
• Step 2 Review the input files and customize it
  for the modeling area
• Step 3 Make necessary changes to the scripts so
  that it corresponds to the transit service in the
  modeling area
• Step 4 Calibrate the auto and transit speeds
• Step 5 Calibrate the mode choice model
• Step 6 Validate the base year transit
  assignments
• Step 7 Test the model for at least one future
  alternative to assess its forecasting ability

23
24
TMT Screenshot
24
25
FSUTMS Voyager Transit Model
Produces transit path for each IJ
Gives transit trips for each IJ
Loads transit trips to each route
Each application is discussed on next few slides
25
26
TRANSIT PREP Module

• Generates factors files which specifies the
  weights of various travel cost components (e.g.
  fare, wait time, in-vehicle time, transfer
  penalties etc.)
• Computes travel speeds for various transit modes
• Default transit speeds are set to auto speeds
• Users should modify the scripts to calibrate the
  transit speeds
• Generates access connectors (walk to transit,
  drive to transit and transfer connectors)
• Users should modify the scripts if a new mode is
  added

26
27
TRANSIT PREP Application
Scripts that users should adjust are indicated in
purple arrows
27
28
TRANSIT PATHS Module

• Builds transit paths
• Users should modify the scripts if a new mode is
  added
• Generates skim matrices for all the transit paths
• Removes the illogical/unreasonable paths
  developed by the PT module

28
29
TRANSIT PATHS Application
Scripts that users should adjust are indicated in
purple arrows
29
30
MODE CHOICE MODEL Module

• Trips between each interchange (zone) is divided
  into various auto and transit modes
• Mode choice calibration routine is included in
  the application
• Default mode choice constants are set to 1.000
  for all choices
• Generates binary files required by the FTAs
  Summit program for user benefit analysis
• ModeSum.TXT file summarizes the mode choice
  results

30
31
MODE CHOICE MODEL Application
Mode Choice Summary File
31
32
Mode Choice Output Summary

• HBW - PK MODE XCHOICE RESULTS
• 
  
• Total Drive One
  Two Total Walk PNR KNR
  Total
• MARKET SEGMENT Person Alone Pax
  Pax Auto Bus Bus Bus
  Transit
• -------------- ------- ------ ------
  ------ ------ ------ ------- ------
  -------
• Zero Car HHs 11358.2 0 7547.7
  2635.7 10183.4 1141.2 0 33.6
  1174.8
• One Car HHs 95125.8 73326.6 14615.1
  5966.2 93908.0 1142.4 38.5 36.9
  1217.8
• Two Car HHs 200454.6 156097.9 30979.4
  12667.6 199744.9 558.6 90.0 61.2
  709.7
• TOTAL 306938.6 229424.5 53142.2
  21269.6 303836.3 2842.2 128.5 131.7
  3102.3
• Productions
• CBD 3272.3 2395.6 603.1
  228.2 3226.9 45.4 0.0 0.0
  45.4
• Exurban 21780.0 16151.8 3713.9
  1392.7 21258.4 503.2 9.2 9.2
  521.6
• Other 281886.3 210877.0 48825.3
  19648.7 279351.0 2293.5 119.2 122.5
  2535.2
• Attractions
• CBD 16271.6 11981.3 2759.9
  1098.8 15840.0 402.3 14.6 14.7
  431.6
• Exurban 37302.1 27806.2 6359.5
  2490.7 36656.4 583.7 30.7 31.4
  645.8

32
33
TRANSIT ASSIGNMENT Module

• Assigns the transit trips to the various transit
  routes
• Generates output files required for reporting the
  assignment results

33
34
TRANSIT ASSIGNMENT Application
34
35
TRANSIT REPORTING Module

• Summarizes the assignment results in easy-to-read
  formats
• Generates the following reports
• Route-level summary report
• Stop-level summary report
• Station activity report
• Highway network with transit volumes

35
36
TRANSIT REPORTING Application
Route-Level Summary Report Stop-Level Summary
Report Station Activity Report
36
37
Route-Level Report File TASUM_AYY.PRN
37
38
Stop-Level Report File TASROUTE_AYY.PRN
38
39
Station Activity Report File Stations_AYY.PRN
39
40

• Questions?

41
Walking Through the TMT

• Files and Networks representing the transit
  system
• Transit access, transit paths and mode choice
• Transit assignment

41
42
Important PT Input Files (1)

• System Data File
• TSYSD.PTS file in the parameters folder
• Defines modes, operators and wait curves
• Transit Fares File
• TFARES.FAR in the parameters folder
• Defines the fare structure of the transit system
• Factors Files
• These files are automatically generated within
  the model
• Defines weights for various travel components
  (e.g. fares, wait times, transfer time, walk time
  etc.)

All PT steps use these files
42
43
Important PT Input Files (2)

• Transit Line File
• Should be coded in PT line format
• Public time table is used for coding the
  individual routes of the transit system
• Reflects the best possible representation of the
  route alignment, stop locations and the frequency
• Peak and off-peak services are represented
  separately

All PT steps use this file
43
44
Transit Speeds

• There are no predetermined ways of representing
  transit speeds in the transit model
• MxxTIMEAM, MxxTIMEMD fields added to
  transportation network representing travel time
  on the links for each mode xx
• Link time can be refined for individual routes
  using LINE keywords (e.g., TIMEFAC, DELAY, DWELL
  etc)

44
45
Transit Data in the Transportation Network

• The following transit-related data should be
  included in the highway network
• Transit-only links
• Station and park-ride micro-coding
• Station data information

45
46
Walking Through the TMT

• Files and Networks representing the transit
  system
• Transit access, transit paths and mode choice
• Transit assignment

46
47
Transit Access

• Transit access is connecting the zones (or
  centroids) to the transit network and vice-versa
• How is transit access represented? In two ways
• Connectors from centroids to transit stops
• For walk-access, estimates of transit
  accessibility for each zone
• The representation of transit access performs a
  function similar to that of centroid connectors
  in highway path-building and assignment

47
48
Three Types of Access

• Walk-access
• Walking between the zone (centroid) and the
  transit network
• Requires that a transit stop is nearby
• Auto-access
• Driving between the zone (centroid) and the
  transit network
• Assumes some type of parking is available near
  the first boarded transit service
• Transfer/sidewalks
• A short walk between the one transit service to
  the subsequent transit service

48
49
Transit Path-Building

• Determines best transit option for each I-J pair
  based on the cost of the trip
• The number of transit paths is controlled by the
  mode choice structure
• Example walk-transit drive-transit for
  peak and off-peak periods

49
50
Transit Skims

• Transit skims are the actual/perceived values of
  some of the cost components of a transit path for
  each I-J pair
• These skims are used in the mode choice to
  calculate the utility of the transit options

50
51
Mode Choice Nested Logit

• Nested logit models are logit models with a
  hierarchical structure, with similar choices
  grouped into nests
• All FSUTMS transit models use the nested logit
  formulation

51
52
Travel Components in Utility Expressions
Auto Choices
Transit Choices

• Auto in-vehicle time
• Toll
• Parking cost
• Auto operating cost
• Terminal time
• HOV time saving etc

• Bus rail in-vehicle time
• Walk (access r transfer) time
• Auto access time
• Wait time (initial transfer)
• Number of transfers
• Transit fare etc

52
53
Nesting Structures Auto (All Tiers)

• Auto nesting same as existing, larger area models

53
54
Nesting Structures Transit (Tier A Areas)

• Tier A Areas
• Local service only
• No park-and-rides
• Limited data available
• Build walk-transit drive-transit paths per
  period

Source of skims/impedances
walk-transit paths
drive-transit paths
drive-transit paths
54
55
Nesting Structures Transit (Tier B/C
Areas)
Source of skims
walk-bus paths
walk-project mode paths
drive-project mode paths
drive-bus paths
drive-bus paths
drive-project mode paths
55
56
Nesting Structures Transit (Tier B/C
Areas)

• Tier B/C Areas
• Local express service
• At least some park-and-rides
• At least system-wide boardings data, but on-board
  survey recommended
• May be planning for New/Small Starts project in
  near future

• Build 4 paths per period
• Walk-bus
• Walk-project/premium
• Auto-bus
• Auto-project/premium

56
57
Walking Through the TMT

• Files and Networks representing the transit
  system
• Transit access, transit paths and mode choice
• Transit assignment

57
58
Transit Assignment

• Loads the transit trips to the transit network
• For most cases, assignment is done by purpose and
  by period
• Home-based work trips are assigned to the peak
  period network
• Non-work trips are assigned to the off-peak
  period network
• Assignment is done in P?A (production?attraction)
  format in FSUTMS models

58
59
The NETO File

• NETO file is the loaded transit network produced
  during a PT assignment
• Network file is used to display volumes along the
  routes
• Transit On/Off
• Transit Line Profile

59
60
Station Activity Plot (Transit On/Off)
The loaded transit network is used for Transit
On/Off plot
60
61
Line Volumes at Stop (Transit Line Profile)
The loaded transit network is used for Transit
Line Profile
61
62
Bandwidth Plots of Transit Volumes
Shows transit volume on each street (thickness of
the band width increases with increasing transit
volume)
62
63
TAREPORT Output Report Files

• Three ASCII output files are produced
  (screenshots shown earlier)

File Description
TASUM_ayy.PRN Reports route-level results by period
TASROUTE_ayy.PRN Reports stop-level results by period
Stations_ayy.PRN Activity report at major transit hubs
63
64

• Questions?

65
Calibrating the TMT

• Transit speed calibration
• Mode choice model calibration

65
66
Transit Speed Calibration

• Compare the model transit travel times
  (end-to-end) against the observed times
• Observed times generally obtained from public
  time table
• The print file of a PT module contains the travel
  time by route
• If the system contains extensive transit service,
  categorize the routes by mode and geography
• The following results should be looked at
• Relative difference
• Absolute difference
• RMSE

66
67
Mode Choice Model Calibration

• An iterative process
• Adjusting bias constants with the goal of making
  the sub-modal trips match observed targets (by
  purpose and market segmentation)
• Reviewing the constants for reasonableness
• Re-adjusting bias constants if necessary
• How to accomplish this in the transit model

67
68
File Format Constants File
File Name MC_CONSTANTS.DBF Folder parameters\
Note Default constants used in the file is
1.000 If the choice is not available, constant is
-999.99
68
69
File Format Targets File
File Name MC_TARGETS.DBF Folder parameters\
69
70
Steps for Calibrating the Mode Choice Model

1. Develop a mode choice target file
2. Set the value of MC_Calib key in the catalog to
   1
3. Open the Mode Choice Calibration Application
   (next slide)
4. Make sure that the scenario representing the
   calibration year model (Base in the Transit
   Model) is selected
5. Set the number of iterations initial calibration
   may take 30 or more iterations
6. Run the calibration application
7. Review the CalibSum.TXT file in the output folder
   for the difference between the observed targets
   and the estimated target shares for the final
   iteration run
8. If this difference is large (for e.g., within 1
   for bigger markets), repeat the steps from Step 3
   onwards

70
71
Calibrating Mode Choice Model
Select the Base Scenario
Adjust the number of calibration loops
71
72

• Questions?

73
Thank You!

• Please go to www.fsutmsonline.net to signup for
  the FSUTMS Transportation Modeling Newsletter
  mailing list
• If you would like training for the TMT, please
  watch for the Transit Modeling Workshop date (to
  be held in FY 10)