INFOGTFS Schedule notice

A service has a gap of at least 14 days

big_gap_in_service
Severity
INFO
Files to check
2
Report fields
4
Documentation
Curated

Diagnosis

What this notice means

The calendar for the reported serviceId has a long break between active dates.

Operational effect

Why it matters

This may be an intentional seasonal break or a missing part of the timetable.

Scope

Files to check and report fields

Report fieldTypeMeaning
gapDurationDaysnumberThe number of days in the gap.
gapEndDatestringThe last day of the gap.
gapStartDatestringThe first day of the gap.
serviceIdstringThe service_id that has the gap.

Repair

How to fix it

  1. 1

    Check the reported gap against calendar.txt and the added or removed dates in calendar_dates.txt.

  2. 2

    Restore missing service dates if the service should run. Keep an intentional break; do not add departures that are not operated.

  3. 3
    Check 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