invalid_character: GTFS validation rule Error
A value holds a character that is no text, such as the replacement character U+FFFD: the file was probably not saved in UTF-8, the encoding GTFS requires.
What the rule checks
A value holds a character that is no text, such as the replacement character U+FFFD: the file was probably not saved in UTF-8, the encoding GTFS requires.
Severity: error
An error marks data that breaks the GTFS specification. A journey planner or a rider app may refuse the file, or show a wrong version of it. Correct it before publishing the GTFS.
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 invalid_character 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
invalid_character is the code of the MobilityData GTFS validator, the one its report carries. Its documentation describes the rule: invalid_character on the MobilityData site.