Diagnosis
What this notice means
A timed trip's first or last stop lacks arrival_time or departure_time.
Operational effect
Why it matters
Apps cannot reliably determine when the trip starts or ends.
Scope
Files to check and report fields
| Report field | Type | Meaning |
|---|---|---|
csvRowNumber | integer | The row of the faulty record. |
specifiedField | string | Name of the missing field. |
stopSequence | integer | `stops.stop_sequence` of the faulty record. |
tripId | string | The `trips.trip_id` of the faulty record. |
Repair
How to fix it
- 1
Find the reported trip and sort its
stop_times.txtrows bystop_sequence. - 2
Supply both times at the affected boundary from the timetable. When arrival and departure are the same event, use the same value for both; preserve hours above 24 for overnight 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