Diagnosis
What this notice means
The reported end date or time precedes its start.
Operational effect
Why it matters
The period or stop-time event cannot be interpreted in the intended order.
Scope
Files to check and report fields
Use the file or input resource identified in the report. Check the message and available context fields; runtime failures may not identify a GTFS row.
| Report field | Type | Meaning |
|---|---|---|
csvRowNumber | integer | The row number of the faulty record. |
endFieldName | string | The end value's field name. |
endValue | string | The end value. |
entityId | string | The faulty service id. |
filename | string | The name of the faulty file. |
startFieldName | string | The start value's field name. |
startValue | string | The start value. |
Repair
How to fix it
- 1
Compare
startFieldName,startValue,endFieldName, andendValuewith the source timetable. - 2
Correct the mistaken boundary. For overnight stop times within one service day, use hours above 24 where allowed instead of resetting the clock to zero.
- 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