search

transitmatters / mbta-performance

For processing performance data for the data dashboard
MIT License
0 stars 0 forks source link

Include MBTA benchmark stats #2

Closed devinmatte closed 2 months ago

devinmatte commented 3 months ago

Just like we had with the performance API and gobble, we should include the benchmark so we know how bad/good each trip/headway is to the expectation

devinmatte commented 3 months ago

Performance API:

Screenshot 2024-04-18 at 7 15 53 PM

Us, using LAMP/GTFS data

Screenshot 2024-04-18 at 7 11 07 PM
devinmatte commented 2 months ago

Okay only missing piece is to rename scheduled_travel_time to scheduled_tt now to reach feature parity, or, need to handle both names in the frontend. Frontend has a handle for this now

devinmatte commented 2 months ago
Screenshot 2024-05-02 at 12 56 11 PM

Ah looks like the travel times benchmarks are off

devinmatte commented 2 months ago

Alright so after my investigation I think we need to read from gtfs for travel time benchmarks just like we do in gobble. I think we can mostly copy over the code from gobble OR we can use https://github.com/transitmatters/mbta-gtfs-sqlite

devinmatte commented 2 months ago

We may need something like (this is some code snached from gobble, syntax isn't 100%) https://github.com/transitmatters/mbta-performance/compare/gtfs-traveltimes?expand=1 But I haven't been able to get it working quite right Probably quick work for @hamima-halim?

devinmatte commented 2 months ago

Closing this, we now have benchmark stats, they just need refining. We should make issues for the refining separately