start_and_end_date_out_of_order: GTFS validation rule Error
A start_date is greater than its corresponding end_date (calendar.txt or feed_info.txt).
What the rule checks
A start_date is greater than its corresponding end_date (calendar.txt or feed_info.txt).
Severity: error
An error marks data that breaks the GTFS specification. A journey planner or a rider app may refuse the file, or show a wrong version of it. Correct it before publishing the GTFS.
Where it applies
The rule applies to calendar.txt and feed_info.txt.
Finding and correcting it
Open the GTFS in GTFS Express. Reading is free, and the validation, by the MobilityData validator and the rules of GTFS Express itself, lists the occurrences of start_and_end_date_out_of_order 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
The MobilityData GTFS validator uses the same code, start_and_end_date_out_of_order. Its documentation describes each rule: MobilityData validator rules.