Relation: REM A4 - Deux-Montagnes<>Brossard (19792160): type=route_master
Relation REM A4 : Brossard → Deux-Montagnes (19669299): type=route
Relation REM A4 : Deux-Montagnes → Brossard (19668643): type=route
Relation: REM A2 -YUL-Aéroport-Montréal-Trudeau (19672326): type=route
Relation: REM A3: Anse-à-l’Orme <> Brossard (19792138): type=route_master
Relation: REM A3: Anse-à-l’Orme → Brossard (19668926): type=route
Relation: REM A3: Brossard → Anse-à-l’Orme (19672327): type=route
Relation: REM A2: YUL-Aéroport-Montréal-Trudeau → Brossard (19668927): type=route
Relation: REM A1 - Brossard (16141765): type=route_master
Relation: REM A1 : Montréal → Brossard (16139923): type=route
Relation: REM A1 : Brossard → Montréal (6170078): type=route
This does not represent reality, because there will never be an A2, A3 or A4 train to Brossard, and the A1 line shown only represents a small initial segment separate from the network. There are only REM trains : all trains heading to Brossard (regardless of what branch they start from) are A1, A4 trains will always go toward Deux-Montagnes, A2 trains toward A2 Airport and A3 trains toward Anse-à-l’Orme.
I propose we reorganize and rename these relations to reflect reality:
Relation: REM A1 - Brossard (16141765): type=route_master
Relation: REM A2: A1 - YUL-Aéroport-Montréal-Trudeau → Brossard (19668927): type=route
Relation: REM A3 A1: Anse-à-l’Orme → Brossard (19668926): type=route
Relation REM A4 A1 : Deux-Montagnes → Brossard (19668643): type=route
Relation: REM A2 - YUL-Aéroport-Montréal-Trudeau (19672326): type=route
Relation: REM A3 - : Brossard → Anse-à-l’Orme (19672327): type=route
Relation REM A4 - : Brossard → Deux-Montagnes (19669299): type=route
In this setup, I believe that these relations become redundant:
Relation: REM A1 : Montréal → Brossard (16139923): type=route*
Relation: REM A1 : Brossard → Montréal (6170078): type=route*
Relation: REM A4 - Deux-Montagnes<>Brossard (19792160): type=route_master
Relation: REM A3: Anse-à-l’Orme <> Brossard (19792138): type=route_master
*These two relations represented the introductory service of the REM from July 2023 to November 2025, but operationally the direction toward Montréal (Gare Centrale) was never labeled A1.
Does this relationship of routes and master routes make sense? Does it break something that I’m not aware of? I welcome all feedback.
Exact. Aucun trajet “express” comme font les lignes du Subway de New York. Tout train arrête à chaque station entre Brossard et Bois-Franc, et ensuite chaque station sur l’antenne qu’il emprunte.
Thanks for taking the initiative to untangle this REM confusion and attempting to map it to the OSM data model. I find it utterly confusing that they decided to deviate from the international standard of naming one line service in both directions with the same line reference number. This deviation makes it tricky to map it to the OSM public transport model.
In this established OSM public transport model a route_master relation links all variants of a line service. E.g. in a normal system "northbound and southbound subway routes of line 1”. Most of the time these are two routes, but some times there are line variants for shorter services or branches.
In the REM scenario it seems there are these three “line services” between terminus stations:
Brossard ↔ YUL-Aéroport-Montréal-Trudeau
Brossard ↔ Anse-à-l’Orme
Brossard ↔ Deux-Montagnes
Each of these I would suggest to represent in OSM with a route_master linking two route relations for each direction. (2/3 of this is what’s already mapped in OSM right now). The only problem with existing OSM metro validators now would be that each direction has a different reference number, but that’s a warning we have to ignore.
Let me know if this makes sense or you have more questions. I’m happy to help update OSM data accordingly if we agree on an approach.
Technically, the whole REM system constitutes line A, with the termini designated A1 (to the south), A2, A3 and A4 (to the north). In practice, the operator (almost) treats A1-, A2-, A3- and A4-bound services as wholly different lines in some public communications.
I have a proposal. Because it seems the GTFS data for the REM has the same challenge adapting these A1, A2, A3, A4 directions as we do in OSM.
They’ve given a route representing the equivalent of relation 16141765 a route_short_name of A4-A1. (There’s a second route currently, but it’s temporary while they bring the branch leading to A3 online.)