big_gap_in_service: GTFS validation rule Info
A service of calendar.txt runs on no day for more than 13 days in a row between two of its active dates, the exceptions of calendar_dates.txt counted. The notice gives the first and the last day of…
What the rule checks
A service of calendar.txt runs on no day for more than 13 days in a row between two of its active dates, the exceptions of calendar_dates.txt counted. The notice gives the first and the last day of the gap.
Severity: information
An information notice marks a feature of the GTFS that does not affect its conformity. It helps to understand the data and asks for no correction.
Where it applies
The rule applies to calendar.txt and calendar_dates.txt.
Finding and correcting it
Open the GTFS in GTFS Express. Reading is free, and the validation, by the MobilityData validator, lists the occurrences of big_gap_in_service with the file and rows involved. The correction is made in a draft, by hand or from a brief, with the licence: the corrected GTFS is validated again before it is delivered, and the change can be undone.
In the MobilityData validator
big_gap_in_service is the code of the MobilityData GTFS validator, the one its report carries. Its documentation describes the rule: big_gap_in_service on the MobilityData site.