Feed status · checked 2026-09-05
Thunder Bay Transit
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Ontario, 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.3, validator 8.0.1.
Checked for changes 1 hours ago; last changed 1 hours ago.
Measured 4 of 4 score categories from the official feed URL on file.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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
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
5489 of 5489 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus 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
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
250 of 729 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 +9 points in its category
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
- 5489 of 5489 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- Feed evidence
- The feed contains no fare information.
- Next action
- 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.
- 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
- Feed evidence
- 250 of 729 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
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_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.
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.
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 70 days.
- Published accessibility data
- Accessibility information is stated for 65.7% 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
- Live-arrival data covered 100% of scheduled trips in the sampled window.
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 5 kinds of issue across 234 instances (0 error, 234 warning, 0 informational).
Service data covers the next 70 days.
66% of stops state wheelchair accessibility (66% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
66% of stops state accessibility (66% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
13 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 2, 17, 18, 3C, and more).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
695 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Ft. Wm. Rd. & Transit Office", "Ft. Wm. Rd. & Central", "Ft. Wm. Rd. & Walmart", 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.
Sampled 9 times: 3 of 3 configured feeds healthy; 100.0% of scheduled trips had live predictions; 100.0% of vehicles on their route; predictions ran a median of 0s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 729 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.
- 1 (red)
- 10 (purple)
- 11 (gray)
- 12 (yellow)
- 13 (teal)
- 14 (gray)
- 15 (black)
- 16 (red)
- 17 (pink)
- 18 (pink)
- 2 (teal)
- 3C (brown)
- 3J (pink)
- 3M (orange)
- 4 (orange)
- 5 (purple)
- 6 (red)
- 7 (brown)
- 8 (green)
- 9 (teal)
| Route | Type | Line color |
|---|---|---|
| 1 | Bus | red |
| 10 | Bus | purple |
| 11 | Bus | gray |
| 12 | Bus | yellow |
| 13 | Bus | teal |
| 14 | Bus | gray |
| 15 | Bus | black |
| 16 | Bus | red |
| 17 | Bus | pink |
| 18 | Bus | pink |
| 2 | Bus | teal |
| 3C | Bus | brown |
| 3J | Bus | pink |
| 3M | Bus | orange |
| 4 | Bus | orange |
| 5 | Bus | purple |
| 6 | Bus | red |
| 7 | Bus | brown |
| 8 | Bus | green |
| 9 | Bus | teal |
List every stop
- Ft. Wm. Rd. & Transit Office
- Ft. Wm. Rd. & Central
- Ft. Wm. Rd. & Walmart
- Ft. Wm. Rd. & Harbour Expy
- Ft. Wm. Rd. & Intercity
- Intercity Shopping Centre
- Ft. Wm. Rd. & Northern
- Simpson & Southern
- Simpson & Assef Ct.
- Simpson & Pacific
- Simpson & Rowand
- Simpson & Ogden
- Simpson & Finlayson
- Simpson & Dease
- Simpson & Bethune
- City Hall Terminal
- Donald & Cent. Sq.
- Vickers & Victoria
- Victoria & Marks
- Court & River
- Franklin & Arthur
- Franklin & Isabella
- Franklin & Moodie
- Walsh & Franklin
- Walsh & St. Pats
- Sprague & Empire
- Sprague & Brock
- Brock & 300s Block
- Brock & Tarbutt
- Brock & 200s Block
- Ford & Brock
- Ford & Frederica
- Frederica & Ford
- Frederica & 100s Block
- Frederica & Edward
- Frederica & Brown
- Frederica & 200s Block
- Frederica & Heath
- Frederica at James
- Frederica & Centre
- Frederica & Mountdale
- Frederica & Crawford
- Frederica & Stanley
- Frederica & Georgina
- Frederica & Alpine
- Neebing & Francis
- Mary & Neebing
- Mary & Holt
- Mary & Georgina
- Mary & Nipigon
- Mary & Home
- Mary & Broadmore
- Mary & Euclid
- Mary & Yonge
- Mary & Heath
- Mary & Brown
- Brown & Francis
- Brown & Frederica
- Frederica & Brown
- Frederica & Edward
- Frederica & 100s Block
- Ford & Frederica
- Ford & Francis
- Brock & 200s Block
- Brock & Tarbutt
- Brock & 300s Block
- Brock & Sprague
- Sprague & Brock
- Sprague & Empire
- Sprague & Walsh
- Walsh & Selkirk
- Franklin & Moodie
- Franklin & Isabella
- Franklin & Ridgeway
- Franklin & Arthur
- Franklin & Donald
- Victoria & Marks
- Vickers & Victoria
- Arthur & McKellar
- Simpson & Miles
- Simpson & Bethune
- Simpson & Dease
- Simpson & Finlayson
- Simpson & Ogden
- Simpson & Rowand
- Simpson & Pacific
- Simpson & Atlantic
- Simpson & Southern
- Ft. Wm. Rd. & Isabel
- Intercity Shopping Centre
- Ft. Wm. Rd. & Intercity
- Ft. Wm. Rd. & Main
- Ft. Wm. Rd. & Mooney
- Ft. Wm. Rd. & Central
- Ft. Wm. Rd. & Spofford
- Ft. Wm. Rd. & Court
- Court & Wholesale Club
- Court & John
- Court & Cornwall
- Bay & Johnson
- Cumberland & Water
- Cumberland & Pearl
- Cumberland & Red River
- Waterfront Terminal
- Cumberland & Villa
- Cumberland & St. James
- Cumberland & Van Horne
- Cumberland & Angus
- Cumberland & Egan
- Cumberland & Fitzgerald
- Clavet & Cumberland
- Clavet & Algoma
- Algoma & Dawson Court
- Algoma & MacDougall
- MacDougall & Algoma
- MacDougall & Cumberland
- Cumberland & Gibson
- Cumberland & Parks North
- Hodder & Grenville
- Hodder & Cuyler
- Hodder & Merrill
- Hodder & Morse
- Hodder & Lillian
- Hodder & Surrey
- Hodder & Arundel
- Hodder & Elliot
- Hodder & Black Bay
- Hodder & Rona
- Cowan & Hodder
- Leslie & Rona
- Leslie & Black Bay
- Black Bay & Grenville
- Black Bay & Dewe
- Dewe & 500s Block
- Dewe & Arundel
- Arundel & Grenville
- Leslie & Arundel
- Leslie & Conyers
- Leslie & Talbot
- Lillian & Leslie
- Greville & Rita
- Grenville & Morse
- Grenville & Marion
- Grenville & Adams
- Grenville & Roberta
- Grenville & Adelaide
- Cumberland & Grenville
- Cumberland & Gibson
- Cumberland & Beck
- Cumberland & MacDougall
- Clavet & Cumberland
- Cumberland & Munro
- Cumberland & Egan
- Cumberland & Angus
- Cumberland & Van Horne
- Cumberland & Wolseley
- Cumberland & Elgin
- Cumberland & Villa
- Cumberland & Red River
- Cumberland & Pearl
- Cumberland & Wilson
- Cumberland & Water
- Bay & Johnson
- Court & Bay
- Court & Cornwall
- Court & Queen
- Ft. Wm. Rd. & Wholesale Club
- Ft. Wm. Rd. & Lisgar
- Ft. Wm. Rd. & Water
- Ft. Wm. Rd. & Second
- Camelot & Court
- Court & Manitou
- John & Machar
- John & Secord
- John & Banning
- High & Queen
- Canada Games Complex
- Community Auditorium
- Beverly & Newton
- Beverly & Ravenwood
- Oliver & Balmoral
- Lakehead University
- Nursing Building
- Oliver & Keith Jobbitt
- Thunder Bay Regional Hospital
- Golf Links & Oliver
- Golf Links & Medical Clinic
- Golf Links & Ridgecrest
- Golf Links & Innovation
- Golf Links & Fanshaw
- Confederation College
- Sibley Residence
- Edward & James
- Edward & Ironwood
- Edward & Redwood
- Northwood Park Plaza
- Edward & Ward
- Edward & Churchill
- Edward & Parkway
- Edward & Miles
- Victoria & Maplewood
- Victoria & Ford
- Victoria & Lillie
- Victoria & Hyde Park
- Victoria & Wellington
- Victoria & Selkirk
- Victoria & Franklin
- Victoria & Waterloo
- Victoria & Friendship Gardens
- Victoria & Lillie
- Victoria & Ford
- Victoria & Maplewood
- Edward & Victoria
- Edward & Donald
- Edward & Begin
- Edward & Isabella
- Edward & Walsh
- Edward & Gordon
- Edward & Christina
- Edward & Brock
- Edward & Frederica
- Gore & Brown
- Brown & Frederica
- Brown & Francis
- Brock & Brown
- Edward & Brock
- Edward & Christina
- Edward & Gordon
- Edward & Walsh
- Edward & Isabella
- Edward & Arthur
- Edward & Donald
- Edward & Victoria
- Edward & Riverview
- Edward & Churchill
- Edward & Ward
- Edward & Redwood
- Edward & Woodlawn
- Edward & James
- Sibley Residence
- Golf Links & Fanshaw
- Golf Links & Medical Clinic
- Golf Links & Oliver
- Thunder Bay Regional Hospital
- Oliver & Sanders
- Oliver & Bora Laskin
- Beverly & Ravenwood
- Beverly & Darwin
- Community Auditorium
- Tbaytel Park
- and 479 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
- Warning5489 instances
5489 of 5489 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning250 instances
250 of 729 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)
- Warning210 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning20 instances
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.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · 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)
- Info26 instances
26 of 26 published service alerts have no header text.
An alert with no text shows up blank in the app. Riders never learn what changed.
Fix: Give every alert a one-line plain-language header in your alerts tool; the description field can carry the detail. (A habit in your alerts tool, not a code change.)
Finding code: scorecard_rt_alerts_missing_text
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · 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 66% 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 70 days.
- Accessible Not yet
- States wheelchair access on 66% 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 2 of 729 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Realtime reliability
The realtime feed responded on 100.0% of 7 checks over the last 1 day, with 5s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Live predictions vs schedule
Arrival predictions ran right on the schedule, and stayed within 74s nine times in ten. They were on time (about a minute early to five late) 97.6% of the time. 100.0% of reported vehicle positions sat on or near the published route shape.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
Clears the Google and Apple Maps four-week coverage bar. This feed has 70 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 74 / 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 54 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 100 / 100
- 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/thunder-bay-transit/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.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.