Feed status · checked 2026-08-23
London Transit Commission (Ontario)
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
down 0.4 since 2026-08-22
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 53 minutes ago; last changed 1 days ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
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 configured feed URL. Publisher ownership of that URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export with a validity window that reaches at least 60 days out.Likely your export tool
Service data runs out in 13 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
⏱ One export setting.worth about +67 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
1938 of 1938 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
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
7684 of 7684 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
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
- Service data runs out in 13 day(s).
- Next action
- Re-export with a validity window that reaches at least 60 days out.
- 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
- 1938 of 1938 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
- Feed evidence
- 7684 of 7684 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
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.
Re-export with a validity window that reaches at least 60 days out. · 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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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 13 days.
- Published accessibility data
- Accessibility information is stated for 0% 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.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 6 kinds of issue across 10 instances (0 error, 10 warning, 0 informational).
Service data runs out in 13 day(s). Publish an updated feed soon or riders will lose trip planning.
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.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
190 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Adelaide at Fanshawe Pk Rd SB - #32", "Adelaide south of Leathorne St NB - #48", "Adelaide at SE Osgoode NB - #60", 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.
This feed has 1938 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.
- 01 (gray)
- 02 (gray)
- 03 (gray)
- 04 (gray)
- 05 (gray)
- 06 (yellow)
- 07 (green)
- 09 (gray)
- 10 (gray)
- 12 (pink)
- 13 (gray)
- 15 (teal)
- 16 (green)
- 17 (white)
- 19 (gray)
- 20 (teal)
- 24 (pink)
- 25 (gray)
- 27 (gray)
- 28 (teal)
- 30 (pink)
- 31 (green)
- 33 (pink)
- 34 (pink)
- 35 (yellow)
- 36 (white)
- 37 (teal)
- 38 (pink)
- 90 (orange)
- 91 (orange)
- 92 (orange)
- 93 (orange)
- 94 (orange)
| Route | Type | Line color |
|---|---|---|
| 01 Route 1 | Bus | gray |
| 02 Route 2 | Bus | gray |
| 03 Route 3 | Bus | gray |
| 04 Route 4 | Bus | gray |
| 05 Route 5 | Bus | gray |
| 06 Route 6 | Bus | yellow |
| 07 Route 7 | Bus | green |
| 09 Route 9 | Bus | gray |
| 10 Route 10 | Bus | gray |
| 12 Route 12 | Bus | pink |
| 13 Route 13 | Bus | gray |
| 15 Route 15 | Bus | teal |
| 16 Route 16 | Bus | green |
| 17 Route 17 | Bus | white |
| 19 Route 19 | Bus | gray |
| 20 Route 20 | Bus | teal |
| 24 Route 24 | Bus | pink |
| 25 Route 25 | Bus | gray |
| 27 Route 27 | Bus | gray |
| 28 Route 28 | Bus | teal |
| 30 Route 30 | Bus | pink |
| 31 Route 31 | Bus | green |
| 33 Route 33 | Bus | pink |
| 34 Route 34 | Bus | pink |
| 35 Route 35 | Bus | yellow |
| 36 Route 36 | Bus | white |
| 37 Route 37 | Bus | teal |
| 38 Route 38 | Bus | pink |
| 90 Route 90 | Bus | orange |
| 91 Route 91 | Bus | orange |
| 92 Route 92 | Bus | orange |
| 93 Route 93 | Bus | orange |
| 94 Route 94 | Bus | orange |
| 95 Route 95 | Bus | orange (no shape in feed) |
List every stop
- 1030 Clarke Road NB - #2929
- 15701 Robins Hill WB - #2930
- 15835 Robins Hill WB - #2931
- 1901 Crumlin SB - #2932
- 1980 Crumlin NB - #2933
- Opp 1985 Richmond NB - #2773
- 1985 Richmond SB - #2774
- Main at Bainard Street - #2504
- 2530 Innovation SB - #2950
- 2860 Innovation SB - #2951
- Opp 517 Fanshawe Park Rd EB - #2979
- 517 Fanshawe Park Road - #2505
- Adelaide at Ada NB - #20
- Adelaide at Ada SB - #21
- Adelaide at Blackwater SB - #2693
- Adelaide at Central NB - #22
- Adelaide at Central SB - #23
- Adelaide at Cheapside NB - #24
- Adelaide at Cheapside SB - #25
- Adelaide at Dufferin SB - #2690
- Adelaide at Dundas NB - #27
- Adelaide at Dundas SB - #28
- Adelaide at Edna SB - #29
- Adelaide at Fanshawe Pk Rd SB - #32
- Adelaide at Glenora SB - #2779
- Adelaide at Glenora NB - #33
- Adelaide at Grosvenor NB - #34
- Adelaide at Grosvenor SB - #35
- Adelaide at Hamilton SB - #36
- Adelaide at Hill NB - #37
- Adelaide at Hill SB - #38
- Adelaide at Huron NB - #39
- Adelaide at Huron SB - #40
- Opposite 1145 Adelaide NB - #42
- Adelaide north of Kipps Lane NB - #43
- Adelaide north of Kipps Lane SB - #44
- Adelaide south of Kipps Lane 2 SB - #47
- Adelaide south of Leathorne St NB - #48
- Adelaide at Leathorne SB - #49
- Adelaide north of Leathorne 1 NB - #50
- Adelaide north of Leathorne 2 NB - #52
- Adelaide north of Leathorne 3 NB - #2185
- Adelaide at Hamilton NB - #53
- Adelaide at Lorne NB - #54
- Adelaide at Mapledale SB - #55
- Adelaide at Maud NB - #56
- Adelaide at McMahen NB - #57
- Adelaide at Nelson NB - #58
- Adelaide at Nelson SB - #59
- Adelaide at SE Osgoode NB - #60
- Adelaide at NW Osgoode SB - #61
- Adelaide at NE Osgoode NB - #62
- Adelaide at SE Osgoode SB - #63
- Adelaide at SE Osgoode NS NB - #64
- Adelaide at SW Osgoode SB - #65
- Adelaide at Osgoode 3 NB - #66
- Adelaide at Oxford NB - #67
- Adelaide at Oxford SB - #68
- Adelaide at McMahen SB - #69
- Adelaide at Piccadilly NB - #70
- Adelaide at Piccadilly SB - #71
- Adelaide at Princess SB - #72
- Adelaide at Queens SB - #73
- Adelaide at Regent NB - #74
- Adelaide at Southdale SB - #77
- Adelaide at St. James NB - #78
- Adelaide at St. James SB - #79
- Adelaide at Tennant NB - #80
- Adelaide at Terrace NB - #81
- Adelaide at Thompson NB - #82
- 207 Adelaide - #83
- Adelaide at Thompson SB - #84
- 155 Adelaide SB - #85
- 247 Adelaide SB - #86
- Adelaide at Victoria NB - #87
- Adelaide at Victoria SB - #88
- Adelaide at Willowdale SB - #2186
- Adelaide at Windermere NB - #89
- Adelaide at Windermere SB - #90
- Admiral at Bonaventure EB - #93
- Admiral at Bonaventure WB - #94
- Admiral at Carlyle EB - #95
- Admiral at Carlyle WB - #96
- 319 Admiral - #97
- Admiral at Kipling EB - #99
- Admiral at Sovereign WB - #100
- Admiral at Trafalgar NB - #2635
- Admiral at Vaubois EB - #101
- Admiral at Vaubois WB - #102
- Admiral at Veterans Memorial Pkwy WB - #104
- Aldersbrook Gt at Aldersbrook Rd SB - #2188
- Aldersbrook at Ardsley NB - #114
- Aldersbrook at Ardsley SB - #115
- Aldersbrook at Aurora SB - #116
- Aldersbrook at Barrydale SB - #117
- Aldersbrook at Blackacres SB - #119
- Aldersbrook north of Blackacres NB - #120
- Aldersbrook at Brandy Lane NB - #121
- Aldersbrook at Brunswick NB - #122
- Aldersbrook at Brunswick SB - #123
- Aldersbrook at Gainsborough NB - #126
- Aldersbrook at Gainsborough SB - #127
- Aldersbrook at Hawthorne NB - #128
- Aldersbrook at Hawthorne SB - #129
- Aldersbrook at Lawson NB - #130
- Aldersbrook at Lawson SB - #131
- Aldersbrook at Ranchwood NB - #132
- Aldersbrook at Rexway NB - #134
- Aldersbrook at Rexway SB - #135
- Aldersbrook at Southcott Crt WB - #136
- Aldersbrook at Brandy Ln N Leg NB - #137
- Aldersbrook at Brandy Ln SB - #138
- Alumni Hall EB - #141
- Alumni Hall WB - #142
- Ambleside at Corley FS SB - #2780
- Ambleside at Grangeover Cres NS SB - #2781
- Ambleside at Hesketh NS SB - #2782
- Ambleside at Hillside NS SB - #2783
- Ambleside at Whitehaven NS SB - #2784
- Ambleside at Grasmere Cres WB - #145
- Ambleside at Grangeover WB - #2190
- Ambleside at Hillside WB - #147
- Ambleside at Whitehaven WB - #149
- 286 Ambleside - #150
- Andover at Commissioners NB - #154
- Andover at Commissioners SB - #155
- Andover at Elmgrove Cr SB - #156
- Andover at Novello NB - #158
- Andover at Village Green NB - #160
- Andover at Village Green SB - #161
- Andover at Viscount SB - #163
- Andover north of Viscount NB - #164
- Argyle Mall SB - Stop 1 - #166
- Argyle Mall NB - Stop 2 - #167
- Ashbury at Millbank EB - #168
- Ashbury at Millbank WB - #169
- Ashbury at Surrey Cres NB - #170
- Ashbury at Surrey Cres SB - #171
- Philip Aziz at Western NB - #2785
- Barker at Huron NB - #2786
- Barker at Huron SB - #176
- Barker at Kipps NS NB - #2787
- Barker at Melsandra FS NB - #2788
- Barker at Melsandra NS SB - #2789
- Base Line at Cotswold WB - #2605
- Base Line at Dundee Place EB - #184
- Base Line west of Fairview Ave WB - #189
- Base Line west of Fairview EB - #190
- Base Line at High EB - #192
- Base Line at McGregor EB - #196
- Base Line east of Wellington EB - #206
- Base Line west of Wellington EB - #208
- Base Line west of Wellington WB - #210
- Base Line east of West St EB - #211
- 30 Base Line WB - #212
- Base Line west of West St EB - #213
- 90 Base Line WB - #214
- Base Line at Wharncliffe EB - #2194
- Base Line at Wharncliffe WB - #216
- Beachwood at Base Line NB - #222
- Beachwood at Base Line SB - #223
- Beaverbrook at Blythwood WB - #224
- Beaverbrook at Capulet WB - #2415
- Beaverbrook at Capulet EB - #2416
- Beaverbrook at Horizon EB - #2417
- Beaverbrook at Horizon WB - #225
- Beaverbrook at Oakcrossing west WB - #2575
- Beaverbrook at Oakcrossing east WB - #2385
- Beaverbrook at Oxford NB - #226
- Beaverbrook at Oxford SB - #227
- Beaverbrook at Proudfoot EB - #2418
- Sarnia at Beaverbrook EB - #2387
- Beaverbrook at Whetherfield EB - #2701
- Beaverbrook at Wild Rose WB - #2388
- Beaverbrook at Wonderland EB - #2389
- Beaverbrook at Wonderland WB - #228
- Beckworth at Lancaster EB - #229
- Beckworth at Langton EB - #230
- Beckworth at Sorrel EB - #231
- Beckworth at Toukay EB - #232
- Beckworth at Tudor EB - #233
- Belmont at Hillsborough EB - #234
- Belmont at Notre Dame EB - #235
- Belmont at St Lawrence EB - #236
- Belmont at Wharncliffe EB - #237
- Berkshire at Berkshire Place NB - #2195
- Berkshire at Berkshire Place SB - #2196
- Berkshire at Gardenwood NB - #240
- Berkshire south of Gardenwood SB - #2198
- Berkshire north of Gardenwood SB - #241
- Berkshire at Robin NB - #242
- Berkshire at Robin SB - #243
- Berkshire at Springbank NB - #244
- Berkshire at Springbank SB - #245
- Berkshire at Topping Lane NB - #246
- Berkshire at Topping Lane SB - #247
- Bessemer at Exeter NB - #250
- Bessemer at Bessemer Crt 2 NB - #252
- Bessemer at Hargrieve NB - #253
- Blackwater east of Adelaide EB - #255
- Blackacres at Edgehill Cres 1 WB - #262
- Blackacres at Edgehill Cres WB - #263
- Blackacres at Hawthorne NB - #265
- Blackacres at Wonderland WB - #267
- Blackacres at Winding Way WB - #269
- Bluebell at Sunningdale NB - #2309
- Bluebell at Sunningdale SB - #274
- Boler at Byron Baseline NB - #275
- Boler south of Commissioners NB - #276
- Boler north of Commissioners NB - #277
- Boler at Glenrose NB - #278
- Boler at Griffith NB - #279
- Boler at Wayne Road NB - #280
- Bonaventure at Dundas SB - #281
- Bonaventure at Moreau Cr SB - #283
- Bonaventure at Napoleon Cr SB - #284
- Bonaventure at Simpson Cr SB - #285
- Bonaventure at Trafalgar SB - #287
- Bow at Bancroft EB - #290
- Bradley between Willow & Adelaide EB - #291
- Bradley at Adelaide WB - #292
- Bradley at Adelaide EB - #2203
- Bradley between Adelaide & Willow WB - #2324
- Bradley at Willow 2 EB - #2325
- Bradley at Willow 1 WB - #293
- Bradley at Dearness WB - #294
- Bradley west of Ernest WB - #2790
- Bradley west of Ernest 2 WB - #2791
- Bradley at Ernest Ave EB - #295
- Bradley at Jalna FS EB - West Leg - #2792
- Bradley west of Jalna WB - East Leg - #2793
- Bradley west of Jalna WB - West Leg - #2794
- Bradley at Jalna EB - #296
- Bradley at Jalna East EB - #2597
- Bradley west of Wellington Rd EB - #2326
- Bradley at Wellington WB - #2327
- Bradley east of Wellington Rd EB - #297
- Bradley at Willow 1 EB - #298
- Bradley at Willow 2 WB - #2205
- White Oaks Elementary School - #2206
- Briarhill at Huron SB - #300
- Briarhill north of Melsandra SB - #302
- Briarhill south of Melsandra 2 SB - #2601
- Bruce at Marley Place EB - #303
- Bruce at Wortley EB - #304
- Brydges at Cornish EB - #2207
- Brydges at Graydon WB - #2208
- Brydges at Hale EB - #305
- Brydges at Hale WB - #306
- Brydges at Highbury WB - #308
- and 1688 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 0.4 since 2026-08-22.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 61.0 | first check |
| 2026-08-07 | 60.6 | down 0.4 |
| 2026-08-22 | 50.8 | down 9.8 |
| 2026-08-23 | 50.4 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.6
- Rider experience no change
What changed in this feed
Overall score fell 0.4 points since 2026-08-22.
Same feed file as 2026-08-22; the published zip did not change.
What changed inside the export
- Route 95 (Route 95) is new in this export.
- 5 stops left the export.
- 1 stop moved more than 100 m.
Read from the feed file itself, compared with the previous export. A service change is normal; this is a heads-up so nothing disappears silently.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
What changed over time
On 2026-08-06 this feed started at grade D. On 2026-08-22 the grade moved from D to F. As of 2026-08-23 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-08-22 Grade went D to F, freshness fell 25 points.
Everything we checked
12 findings, ordered by severity.
Show every finding
- Warning7684 instances
7684 of 7684 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)
- Warning1938 instances
1938 of 1938 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)
- Warning7 instances
7 of 7684 trips lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning4 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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)
- Warning1 instance
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)
- Warning1 instance
This feed's service calendar runs out within the next 30 days.
If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.
Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date30_days · 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
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.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Finding code: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Service data runs out in 13 day(s).
When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Finding code: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
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)
Who this service reaches
In the areas this feed serves, the Canadian Index of Multiple Deprivation reads as moderate need, a within-Canada measure of economic dependency and situational vulnerability. Current, complete data matters most where need is highest.
Conformance mark Not yet
Two requirements remain for this feed to earn the conformance mark. Service data runs out in 13 days; renew to qualify. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data runs out in 13 days; renew to qualify.
- Accessible Not yet
- States wheelchair access on 0% 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.
At risk for the Google and Apple Maps four-week coverage bar. This feed has 13 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.
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 76 / 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 22 / 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 38 / 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/london-transit-commission/2026-08-23.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-08-23. 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.