Diagnosis
What this notice means
Routes for the same agency and transport type share the same short-name and long-name combination.
Operational effect
Why it matters
Passengers may have difficulty choosing the intended route.
Scope
Files to check and report fields
| Report field | Type | Meaning |
|---|---|---|
agencyId | string | Common `routes.agency_id`. |
csvRowNumber1 | integer | The row number of the first occurrence. |
csvRowNumber2 | integer | The row number of the other occurrence. |
routeId1 | string | The id of the the first occurrence. |
routeId2 | string | The id of the the other occurrence. |
routeLongName | number | Common `routes.route_long_name`. |
routeShortName | string | Common `routes.route_short_name`. |
routeTypeValue | string | Common `routes.route_type`. |
Repair
How to fix it
- 1
Compare the reported routes with the operator's public route names.
- 2
Merge accidental duplicates and update trips, or use genuinely distinct public names. Opposite directions normally belong to one route. Keep legitimate identical names when the real services require them.
- 3Check the result
After a repair, rebuild the archive and validate it again. Confirm that the affected records are correct and that no new related notices appeared. A reviewed warning or informational notice may remain when it describes intentional, supported data.
Re-check your feed in the browserFree, no upload for a file you pick.
Sources