Diagnosis
What this notice means
The validator's window of substantial trip activity ends too soon.
Operational effect
Why it matters
A small amount of later service may remain while most passengers lose upcoming departures.
Scope
Files to check and report fields
calendar.txtOpen GTFS specificationcalendar_dates.txtOpen GTFS specificationfrequencies.txtOpen GTFS specificationtrips.txtOpen GTFS specification
| Report field | Type | Meaning |
|---|---|---|
currentDate | object | Current date (YYYYMMDD format). |
serviceWindowEndDate | object | The end date of the majority service window. |
serviceWindowStartDate | object | The start date of the majority service window. |
Repair
How to fix it
- 1
Compare the reported service window with the next confirmed timetable, including trips and both calendar files.
- 2
Publish the missing upcoming service and align feed metadata with it. Extending
feed_end_datealone does not extend trip coverage. - 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 — frequencies.txtOfficial GTFS documentation
- GTFS Schedule Reference — trips.txtOfficial GTFS documentation
- GTFS Scorecard fix guidePlain-language repair steps and checks