feed_expired: GTFS validation rule (data quality) Warning
The feed-level end_date is in the past.
What the rule checks
The feed-level end_date is in the past.
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 measures the quality of the data rather than strict conformity: it points at values that are allowed but unlikely.
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 feed_expired 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, feed_expired. Its documentation describes each rule: MobilityData validator rules.
Rules of the same domain
- feed_expiration_date_30_days
- feed_expiration_date_7_days
- missing_recommended_field
- mixed_case_recommended_field
- non_ascii_or_non_printable_char
- point_near_origin
- point_near_pole
- route_without_trips
- start_and_end_range_equal
- stop_time_travel_distance_too_long
- stop_time_travel_speed_too_fast
- All the validation rules