metrics-mvp icon indicating copy to clipboard operation
metrics-mvp copied to clipboard

Add support for BART

Open hathix opened this issue 5 years ago • 3 comments

The #1 question we get is: can OT support BART as well? (And, more generally, can we support the other dozens of agencies that operate in SF?) Hopefully we can expand the work we do with Muni to other agencies with just some more configuration files.

This is a big project (kind of like expanding to a whole new city) but it's worth some investigation.

Ideally we could create a whole "SF" part of the site that integrates Muni, BART, AC Transit, Caltrain, etc.

hathix avatar Feb 20 '20 05:02 hathix

BART is different from other agencies we've integrated with so far in that they don't provide real-time GPS locations of the trains. BART's GTFS-Realtime API only provides estimated arrival/departure times at subsequent stops. If we store the estimated arrival/departure time data, it should be possible to figure out approximately when each train arrives and departs from each stop. We would need to implement a different algorithm for computing arrival times.

youngj avatar Feb 20 '20 05:02 youngj

What algorithm do you use for Trimet? I see that one isn't on Nextbus but has its own GTFS realtime feed.

hathix avatar Mar 05 '20 04:03 hathix

Trimet's GTFS-realtime feed provides GPS locations, so it uses the same eclipses algorithm as the nextbus agencies. Bart's GTFS-realtime feed only provides estimated arrival/departure times, not GPS locations.

youngj avatar Mar 05 '20 04:03 youngj