Diagnosis
What this notice means
Two frequencies.txt intervals for the same trip cover some of the same time.
Operational effect
Why it matters
Apps may generate duplicate or contradictory departures during the overlap.
Scope
Files to check and report fields
| Report field | Type | Meaning |
|---|---|---|
currCsvRowNumber | integer | The overlapping frequency's row number. |
currStartTime | object | The overlapping frequency's start time. |
prevCsvRowNumber | integer | The row number of the first frequency. |
prevEndTime | object | The first frequency end time. |
tripId | string | The trip id associated to the first frequency. |
Repair
How to fix it
- 1
Compare the reported rows'
start_time,end_time, and headways. - 2
Merge equivalent intervals or adjust their boundaries to match the real service. Adjacent intervals can share a boundary where one ends and the next starts.
- 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