Diagnosis
What this notice means
The fields named by the report have equal values where this check expects a nonzero interval.
Operational effect
Why it matters
A zero-length frequency interval does not describe a usable period of departures.
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. |
entityId | string | The id of the faulty entity. |
filename | string | The name of the faulty file. |
startFieldName | string | The start value's field name. |
value | object | The faulty value. |
Repair
How to fix it
- 1
Check
filename,startFieldName, andendFieldName; forfrequencies.txt, these arestart_timeandend_time. - 2
Supply the actual interval with an end after its start. If the intention is one departure, model a scheduled trip instead. Do not treat every one-day calendar as invalid.
- 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