Call-prep brief · checked 2026-10-07

London Transit Commission (Ontario)

Grade C · 79.4 / 100

Down 0.4 points since 2026-10-06 (C to C).

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.

What changed since the last check

Correctness no change
Freshness down 1.6
Rider experience no change

Top three things to 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.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
This one is about the feed as a whole, so there is no share of it to count.
Effort: A small file for most flat-fare systems.
Delete the empty calendars or set their service days.
Some service calendars have no days of the week switched on. Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Effort: A few minutes in your scheduling software.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Effort: Often a bulk fix in your scheduling software.

Riders and need behind these fixes

Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
The areas this feed serves measure moderate on transit need, on a within-Canada scale. Source: Canadian Index of Multiple Deprivation 2021, as of 2026-10-01.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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: 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

Agency: London Transit Commission (Ontario)
Finding: scorecard_no_fare_data
Feed evidence: The feed contains no fare information.
Why it matters: Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/london-transit-commission/?finding=scorecard_no_fare_data#finding-handoff

Key facts

Feed URL: http://www.londontransit.ca/gtfsfeed/google_transit.zip
Last checked: 2026-10-07
Service window: 52 days of service data remain. Last service date 2026-11-28.
Feed version: 2026 September + Trippers_20260924
Location: Ontario, Canada

Part of the Canada portfolio: see where this agency sits among the other feeds in that group before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.