austinjpaul
austinjpaul
This was fixed by #3505, which I assume will be included in the next release.
just saw this, check green line for examples of many stop ids for the same stop simultaneously On Sat, Dec 23, 2023, 2:42 PM Devin Matte ***@***.***> wrote: > Okay...
This probably isn't accurate data, but it doesn't help the green line's case: https://dashboard.transitmatters.org/rapidtransit?config=Green,70241,70243,2021-03-29
https://dashboard.transitmatters.org/rapidtransit?config=Green,70235,70211,2020-06-04,
Park street is going to require handling of stop 71199, the id for "Park Street - Green Line - Drop-off Only"
hell yeah! were going to have to validate the data before we publish these -- i remember seeing some things like that huge spike in march and it wasn't real.
I think a disclaimer isn't quite enough here - if there's garbage data we should probably go remove it manually from the backing files so we don't display it.
Hi Ian, So glad you're interested in this! Our `chalicelib` implementation is quite closely tied to our backend infrastructure, so i'm not surprised you ran into issues. However, our backend...
Yeah, you're not wrong. Stops can be found in our front-end source code. https://github.com/transitmatters/t-performance-dash/blob/main/src/bus_constants/22.json It's basically route-direction-stop_id. Sometimes there are multiple stop ids because of changes to GTFS or bus...
Travel times was updated in 8ab931be1db0a9247433bedc9f6fea9e45dda36e for sanity, but we should still consider correctness.