Diagnosis
What this notice means
A route allows continuous pickup or drop-off while one of its trips uses pickup/drop-off windows.
Operational effect
Why it matters
These settings combine incompatible ways of describing passenger access.
Scope
Files to check and report fields
routes.txtOpen GTFS specificationstop_times.txtOpen GTFS specificationtrips.txtOpen GTFS specification
| Report field | Type | Meaning |
|---|---|---|
endPickupDropOffWindow | object | The end time of the pickup/drop-off window. |
routeCsvRowNumber | integer | The row number of the route in the `routes.txt` file. |
startPickupDropOffWindow | object | The start time of the pickup/drop-off window. |
stopTimeCsvRowNumber | integer | The row number of the stop time in the `stop_times.txt` file. |
tripId | string | The ID of the trip. |
Repair
How to fix it
- 1
Inspect the reported route and stop-time rows.
- 2
For a window-based service, use route settings that do not declare continuous pickup/drop-off, as required by the specification. Otherwise remove incorrectly exported windows and model the actual service.
- 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