timeframe_only_start_or_end_time_specified: GTFS validation rule Error
A timeframes.txt row sets only one of (start_time, end_time). Both fields must be either both present or both absent.
What the rule checks
A timeframes.txt row sets only one of (start_time, end_time). Both fields must be either both present or both absent.
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 timeframes.txt. This file describes the time ranges over which a fare applies.
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 timeframe_only_start_or_end_time_specified 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, timeframe_only_start_or_end_time_specified. Its documentation describes each rule: MobilityData validator rules.