MétaCan
Menu
Back to cohort
Record W7083590338 · doi:10.1016/j.jpubtr.2025.100139

Measuring the operational impacts of a new Bus Rapid Transit (BRT) in Montreal, Canada

2025· article· en· W7083590338 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
fundA Canadian funder is recorded on the work.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueJournal of Public Transportation · 2025
Typearticle
Languageen
FieldComputer Science
TopicGeochemistry and Geologic Mapping
Canadian institutionsMcGill University
FundersSocial Sciences and Humanities Research Council of CanadaNatural Sciences and Engineering Research Council of CanadaFonds de Recherche du Québec-Société et Culture
KeywordsBus rapid transitHeadwayScheduleTravel timeTransit (satellite)Service (business)Public transportKey (lock)Taxis

Abstract

fetched live from OpenAlex

Recent research on Bus Rapid Transit (BRT) systems has mostly focused on ridership forecasting and scheduled travel time gains, with little empirical evidence on potential operational improvements. This study examines the short-term impacts of implementing a new BRT corridor in Montreal, Canada, on key bus performance indicators: running time, running time deviation, and headway deviation. Using Automatic Vehicle Location (AVL) and Automated Passenger Count (APC) data from 2022 to 2023, we compare the performance of the BRT to a parallel local bus route operating along the same corridor, before and after the BRT implementation. Our findings indicate that the BRT significantly reduced trip durations (about four minutes on average) primarily due to infrastructure features such as dedicated lanes and all-door boarding policy. The local route experienced modest running time improvements post-BRT, suggesting potential corridor-wide benefits. However, run time deviation was significantly higher for the BRT, particularly during peak periods while headway deviation worsened along the corridor compared to pre-BRT conditions. These findings highlight the importance of integrating infrastructure investments with dynamic operational strategies such as real-time dispatching and headway control. It emphasizes the need for schedule calibration following implementation to ensure that planned service aligns with actual performance. These findings offer practical insights for transit agencies planning or managing BRT systems.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.684
Threshold uncertainty score0.932

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.021
GPT teacher head0.212
Teacher spread0.192 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it