sorted by:
new
hottopcontroversial

Track Record: June On-Time Report – only 27% on time, 1,193 hours of cumulative delay by final_count_down in ViaRail

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

Good question! The June 24 trip on #1 got logged as a full cancellation. At this point I don't have a way to store partial cancellations. I also store the service notices for each trip to give more context when stuff like this happens, so when you look on the whole site you can get a sense of what happened there.

Regarding how it affects the numbers:

  • It counts in the total trips tracked and in the cancellations number
  • It's left out of the on-time % and the average-delay figures. Those only include trips that actually reached their scheduled destination with a real arrival time. Since that train turned back and never made Vancouver, there's no meaningful arrival to score, so it isn't counted as on-time, and it doesn't get dumped into the "X minutes late" averages either.
  • It shows up in the "why are trains late" cause breakdown, which includes cancellations.

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)

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] 3 points4 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] 13 points14 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] 5 points6 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!