route_both_short_and_long_name_missing: GTFS validation rule (routes.txt) Error
Neither route_short_name nor route_long_name is provided: at least one is required.
What the rule checks
Neither route_short_name nor route_long_name is provided: at least one is required.
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 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_both_short_and_long_name_missing 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_both_short_and_long_name_missing. Its documentation describes each rule: MobilityData validator rules.