Diagnosis
What this notice means
A service begins before feed_start_date or ends after feed_end_date.
Operational effect
Why it matters
The timetable and its validity metadata disagree, which may affect availability in apps.
Scope
Files to check and report fields
feed_info.txtOpen GTFS specificationcalendar.txtOpen GTFS specificationcalendar_dates.txtOpen GTFS specification
| Report field | Type | Meaning |
|---|---|---|
daysAfterFeedEnd | object | Number of days the service window extends after feed_end_date (0 if none). |
daysBeforeFeedStart | object | Number of days the service window extends before feed_start_date (0 if none). |
serviceId | string | The service_id whose active window extends outside the feed validity period. |
serviceWindowEndDate | string | The last active date of the service window. |
serviceWindowStartDate | string | The first active date of the service window. |
Repair
How to fix it
- 1
Compare the reported service window with both calendar files and
feed_info.txt. - 2
Extend the declared period if the included service is confirmed, or trim an unintended calendar range. Keep feed dates and actual timetable coverage consistent.
- 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
References
- MobilityData validator ruleCanonical notice metadata and rule details
- GTFS Schedule Reference — calendar.txtOfficial GTFS documentation
- GTFS Schedule Reference — calendar_dates.txtOfficial GTFS documentation
- GTFS Schedule Reference — feed_info.txtOfficial GTFS documentation
- GTFS Scorecard fix guidePlain-language repair steps and checks