invalid_exact_times: GTFS validation rule (frequencies.txt) Error
exact_times is not 0 or 1.
What the rule checks
exact_times is not 0 or 1.
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 frequencies.txt. This file describes trips given by a headway rather than time by time.
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 invalid_exact_times 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, invalid_exact_times. Its documentation describes each rule: MobilityData validator rules.