Feed status · checked 2026-07-19
VIA Rail Canada
Based on the feed this agency publishes
Service mode Rail + Bus
First scorecard for this agency
Catalogued in Canada.
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.2, validator 8.0.1.
Checked for changes 8 hours ago; last changed 8 hours ago.
Measured 3 of 4 score categories from the agency's own feed.
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 agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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
332 of 388 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 +21 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
85 of 85 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
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
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. Make this change in whatever tool produces your feed, then re-export.
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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
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. Make this change in whatever tool produces your feed, then re-export.
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 111 days.
- Published accessibility data
- Accessibility information is stated for 14.4% of stops and 0% 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
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 7 kinds of issue across 167 instances (0 error, 4 warning, 163 informational).
Service data covers the next 111 days.
14% of stops state wheelchair accessibility (14% marked accessible, 1% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
14% of stops state accessibility (14% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
4 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("St. Catharines", "St. Marys", "Sudbury Jct", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
- VIA Rail (yellow)
| Route | Type | Line color |
|---|---|---|
| VIA Rail Toronto - New York | Rail | yellow |
| VIA Rail Toronto - Sarnia | Rail | yellow |
| VIA Rail Toronto - Windsor | Rail | yellow |
| VIA Rail Toronto - London | Rail | yellow |
| VIA Rail The Pas - Churchill | Rail | yellow |
| VIA Rail Jasper - Prince Rupert | Rail | yellow |
| VIA Rail Montréal - Toronto | Rail | yellow |
| VIA Rail Montréal - Jonquière | Rail | yellow |
| VIA Rail Montréal - Senneterre | Rail | yellow |
| VIA Rail Montréal - Halifax | Rail | yellow |
| VIA Rail Winnipeg - Churchill | Rail | yellow |
| VIA Rail Ottawa - Toronto | Rail | yellow |
| VIA Rail Ottawa - Montréal | Rail | yellow |
| VIA Rail Ottawa - Québec | Rail | yellow |
| VIA Rail Sudbury - White River | Rail | yellow |
| VIA Rail Québec - Montréal | Rail | yellow |
| VIA Rail Québec - Fallowfield | Rail | yellow |
| VIA Rail Vancouver - Toronto | Rail | yellow |
| VIA Rail Air Connect | Bus | yellow |
This feed has 388 stops.
List every stop
- Grimsby
- Truro
- Kamsack
- Mud River
- Auden
- Ferland
- Gladstone
- Collins
- Armstrong
- Flindt Landing
- Savant Lake
- Allanwater Bridge
- St. Marys
- Matapédia
- Red Lake Road
- Capreol
- Kitchener
- Richan
- White River
- Kamloops North
- Saskatoon
- Toronto
- Moncton
- New York
- Club Sommet
- Signai
- Garneau
- Franz
- Woman River
- Forsythe
- Saint-Paulin
- Canyon
- Grand-Mère
- Hirondelle
- Goat River
- La Pocatière
- Gillam
- Strathroy
- Farlane
- Glenella
- Minaki
- Redditt
- Abbotsford
- Cressman
- Houston
- The Pas
- Biscotasing
- Halcrow
- Ottermere
- Tremaudan
- Bridgar
- Hockin
- Endeavour
- Club Kapitachuan
- Kiskisink
- Brantford
- Gagnon
- Kormak
- Leven
- Stadacona
- Malachi
- Wigwam
- Grandview
- Trois Pistoles
- McTavish
- Dorreen
- Amsterdam
- Kwinitsa
- Kondiaronk
- Cobourg
- La Perouse
- Jacquet River
- Coquar
- Club Maniwawa
- Lac Édouard
- Larchwood
- St. Catharines
- Copelands Landing
- Albany
- Rogersville
- Club Beaudin
- Rochester
- Levack
- Bourmont
- Cedarvale
- Herchmer
- Rice Lake
- Benny
- Chelmsford
- Gananoque
- Buffalo (Exchange)
- Sackville
- Lac Darey
- Brereton Lake
- Chapleau
- Elma
- McBride
- Wekusko
- Club Jacques-Cartier
- Jasper
- Croton-Harmon
- McCarthy
- Girdwood
- Manjobagues
- Casey
- Club Triton
- Metagama
- Amherst
- Azilda
- Amqui
- Rhinecliff
- Portage la Prairie
- Montréal
- New Hazelton
- Watrous
- Chesnaye
- Nemegos
- Unity
- Button
- Munk
- Wainwright
- Nonsuch
- Atikameg Lake
- Sturgis
- Poughkeepsie
- Evansburg
- Aleza Lake
- Brooks
- Rawebb
- Van Bruyssels
- Pogamasing
- Pit Siding
- Schenectady
- Caribou
- Paterson
- Monet
- Edson
- Lac-aux-Perles
- Pacific
- Valemount
- Rome
- Miquick
- Hudson
- Reserve
- Ponton
- Hinton
- Winnitoba
- Ramsey
- Sultan
- Miramichi
- Blue River
- Ashcroft
- Falrie
- Usk
- Boston Bar
- Hope
- Rivière Oskélanéo
- Chilliwack
- Amery
- Rousseau
- Wyoming
- Sinclair Mills
- Woodstock
- Tidal
- Katz
- Strachan
- Sheahan
- North Bend
- Dauphin
- Earchman
- Sipiwesk
- Timbrell
- O'Brien
- Telkwa
- Saint-Maurice Rivière Boom
- Agassiz
- Thibaudeau
- Mission Harbour
- Windigo
- Veregin
- Oskelaneo Lodge
- Upper Fraser
- Sanmaur
- Smithers
- Willow River
- Napanee
- Terrace
- Bathurst
- Cartier
- Thicket Portage
- Pipun
- Roberts
- Plumas
- Boyd
- Club Iroquois
- Club Sisco
- Rapide Blanc
- Cann
- Brampton
- Ingersoll
- Bolkow
- Budd
- Rivière-du-Loup
- Rimouski
- Stralak
- Bima
- Dorval
- Penny
- Weir River
- Burns Lake
- Vandry
- Malton
- Wivenhoe
- Sarnia
- Mont-Joli
- Saint-Lambert
- Alexandria
- Yonkers
- Niagara Falls
- Ochre River
- Orok
- Brockville
- Rivière-à-Pierre
- Coteau
- O'Day
- Odhill
- Campbellton
- Arnot
- Buffalo (Depew)
- Vanderhoof
- Nicholson
- Bend
- Utica
- Oshawa
- Bolger
- Pont Beaudet
- Mikado
- Lyddal
- Pikwitonei
- M'Clintock
- Missanabie
- Smiths Falls
- Longworth
- McGregor
- Saint-Tite
- McCreary
- Megiscane
- Luke
- Club Rita
- Loos
- and 138 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
10 findings, ordered by severity.
Show every finding
- Warning332 instances
332 of 388 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning85 instances
85 of 85 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning3 instances
Missing timepoint value (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_timepoint_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Validator rule: missing_recommended_field · 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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info83 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info74 instances
Service extends far in the future (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: service_extends_far_in_the_future · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 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.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 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.)
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the transit vehicle ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 14% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 111 days.
- Accessible Not yet
- States wheelchair access on 14% of stops and 0% 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 1626 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 88 / 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 49 / 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.
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/via-rail-canada/2026-07-19.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-07-19. 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.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.