Release note for the new GTFS

GTFS bêta 26M – Coming into production on June 15, 2026

This page lists the details to our GTFS schedule adjustments, which we plan to release to production for our next scheduling period, on June 15, 2026. For any questions or comments, please reach out to: dev@stm.info

Download the beta version of March schedules

New « directions.txt » file detailing directions by route

Field

Description

Example values

route_direction_id

A unique key identifying a route-direction ID combination

100_0
200_1
…

route_id

Route ID

Field referenced in the routes.txt file

100
200
…

direction_id

Route-direction ID

Field referenced in the trips.txt & route_patterns.txt files

0
1

direction

Route-direction text

This value is either a cardinal direction or a "public" direction when specified.

North
South
East
West

Nord sur St-Jean et sud sur St-Charles

Est - Vers le centre-ville de Montréal

…

direction_legacy

Direction code for compatibility with linked systems

NORTH
SOUTH
EAST
WEST

New « route_patterns.txt » file detailing typical route-pattern per route

Field

Description

Example values

route_pattern_id

A unique key identifying a typical route-pattern

Field referenced in the trips.txt & shapes.txt files

1_1071
44_1
…

route_id

Route ID

Field referenced in the routes.txt file

1
44
…

direction_id

Route direction ID

Field referenced in the trips.txt & directions.txt files

0
1

route_pattern_typicality

Main route-pattern identifier for route-direction type (1 = main route-pattern)

0
1

Adjustments to the TRIPS.TXT file

  • note field has been removed from the file in order to only maintain trip_headsign field which inform about the trip’s destination.
  • trip_headsign field, which relates to route directions, will now display “public” route directions
  • Route-pattern identifier added to TRIPS.TXT file (route_pattern_id field)
  • New format of shape_id key, so it is consistent with route_pattern_ID

Adjustments to the SHAPES.TXT file

  • Addition of route_pattern_id as the route-pattern identifier
  • New format of shape_id key, so it is consistent with route_pattern_ID

Adjustments to the ROUTES.txt file

  • Addition of the route_desc field, that includes the route description code, where applicable
  • Addition of the route_desc_detail field, that includes the route_desc detailed description

Adjustments to the TRANSLATIONS.txt file

  • note entries have been removed
  • trip_headsign entries of the trips section are maintained and related to the trip’s destination translation (trip_headsign) that are in the TRIPS.TXT file.
  • Addition of a direction entry to the directions section
  • Addition of a route_desc entry to the routes section
  • Addition of a route_desc_detail entry to the routes section
Top of page