stops_match_shape_out_of_order: GTFS validation rule (shapes.txt) Warning
The stops of a trip, projected onto its shape polyline, are not in monotonic increasing order.
What the rule checks
The stops of a trip, projected onto its shape polyline, are not in monotonic increasing order.
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 shapes.txt. This file describes the geographic path of the trips, point by point.
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 stops_match_shape_out_of_order 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, stops_match_shape_out_of_order. Its documentation describes each rule: MobilityData validator rules.
Rules of the same domain
- decreasing_or_equal_shape_pt_sequence
- decreasing_shape_distance
- equal_shape_distance_diff_coordinates
- equal_shape_distance_diff_coordinates_distance_below_threshold
- equal_shape_distance_same_coordinates
- invalid_shape_lat
- invalid_shape_lon
- single_shape_point
- stop_has_too_many_matches_for_shape
- stop_too_far_from_shape
- stop_too_far_from_shape_using_user_distance
- trip_distance_exceeds_shape_distance
- All the validation rules