route_type_invalid: GTFS validation rule (routes.txt) Warning
route_type is not in the GTFS spec's enum (0-12 plus extended 100-1799 hierarchical types).
What the rule checks
route_type is not in the GTFS spec's enum (0-12 plus extended 100-1799 hierarchical types).
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 routes.txt. This file describes the routes: their names, transport mode and colours.
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 route_type_invalid 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, route_type_invalid. Its documentation describes each rule: MobilityData validator rules.