Diagnosis
What this notice means
A trip and route named on the same side of a transfer disagree with trips.route_id.
Operational effect
Why it matters
The transfer rule's conditions do not describe the intended journey consistently.
Scope
Files to check and report fields
| Report field | Type | Meaning |
|---|---|---|
csvRowNumber | integer | The row number from `transfers.txt` for the faulty entry. |
expectedRouteId | string | The expected route id from `trips.txt`. |
routeFieldName | string | The name of the route id field (e.g. `from_route_id`) referencing the route. |
routeId | string | The referenced route id. |
tripFieldName | string | The name of the trip id field (e.g. `from_trip_id`) referencing a trip. |
tripId | string | The referenced trip id. |
Repair
How to fix it
- 1
Compare the reported
tripId,routeId, andexpectedRouteIdintransfers.txtandtrips.txt. - 2
Correct the mistaken trip or route reference. Change the trip's route only if that assignment itself is wrong.
- 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