hasadna / hasadna/OpenTrainCommunity

Unable to know if a station was skipped

Open
#52 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
25
Forks
13
PR merge metrics
No merged PRs in 30d

Description

@ekeydar We said previously that we are unable to know if a train station was skipped during a trip. Why is this so? Can't we simply compare it to the published train schedule? For instance, the schedule says train #29 is supposed to go on Monday from Bat Galim 10:09 to Hof HaCarmel 10:16 to Tel Aviv Univ 11:00. If train #29 doesn't arrive at Hof HaCarmel and later arrives at Tel Aviv Univ, then we can safely say that Hof HaCarmel was skipped and include this fact in our statistics.

The biggest problem I can see with this solution is station closures. Once in a while, a station is closed due to construction or rail improvements, in which case it would be difficult to distinguish these two cases. Is there a way to also request a formatted table of station closures, dates of closures, etc.? (Perhaps we can use a simple heuristic -- if > 10 train arrivals at station X are skipped, then we can assume the station is simply closed, instead of a single train needing to 'catch up' on its delayed route).

Even having a general statistic "this station did not provide service to train users X% of the time it was *supposed to provide service* (either due to construction or due to stops being skipped)" would be a very helpful statistic, even if we can't provide the exact reason.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.