Viewing a single comment thread. View all comments

Stronkowski t1_j9ue97e wrote

Is this that different from what TransitMatters already had?

9

austinmartinyes OP t1_j9uffl7 wrote

TransitMatters extrapolates slow zones from travel time data, which they’ve done a very good job with. This information is straight from the horse’s mouth.

35

SutterCane t1_j9ugq8b wrote

Don’t call the MBTA a horse.

Horses are reliable.

27

ZetaInk t1_j9uhrqr wrote

Green Line gets me to Kenmore about as quick as the pony express got mail across the west though

12

SkiingAway t1_j9uy0ps wrote

The Pony Express averaged 10mph. The B/C/E branches only average 7-8mph.

10

ZetaInk t1_j9uzwja wrote

So what you're saying is we need a dedicated horse lane.

10

charons-voyage t1_j9vk5ti wrote

You can lead the MBTA train over the water but you can’t put it in the drink. Except that one time when the Orange line caught fire.

6

vhalros t1_j9ugq9a wrote

TransitMatters can figure it out from travel times, which is great because it got the T to actually admit some of the problems. It seems like the additional information TransitMatters can't necessarily figure out is why there is a slow down (track? tunnel? train? signals?), and precisely how many miles have what level of speed restriction. Of course, what would be really great is having some idea when they are going to fix it.

12

Smilerk t1_j9v4nh9 wrote

Yes! We use a combination of GTFS feeds, public MBTA apis, and data the mbta gives us itself. But it is only ever arrival and departure times. We have no insight into speeds of specific track segments between two stops

5