Options for Link-specific Travel Times

[e-lo]

Currently MTC codes link-specific travel times for several transit modes within the .lin definition.

Option 1 - Keep Line-Specific Travel Times

• This would mean coding and using the travel times in stop_times.txt

Advantages: Flexibility...you can have varying travel times by line (i.e. Electrified vs Diesel Caltrain) Disadvantages: Can't view as easily on network. Very prone to errors.

Option 2 - Code Transit Links with TOD/mode specific travel times on network

• This would mean coding and using the travel times in links.txt

Advantages: Easily viewed on network map. Simplicity. Disadvantages: Not as flexible.

Option 3 - Code travel times on network (Option 2) with an override option (Option 1)

Advantages: benefits of option 1 and 2 Disadvantages: would have to figure out an obvious override; adds complexity; more expensive to implement; more difficult to keep track of/troubleshoot

cc: @DavidOry

[DavidOry]

The best use case seems to be Caltrain, Bullet versus Local, Electrified versus Diesel. How would accommodate in Option 2? Separate network representations for Bullet, Local, and Limited networks? Explicit dwell times at each stations seems better, as that is what is causing the difference. But what about electrified versus diesel?

[e-lo]

I think the dwell times is how I would capture it. Include the time lost to startup/slowdown for various accel/deccel rates.

I would avoid separate network links.