search

Sadless74 / googletransitdatafeed

Automatically exported from code.google.com/p/googletransitdatafeed
0 stars 0 forks source link

Feature request: Detect ultra slow trip legs in feedvalidator #216

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Some experimental GTFS feeds have bad times that jump 24h with no reason.
A simple way to detect them is to introduce a warning, that could be an 
error when the confidence is high, about ultra slow trip legs:
when two consecutive timed entries in stop_times.txt of the same trip have a 
time difference >= 24h and their geodesic distance is <= 100km, this is very 
likely to be an error.

Note that 'two consecutive timed entries' means that there could be untimed 
entries in between.

Original issue reported on code.google.com by vi...@google.com on 5 Jan 2010 at 12:58

GoogleCodeExporter commented 9 years ago 
Issue 225 has been merged into this issue.

Original comment by tom.brow...@gmail.com on 11 Mar 2010 at 2:38

GoogleCodeExporter commented 9 years ago

Original comment by bdfer...@google.com on 26 Sep 2014 at 4:41

GoogleCodeExporter commented 9 years ago 
Issue 225 has been merged into this issue.

Original comment by bdfer...@google.com on 26 Sep 2014 at 4:41

GoogleCodeExporter commented 9 years ago 
Moved to https://github.com/google/transitfeed/issues/216

Original comment by bdfer...@google.com on 8 Oct 2014 at 12:13