forbidden_arrival_or_departure_time: GTFS validation rule (stop_times.txt) Error
A Flex stop_times row that targets a location_id or location_group_id sets arrival_time / departure_time. These columns are forbidden when the trip serves a zone or stop group instead of a fixed stop.
What the rule checks
A Flex stop_times row that targets a location_id or location_group_id sets arrival_time / departure_time. These columns are forbidden when the trip serves a zone or stop group instead of a fixed stop.
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 stop_times.txt. This file gives, for each trip, its stops in order with their times.
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 forbidden_arrival_or_departure_time 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, forbidden_arrival_or_departure_time. Its documentation describes each rule: MobilityData validator rules.
Rules of the same domain
- decreasing_or_equal_stop_sequence
- decreasing_or_equal_stop_time_distance
- decreasing_stop_time
- fast_travel_between_consecutive_stops
- fast_travel_between_far_stops
- forbidden_continuous_pickup_drop_off
- forbidden_drop_off_type
- forbidden_pickup_type
- forbidden_shape_dist_traveled
- invalid_pickup_drop_off_window
- invalid_time
- location_with_unexpected_stop_time
- All the validation rules