You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 30, 2023. It is now read-only.
There are already checks that a feed does not start in the future or finish
within a month. But more than once we have seen data that has some service
in the past and some in the distant future but none around the current date.
There should be a warning if it is possible to find a 14 days with no trips
anywhere from max(start_date, today - 14 days) to min(end_date, today + 60
days). This should be fairly easy starting with the feedvalidator.py code
that generates the summary of trips per day.
From [email protected] on September 22, 2009 08:15:57
There are already checks that a feed does not start in the future or finish
within a month. But more than once we have seen data that has some service
in the past and some in the distant future but none around the current date.
There should be a warning if it is possible to find a 14 days with no trips
anywhere from max(start_date, today - 14 days) to min(end_date, today + 60
days). This should be fairly easy starting with the feedvalidator.py code
that generates the summary of trips per day.
Original issue: http://code.google.com/p/googletransitdatafeed/issues/detail?id=188
The text was updated successfully, but these errors were encountered: