← All agencies

Feed status · checked 2026-09-05

Transcollines (Régie intermunicipale de transport des Collines)

Based on the official feed source on file

Service mode Bus

FDCBA

81.6 / 100

First scorecard for this agency

Catalogued in Quebec, Canada.

Covers 86 daysAccessibility gapsRealtime not yet published

The schedule export named on the operator's open data page. The same repository also carries a Fares v2 file and a Cityway variant of the same network, which are not listed separately.

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.

Measured 3 of 4 score categories from the official feed URL on file.

How we measured this

Confidence in this measurement: medium.

Realtime quality was not measured this run. It does not count against the grade.
The feed was downloaded from the official feed URL on file.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team

425 of 425 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 02

Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Fix 03

Remove past service periods the next time you export the feed.Likely your export tool

Some service calendars in the feed have already ended. Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

⏱ One setting in most export tools.worth about +4 points in its category

This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence: 425 of 425 stops don't say whether a wheelchair user can board there.
Next action: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.

Copy handoff text

Agency: Transcollines (Régie intermunicipale de transport des Collines)
Finding: scorecard_wheelchair_boarding_unknown
Feed evidence: 425 of 425 stops don't say whether a wheelchair user can board there.
Why it matters: Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Requested change: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Evidence: https://gtfsscorecard.org/agency/transcollines/?finding=scorecard_wheelchair_boarding_unknown#finding-handoff

How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. · Read the fix guide
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Remove past service periods the next time you export the feed. · Read the fix guide
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility: The feed's last published service date is in 86 days.
Published accessibility data: Accessibility information is stated for 0% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information: No fare information is published in the feed.
Realtime information: Realtime-feed availability and live-arrival coverage are not known from this scorecard.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

This feed is published from a code repository. Forward this to whoever maintains that repository; the fix happens in the source data, then a fresh export is committed. Each fix names the validator notice and a guide link.

Hi,

Our GTFS feed (Transcollines (Régie intermunicipale de transport des Collines)) scored B (81.6 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 425 of 425 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

2. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
   What: The feed contains no fare information.
   Finding code: scorecard_no_fare_data
   Guide: https://gtfsscorecard.org/fix/scorecard_no_fare_data/

3. Remove past service periods the next time you export the feed.
   What: Some service calendars in the feed have already ended.
   Finding code: expired_calendar
   Guide: https://gtfsscorecard.org/fix/expired_calendar/

Full scorecard: https://gtfsscorecard.org/agency/transcollines/

Score by category

Correctness86.5 / 100

The MobilityData validator flagged 6 kinds of issue across 13 instances (0 error, 6 warning, 7 informational).

Freshness100.0 / 100

Service data covers the next 86 days.

Rider experience60.0 / 100

0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility37.5 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 425 stops.

The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

910 (blue)
921 (blue)
923 (blue)
924 (blue)
925 (blue)
931 (blue)
932 (blue)
940 (blue)

Routes in Transcollines (Régie intermunicipale de transport des Collines)'s feed
Route	Type	Line color
910 Pontiac — Gatineau	Bus	blue
921 La Pêche — Chelsea — Gatineau	Bus	blue
923 La Pêche — Chelsea — Gatineau	Bus	blue
924 La Pêche — Chelsea — Gatineau	Bus	blue
925 La Pêche — Chelsea — Gatineau	Bus	blue
931 Cantley — Gatineau	Bus	blue
932 Cantley — Gatineau	Bus	blue
940 Val-des-Monts — Gatineau	Bus	blue

List every stop

Route 148 | de la Montagne
Route 148 | de la Montagne
Route 148 | de la Rivière
Route 148 | Smith-Léonard
Route 148 | Breckenridge
Route 148 | Breckenridge
Route 148 | Elm
Route 148 | Elm
Route 148 | des Lilas
Route 148 | des Lilas
Route 148 | Fortin
Route 148 | du Marquis
Route 148 | Terry-Fox
Route 148 | Terry-Fox
Route 148 | de l'Hôtel-de-Ville
Route 148 | Kennedy
Route 148 | Eardley-Masham
Route 148 | Eardley-Masham
Route 148 | Parker
Route 148 | Parker
Route 148 | Alary
Route 148 | Pilon
Route 148 | Lebrun
Route 148 | Lebrun
Route 148 | du Village
Route 148 | du Village
Route 148 | de l'Hôtel-de-Ville
Route 148 | Kennedy
Route 148 | Tremblay
Route 148 | Crégheur
Route 148 | Gold Mine Sud
Route 148 | Gold Mine Nord
Route 148 | de Clarendon
Route 148 | MacKechnie
Route 148 | Stanton
Route 148 | Stanton
de Clarendon | Ferry
de Clarendon | Ferry
Route 148 | Russell
Route 148 | Russell
Route 148 | Concesssion 5e
Route 148 | Concession 5e
Route 148 | Wilson
Route 148 | Wilson
Route 148 | de Bristol
Route 148 | Ragged Chute
Route 148 | Wharf
Route 148 | Wharf
Route 148 | Bristol Mines
Route 148 | Bristol Mines
Route 148 | Knox
Route 148 | Knox
Route 148 | d'Aylmer
Route 148 | de Wyman
Route 148 | Route 303
Route 148 | Route 303
Route 148 | de Sand Bay
Route 148 | Rectory
Centre | Marion
Centre | Marion
Route 148 | de Bristol-Clarendon Sud
Route 148 | Stewart
Route 148 | Stewart
Route 148 | Telford
Route 148 | Telford
Route 148 | Homer
Route 148 | Homer
Route 148 | Radford
Route 148 | Radford
Route 148 | Zion
Route 148 | Zion
Route 148 | de Calumet Est
Route 148 | de Calumet Est
Route 148 | de Bristol-Clarendon Sud
Route 148 | 7th Line
Route 148 | 7th Line
Route 148 | Principale
Route 148 | Principale
Route 148 | Route 301
Route 148 | Front
Route 148 | Front
Route 148 | Hayes
Route 148 | Hayes
Route 148 | de Morehead
Route 148 | de Morehead
Route 148 | de la Rivière
Route 148 | de la Rivière
Route 148 | Wilson
Route 148 | Wilson
Route 148 | Kelly
Route 148 | Stitt
Route 148 | Romain
Route 148 | Romain
Route 148 | Eight
Route 148 | Eight
Route 148 | Murtagh
Route 148 | Murtagh
Route 148 | Hearty
Route 148 | Hearty
Route 148 | de la Montagne
Route 148 | de la Montagne
Route 148 | Laforest
Route 148 | Laforest
Route 148 | de la Chute
Route 148 | du Devonshire
Route 148 | Thomas-Lefebvre Nord
Route 148 | Thomas-Lefebvre Nord
Route 148 | du Lac-de-la-Truite
Route 148 | du Lac-de-la-Truite
Route 148 | Thomas-Lefebvre Sud
Route 148 | Thomas-Lefebvre Sud
Route 148 | Dagenais
Route 148 | Dagenais
Route 148 | du Devonshire
Route 148 | de la Chute
Route 148 | Graveline
Route 148 | Graveline
de Chapeau-Waltham | Donlan
de Chapeau-Waltham | Donlan
de Chapeau-Waltham | Leslie
de Chapeau-Waltham | Leslie
de Chapeau-Waltham | Campeau
de Chapeau-Waltham | Campeau
de Chapeau-Waltham | Kelly
de Chapeau-Waltham | Kelly
de Chapeau-Waltham | De Souza
de Chapeau-Waltham | Rochon
Route 148 | de Chapeau-Waltham
Route 148 | de Chapeau-Waltham
Route 148 | Romain
Route 148 | Romain
Route 148 | Robinson
Route 148 | Robinson
Route 148 | de la Rivière-Noire
Route 148 | de la Rivière-Noire
de Pembroke | Notre-Dame
de Pembroke | Notre-Dame
de Pembroke | de Chapeau-Waltham
de Chapeau-Waltham | de Pembroke
de Chapeau-Waltham | Dirty-Dozen
de Chapeau-Waltham | Dirty-Dozen
de Chapeau-Waltham | McGuire
de Chapeau-Waltham | McGuire
Principale | Passe-Partout
Principale Eest | Gosselin
Principale Est | Gosselin
Principale Est | de la Beurrerie
Principale Est | Kennedy
Principale Est | Richard
Principale Est | Vaillant
Principale Est | Brisebois
Principale Est | Kennedy
Principale Est | de la Prairie
Principale Est | Charlevoix
Principale Est | Charlevoix
Principale Est | Murray
Principale Est | Murray
Principale Est | Philippe
Principale Est | de la Prairie
Principale Est | de la Beurrerie
Centre Communautaire Wakefield
de la Vallée-de-Wakefield | Riverside
Riverside | École Wakefield
Stationnement Incitatif de la Locomotive
Riverside | de la Légion
Riverside | Burnside
Riverside | Burnside
Riverside | Mill
Près du 740 chemin Riverside
Riverside | de la Vallée-de-Wakefield
de Ste-Cécile-de-Masham | Stationnement P17
de Ste-Cécile-de-Masham | Stationnement P17
Route 105 | Place des Collines
Route 105 | Place des Collines
Route 105 | Valle Verde
Route 105 | du Progrès
Riverside | MacLaren
Riverside | Gendron
Riverside | Gendron
Riverside | MacLaren
Riverside | Elmdale
IGA - Chelsea
Près du 1638 route 105
Près du 1638 route 105
Route 105 | Léa
Route 105 | Carman
Route 105 | St-Clément
Route 105 | Hammond
Route 105 | Hammond
Route 105 | Croissant
Route 105 | St-Clément
Route 105 | Carman
Route 105 | Croissant
IGA - Chelsea (coté Est)
Route 105 | Pine
Route 105 | de la Rivière
Route 105 | Thomas
Route 105 | Burnett
Route 105 | Ditchfield
Route 105 | Radapaw
Route 105 | Maple Woods
Route 105 | Epps
Route 105 | Old Sawmill
Route 105 | Ditchfield
Route 105 | Burnett
Route 105 | Thomas
Route 105 | de la Rivière
Route 105 | de la Rivière
Route 105 | Pine
Route 105 | Juniper
Route 105 | Reid
Route 105 | Montrose
Route 105 | Montrose
Route 105 | Juniper
Route 105 | Sherrin
Route 105 | Reid
Route 105 | Ojai
Route 105 | Musie
Route 105 | Forest Hill
Route 105 | Doucette-Landing
Route 105 | Doucette-Landing
Route 105 | Forest Hill
Route 105 | Williamson
Route 105 | Ojai
Route 105 | Craiglands
Route 105 | Wilson
Route 105 | Sherrin
Scott | Old Chelsea
Stationnement Incitatif Old Chelsea
Église St-Stephen's
Scott | Preston
Scott | Old Chelsea
Scott | Preston
Old Chelsea | Boischatel
Old Chelsea | Boisjoli
Route 105 | Hudson
Route 105 | Hudson
Accueil CCN (Centre des visiteurs)
Old Chelsea | Boisjoli
Old Chelsea | du Relais
Old Chelsea | de l'Hôtel de Ville
Old Chelsea | Ladyfield
Old Chelsea | Jean-Paul-Lemieux
Old Chelsea | Boischatel
Old Chelsea | du Relais
Old Chelsea | Lonergan
Old Chelsea | Douglas
Old Chelsea | Ladyfield
Scott | de la Belle-Terre
Scott | de la Belle-Terre
and 175 more (see the full list on the map or in the GeoJSON)

Over time

This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.

Everything we checked

8 findings, ordered by severity.

Show every finding

Warning425 instances
425 of 425 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning2 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning2 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning2 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Info4 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info2 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Conformance mark Not yet

One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.

Valid Met: Passes validation with no errors.
Current Met: Service data covers the next 86 days.
Accessible Not yet: States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Clears the Google and Apple Maps four-week coverage bar. This feed has 86 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.

Correctness 86 / 100: GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
Freshness 100 / 100: GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
Rider experience 60 / 100: GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published: GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

[![Transcollines (Régie intermunicipale de transport des Collines) GTFS data quality grade: B](https://gtfsscorecard.org/data/artifacts/transcollines/badge.svg)](https://gtfsscorecard.org/agency/transcollines/)

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/transcollines/2026-09-05.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-09-05. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

GTFS Scorecard. (2026). Transcollines (Régie intermunicipale de transport des Collines) GTFS feed-quality record, dated 2026-09-05 (grade B (81.6/100), rubric v1.3, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 f97bb7697d14…). https://gtfsscorecard.org/data/artifacts/transcollines/2026-09-05.json

@misc{gtfsscorecard-transcollines-2026-09-05,
  title        = {Transcollines (Régie intermunicipale de transport des Collines) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/transcollines/2026-09-05.json}},
  note         = {Checked 2026-09-05; rubric v1.3; gtfs-validator 8.0.1; reader archive profile raw-v1; grade B (81.6/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.