Diagnosis
What this notice means
Rows in timeframes.txt with the same timeframe_group_id and service_id cover overlapping times.
Operational effect
Why it matters
The fare calendar contains overlapping definitions for the same group.
Scope
Files to check and report fields
| Report field | Type | Meaning |
|---|---|---|
currCsvRowNumber | integer | The row number of the second timeframe entry. |
currStartTime | string | The start time of the second timeframe entry. |
prevCsvRowNumber | integer | The row number of the first timeframe entry. |
prevEndTime | string | The first timeframe end time. |
serviceId | string | The service id associated with the two entries. |
timeframeGroupId | string | The timeframe group id associated with the two entries. |
Repair
How to fix it
- 1
Compare the reported current and previous rows and their boundary times.
- 2
Merge redundant intervals or adjust them to the real fare periods. An interval may end exactly when the next begins, because the end boundary is excluded.
- 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.
Worked example
Example correction
Assume the second fare period really begins at 09:00. Adjacent periods may share that boundary.
Before
timeframe_group_id,start_time,end_time,service_id
G1,07:00:00,09:00:00,WKDY
G1,08:30:00,10:00:00,WKDYAfter
timeframe_group_id,start_time,end_time,service_id
G1,07:00:00,09:00:00,WKDY
G1,09:00:00,10:00:00,WKDYIllustrative excerpt, not a complete GTFS feed. Keep all other required records and fields.
Sources