unsorted_stop_times: GTFS validation rule (stop_times.txt) Info
The rows of a trip in stop_times.txt are not in the order of stop_sequence, or do not follow one another in the file.
What the rule checks
The rows of a trip in stop_times.txt are not in the order of stop_sequence, or do not follow one another in the file.
Severity: information
An information notice marks a feature of the GTFS that does not affect its conformity. It helps to understand the data and asks for no correction.
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, lists the occurrences of unsorted_stop_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
unsorted_stop_times is the code of the MobilityData GTFS validator, the one its report carries. Its documentation describes the rule: unsorted_stop_times on the MobilityData site.
Rules of the same domain
- decreasing_or_equal_stop_time_distance
- 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_geography_id
- forbidden_pickup_type
- forbidden_shape_dist_traveled
- invalid_pickup_drop_off_window
- invalid_time
- location_with_unexpected_stop_time
- All the validation rules