unexpected_enum_value: GTFS validation rule Warning
A field that takes one of a list of values holds a number outside the list the validator knows, for example an extended route_type such as 700 in routes.txt. The value may be valid for the tools that…
What the rule checks
A field that takes one of a list of values holds a number outside the list the validator knows, for example an extended route_type such as 700 in routes.txt. The value may be valid for the tools that read it.
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 checks the format of a value: it applies to every field of that type, in any GTFS file that has one.
Finding and correcting it
Open the GTFS in GTFS Express. Reading is free, and the validation, by the MobilityData validator, lists the occurrences of unexpected_enum_value 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
unexpected_enum_value is the code of the MobilityData GTFS validator, the one its report carries. Its documentation describes the rule: unexpected_enum_value on the MobilityData site.