FSUTMS Transit Model Template Web Presentation Florida Department

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

Instructors/Support • Instructors David “Dave” Schmitt Senior Consulting Manager, AECOM 2800 Corporate Exchange Drive, Ste 300 Columbus, OH 43231 Phone: (614) 901 -6026 Email: david. schmitt@aecom. com Ashutosh “Ashu” Kumar Lead Consultant, AECOM 2800 Corporate Exchange Drive, Ste 300 Columbus, OH 43231 Phone: (614) 901 -6025 Email: ashutosh. kumar@aecom. com • Support Terry Corkery FDOT Systems Planning Office 605 Suwannee Street, MS 19 Tallahassee, FL 32399 Phone: (850) 414 -4903 Email: terrence. corkery@dot. state. fl. us Diana Fields FDOT Systems Planning Office 605 Suwannee Street, MS 19 Tallahassee, FL 32399 Phone: (850) 414 -4901 Email: diana. fields@dot. state. fl. us 2

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

Introducing the TMT 4

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_m odeling/comments/new_fsutms_transit_modeling_fr amework 5

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

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

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 8

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

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 10

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) 11

Where Does TMT Fit in the Overall FSUTMS Modeling Process? OVERALL FSUTMS MODEL FLOW GENERATION NETWORK DISTRIBUTION TRANSIT MODEL TIMEOFDAY ASSIGNMENT REPORTING Olympus Model without Transit Components 12

Transit Model Template imported into the Olympus Training Model 13

New Transit Model Standards • Standards originally developed in 1980 s 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. net 14

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. fsutmsonline. net/index. php? /transit_modeling/comments/n ew_fsutms_transit_modeling_framework/ 15

• Questions? 16

Installing the TMT 17

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

Link TM’s 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

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

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

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 TRANTIME[xx] for xx mode are defined Please see the Application Guide to the Transit Model Template for details 22

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

TMT: Screenshot 24

FSUTMS Voyager Transit Model TRANSIT MODEL FLOW TRANSIT NETWORK PREPARATION & ACCESS CONNECTORS TRANSIT PATH BUILDING Produces transit path for each IJ MODE CHOICE MODEL Gives transit trips for each IJ TRANSIT ASSIGNMENT Loads transit trips to each route TRANSIT REPORTING Each application is discussed on next few slides… 25

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

TRANSIT PREP Application Scripts that users should adjust are indicated in purple arrows 27

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

TRANSIT PATHS Application Scripts that users should adjust are indicated in purple arrows 29

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 FTA’s Summit program for user benefit analysis • Mode. Sum. TXT file summarizes the mode choice results 30

MODE CHOICE MODEL Application Mode Choice Summary File 31

Mode Choice Output Summary HBW - PK MODE XCHOICE RESULTS ******************************* Total Drive One Two+ Total MARKET SEGMENT Person Alone Pax Auto --------------------Zero Car HHs 11358. 2 0 7547. 7 2635. 7 10183. 4 One Car HHs 95125. 8 73326. 6 14615. 1 5966. 2 93908. 0 Two+ Car HHs 200454. 6 156097. 9 30979. 4 12667. 6 199744. 9 Walk Bus -----1141. 2 1142. 4 558. 6 PNR Bus ------0 38. 5 90. 0 KNR Bus -----33. 6 36. 9 61. 2 Total Transit ------1174. 8 1217. 8 709. 7 TOTAL 306938. 6 229424. 5 53142. 2 21269. 6 303836. 3 2842. 2 128. 5 131. 7 3102. 3 Productions: CBD Exurban Other 3272. 3 21780. 0 281886. 3 2395. 6 16151. 8 210877. 0 603. 1 3713. 9 48825. 3 228. 2 1392. 7 19648. 7 3226. 9 21258. 4 279351. 0 45. 4 503. 2 2293. 5 0. 0 9. 2 119. 2 0. 0 9. 2 122. 5 45. 4 521. 6 2535. 2 Attractions: CBD Exurban Other 16271. 6 37302. 1 253364. 8 11981. 3 27806. 2 189637. 0 2759. 9 6359. 5 44022. 8 1098. 8 2490. 7 17680. 0 15840. 0 36656. 4 251339. 9 402. 3 583. 7 1856. 2 14. 6 30. 7 83. 1 14. 7 31. 4 85. 6 431. 6 645. 8 2024. 9 1421. 08 0. 50 64. 23 0. 50 65. 83 0. 50 1551. 14 0. 50 1751. 1 1049. 1 41. 8 0. 2 126. 1 2. 3 0. 0 0 129. 4 2. 3 0. 02 0 2006. 6 1053. 7 41. 8 0. 2 Fare Revenue ($) Average Fare ($) Transfers: NONE TWO THREE + Average Auto Occupancy = 1. 157 32

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

TRANSIT ASSIGNMENT Application 34

TRANSIT REPORTING Module • Summarizes the assignment results in easy-toread formats • Generates the following reports – Route-level summary report – Stop-level summary report – Station activity report – Highway network with transit volumes 35

TRANSIT REPORTING Application Route-Level Summary Report Stop-Level Summary Report Station Activity Report 36

Route-Level Report File: TASUM_AYY. PRN 37

Stop-Level Report File: TASROUTE_AYY. PRN 38

Station Activity Report File: Stations_AYY. PRN 39

• Questions? 40

Walking Through the TMT Files and Networks representing the transit system Transit access, transit paths and mode choice Transit assignment 41

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

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

Transit Speeds • There are no predetermined ways of representing transit speeds in the transit model • Mxx. TIMEAM, Mxx. TIMEMD 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

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

Walking Through the TMT Files and Networks representing the transit system Transit access, transit paths and mode choice Transit assignment 46

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

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

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

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

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

Travel Components in Utility Expressions Auto Choices • • • Auto in-vehicle time Toll Parking cost Auto operating cost Terminal time HOV time saving etc… Transit Choices • • • Bus & rail in-vehicle time Walk (access &r transfer) time Auto access time Wait time (initial & transfer) Number of transfers Transit fare etc… 52

Nesting Structures: Auto (All Tiers) ►Auto nesting same as existing, larger area models 53

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 period Source of skims/impedances… walk-transit paths drive-transit paths 54

Nesting Structures: Transit B/C Areas) Source of skims… walk-bus paths walk-project drive-bus mode paths (Tier drive-project drive-bus drive-project mode paths 55

Nesting Structures: Transit (Tier B/C Areas) Tier B/C Areas • Local & express service • At least some park-andrides • At least system-wide boardings data, but onboard survey recommended • May be planning for New/Small Starts project in near future Build 4 paths period • Walk-bus • Walk-project/premium • Auto-bus • Auto-project/premium 56

Walking Through the TMT Files and Networks representing the transit system Transit access, transit paths and mode choice Transit assignment 57

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

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

Station Activity Plot (Transit On/Off) The loaded transit network is used for Transit On/Off plot 60

Line Volumes at Stop (Transit Line Profile) The loaded transit network is used for Transit Line Profile 61

Bandwidth Plots of Transit Volumes Shows transit volume on each street (thickness of the band width increases with increasing transit volume) 62

TAREPORT: Output Report Files • Three ASCII output files are produced (screenshots shown earlier) File TASUM_ayy. PRN Description 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

• Questions? 64

Calibrating the TMT Transit speed calibration Mode choice model calibration 65

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

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

File Format: Constants 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

File Format: Targets File Name: MC_TARGETS. DBF Folder: parameters 69

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

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

• Questions? 72

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) 73