Guides to modify and validate a GTFS feed

Practical guides on the files and fields involved when a transit network changes.

• How to add a stop to a line in a GTFS feed

  Create the stop in stops.txt, insert its call in stop_times with the right sequence and consistent times in both directions, then check shape and validation.

• From a brief to a delivered GTFS feed

  What a good brief must say so a GTFS feed can be changed without guessing, how GTFS Express turns it into a change, and what to check before you deliver.

• Choosing a tool to modify a GTFS feed, the criteria that matter

  Criteria for choosing a GTFS editing tool (scope, proof, validation, versions, data, briefs, who decides) and how GTFS Express answers each of them.

• Making stop timetable sheets from a GTFS feed

  What a timetable posted at a stop must show, how GTFS gives it (day types, notes, periods, no boarding) and the pitfalls that make a sheet wrong.

• How to modify a GTFS feed without breaking it, step by step

  Which files a change touches, keeping ids stable, consistent calendars and stop_times, shapes, and validating the feed before you deliver a new version.

• School holidays and public holidays in a GTFS feed

  Write school periods, French holidays by zone A, B or C and public holidays with calendar.txt and calendar_dates.txt, and avoid the most common traps.

• Validate a GTFS feed with the MobilityData validator

  What the MobilityData GTFS validator checks, its three severities, how to read its report, the typical errors, and when to fix a notice or accept it.