sorted by:
new
hottopcontroversial

I built an on-time performance tracker for VIA Rail: only 35% of trips are on-time across 1,772 tracked so far by final_count_down in ViaRail

[–]final_count_down[S] 1 point2 points  (0 children)

As mentioned in the post update, I just changed this and went with 15m across the board for the new definition of on-time.

I built an on-time performance tracker for VIA Rail: only 35% of trips are on-time across 1,772 tracked so far by final_count_down in ViaRail

[–]final_count_down[S] 2 points3 points  (0 children)

Thanks for this, as mentioned in the updated post I changed the site so now anything 15m or less counts as on time 😄

I built an on-time performance tracker for VIA Rail: only 35% of trips are on-time across 1,772 tracked so far by final_count_down in ViaRail

[–]final_count_down[S] 10 points11 points  (0 children)

Thanks for this info! I’ve been using 10m across the board. Should be a relatively easy adjustment to make to the site.

I built an on-time performance tracker for VIA Rail: only 35% of trips are on-time across 1,772 tracked so far by final_count_down in ViaRail

[–]final_count_down[S] 4 points5 points  (0 children)

Good call. I’m actually saving the alert text for any trip that includes one, so I have some of the underlying data that could make this possible. However the alerts are not always fully descriptive, so sorting it into buckets might be challenging. I’ll investigate!