invalid_input_files_in_subfolder: GTFS validation rule (archive structure) Error
At least one GTFS file sits in a subfolder of the archive. The files must be at its root: zip the files themselves, not the folder that holds them.
What the rule checks
At least one GTFS file sits in a subfolder of the archive. The files must be at its root: zip the files themselves, not the folder that holds them.
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 applies to the structure of the GTFS archive: the files it holds, their headers, their encoding and the shape of their rows.
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_input_files_in_subfolder 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_input_files_in_subfolder is the code of the MobilityData GTFS validator, the one its report carries. Its documentation describes the rule: invalid_input_files_in_subfolder on the MobilityData site.