missing_pickup_drop_off_booking_rule_id: GTFS validation rule (stop_times.txt) Warning
A stop_times row uses pickup_type=2 or drop_off_type=2 (must phone agency) but does not reference a pickup_booking_rule_id / drop_off_booking_rule_id.
What the rule checks
A stop_times row uses pickup_type=2 or drop_off_type=2 (must phone agency) but does not reference a pickup_booking_rule_id / drop_off_booking_rule_id.
Severity: warning
A warning marks data the specification allows but that looks doubtful, or recommended information that is missing. The GTFS can still be published, but riders may see the effect, so each case deserves a look.
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 missing_pickup_drop_off_booking_rule_id 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, missing_pickup_drop_off_booking_rule_id. 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_arrival_or_departure_time
- forbidden_continuous_pickup_drop_off
- forbidden_drop_off_type
- forbidden_pickup_type
- forbidden_shape_dist_traveled
- invalid_pickup_drop_off_window
- invalid_time
- All the validation rules