ERRORGTFS Schedule notice

A date is not a valid YYYYMMDD value

invalid_date
Severity
ERROR
Files to check
See report
Report fields
0
Documentation
Curated

Diagnosis

What this notice means

The field cannot be read as a real calendar date in GTFS format.

Operational effect

Why it matters

The service or feed validity period cannot be interpreted reliably.

Scope

Files to check and report fields

Use the file or input resource identified in the report. Check the message and available context fields; runtime failures may not identify a GTFS row.

Report fieldTypeMeaning
This notice has no structured context fields.

Repair

How to fix it

  1. 1

    Find the reported value and confirm its intended date.

  2. 2

    Use eight digits in year-month-day order, such as 20261005. Remove separators and check that the day exists in that month and year.

  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.

Worked example

Example correction

Assume the intended date is 5 October 2026.

Before

start_date: 2026-10-05

After

start_date: 20261005

Illustrative excerpt, not a complete GTFS feed. Keep all other required records and fields.

Sources

References