search

dystonse / dystonse-gtfs-data

Read gtfs and gtfs-realtime data, write them into a database, perform and export analyses and make predictions based on them.
9 stars 2 forks source link

Empty stop_pages due to mismatched trip_ids for every single prediction. #23

Open lenaschimmel opened 4 years ago

lenaschimmel commented 4 years ago

While investigating #6, we found that for several stops in Hannover, a lot of preditions were found (several hundreds), but each one of those was removed:

...
Could not compute metadata for departure with trip_id 144526159: The id 144526159 is not known
Could not compute metadata for departure with trip_id 144526014: The id 144526014 is not known
Could not compute metadata for departure with trip_id 144526015: The id 144526015 is not known
...

At the same time, the data in other cities was completely ok (Bremen, Oldenburg) or mostly ok except for the known issue #6 (Brunswick).

This happend around midnight (1st / 2nd of September), but also affected searches for time in the future (some hours or several days) and the recent past (some hours ago).

Today we had a non-standard schedule update at 19:09 and then again at 21:40, not sure if this may have caused it:

-rw-r--r-- 1 root root 62252251 Aug 29 21:40 gtfs-schedule-2020-08-29.zip
-rw-r--r-- 1 root root 62102163 Aug 31 19:09 gtfs-schedule-2020-08-30.zip
-rw-r--r-- 1 root root 60635322 Sep  1 21:40 gtfs-schedule-2020-09-01.zip