Feed status · checked 2026-07-19
BC Transit (Kamloops Transit System)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in British Columbia, 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
575 of 575 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
1778 of 1778 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
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 48 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.
Score by category
The MobilityData validator flagged 4 kinds of issue across 88 instances (0 error, 88 warning, 0 informational).
Service data covers the next 48 days.
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.
2 accessibility depth signals
11 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 3, 4, 5, 6, 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.
523 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Crestline St at Fleetwood Ave", "Westsyde Rd at Oak Hills Blvd", "Crestline St at Fleetwood Ave", 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.
- 1 (teal)
- 10 (purple)
- 13 (yellow)
- 14 (brown)
- 16 (gray)
- 17 (pink)
- 18 (gray)
- 2 (gray)
- 3 (orange)
- 4 (teal)
- 5 (yellow)
- 6 (green)
- 7 (pink)
- 9 (purple)
| Route | Type | Line color |
|---|---|---|
| 1 Tranquille | Bus | teal |
| 10 North Shore TRU Express | Bus | purple |
| 13 Yellowhead | Bus | yellow |
| 14 Batchelor Heights | Bus | brown |
| 16 Juniper Ridge | Bus | gray |
| 17 Dallas | Bus | pink |
| 18 Mt. Paul | Bus | gray |
| 2 Parkcrest | Bus | gray |
| 3 Westsyde | Bus | orange |
| 4 Pacific Way | Bus | teal |
| 5 Pineview | Bus | yellow |
| 6 Downtown Loop | Bus | green |
| 7 Aberdeen | Bus | pink |
| 9 Gleneagles | Bus | purple |
This feed has 575 stops.
List every stop
- Lansdowne Exch Bay I
- Lansdowne St at 4th Ave
- Lansdowne St at 2nd Ave
- Tranquille Rd at Don St
- Tranquille Rd at Palm St
- Tranquille Rd at Clapperton Rd
- Tranquille Rd at Wood St
- Tranquille Rd at Oak Rd
- Tranquille Rd at Vernon Ave
- North Shore Exch Bay C
- Tranquille Rd at 10th St
- Tranquille Rd at 12th St
- Tranquille Rd at Valhalla Dr
- Tranquille Rd at Nicolani Dr
- Tranquille Rd at Singh St
- Tranquille Rd at Holt St
- Tranquille Rd at Desmond St
- Tranquille Rd at Southill St
- Tranquille Rd at Caroline St
- Tranquille Rd at Windbreak St
- Tranquille Rd at Invermere Crt
- Tranquille Rd at Shelan Pl
- Tranquille Rd at Schreiner St
- Crestline St at Glenview Ave
- Crestline St at Young Ave
- Crestline St at Fleetwood Ave
- Fleetwood Ave at Schreiner St
- Greenfield Ave at Schreiner St
- Greenfield Ave at Westgate St
- Greenfield Ave at Windbreak St
- Windbreak St at Sunnycrest Ave
- Tranquille Rd at Windbreak St
- Tranquille Rd at Mayfair St
- Tranquille Rd at Holt St
- Tranquille Rd at Singh St
- Tranquille Rd at Nicolani Dr
- Tranquille Rd at 12th St
- Tranquille Rd at 10th St
- Tranquille Rd at 8th St
- North Shore Exch Bay E
- Tranquille Rd at Yew St N
- Tranquille Rd at Yew St S
- Tranquille Rd at MacKenzie Ave
- Tranquille Rd at Knox St
- Tranquille Rd at Palm St
- Tranquille Rd at Wilson St
- Tranquille Rd at Leigh Rd
- 200 Blk Victoria St W
- Seymour St at 1st Ave
- Seymour St at 3rd Ave
- Seymour St at 4th Ave
- 6th Ave at Victoria St
- Lansdowne Exch Bay H
- Yew St at Tranquille Rd
- MacKenzie Ave at Maple St
- MacKenzie Ave at Willow St
- Willow St at Stewart Ave
- Cottonwood Ave at Willow St
- Cottonwood Ave at Kenora Rd
- Kenora Rd at 12th St
- 12th St at Tranquille Rd
- 12th St at Selkirk Ave
- 12th St at Pembroke Ave
- 12th St at Halston Ave
- Halston Ave at 13th St
- Parkcrest Ave at Nicolani Dr
- Parkcrest Ave at Singh St
- Parkcrest Ave at Holt St
- Fleetwood Ave at Holt St
- Fleetwood Ave at Desmond Pl
- Fleetwood Ave at Southill St
- Parkcrest Ave at Bentley Pl
- Parkcrest Ave at Ponlen St
- Parkcrest Ave at Windbreak St
- Parkcrest Ave at McLean St
- Parkcrest Ave at Schreiner St
- Schreiner St at Fleetwood Ave
- Crestline St at Fleetwood Ave
- Crestline St at Parkcrest Ave
- Crestline St at Rosewood Ave
- Briarwood Ave at Crestline St
- Schreiner St at Paulsen Pl
- Parkcrest Ave at Schreiner St
- Parkcrest Ave at McLean St
- Parkcrest Ave at Windbreak St
- Parkcrest Ave at Ponlen St
- Southill St at Parkcrest Ave
- Fleetwood Ave at Southill St
- Fleetwood Ave at Desmond St
- Fleetwood Ave at Holt St
- Parkcrest Ave at Holt St
- Parkcrest Ave at Singh St
- Parkcrest Ave at Ollek St
- Halston Ave at 13th St
- 12th St at Pembroke Ave
- 12th St at Selkirk Ave
- Kenora Rd at 12th St
- Cottonwood Ave at Kenora Rd
- Cottonwood Ave at Willow St
- Willow St at MacKenzie Ave
- MacKenzie Ave at Thrupp St
- MacKenzie Ave at Williams St
- Lansdowne Exch Bay G
- Fortune Dr at Baker St
- Fortune Dr at Fort Ave
- Fortune Dr at Spruce Ave
- Fortune Dr at Birch Ave
- Fortune Dr at Aspen St
- Fortune Dr at Chestnut Ave
- Fortune Dr at Holly Ave
- North Shore Exch Bay D
- 8th St at Fortune Dr
- 8th St at Richmond Ave
- 8th St at Sherbrooke Ave
- 8th St at York Ave
- Westsyde Rd at Collingwood Dr W
- Westsyde Rd at Westmount Dr
- Westsyde Rd at Collingwood Dr E
- Westsyde Rd at Walkem Rd
- Westsyde Rd at Yates Rd
- Westsyde Rd at Anderson Terr
- Westsyde Rd at McQueen Dr
- Westsyde Rd at Woodhaven Dr
- Westsyde Rd at Rue Chez Nous
- Westsyde Rd at Parkview Dr
- Westsyde Rd at Oak Hills Blvd
- Westsyde Rd at Franklin Rd
- Westsyde Rd at Morven Dr
- Westsyde Rd at Soldier Rd
- Westsyde Rd at Garnet Rd
- Westsyde Rd at Bissette Rd
- Westsyde Rd at Porterfield Rd
- Westsyde Rd at Jensen Rd
- Westsyde Rd at Overlander Dr
- Westsyde Rd at Sun Valley Dr
- Harrington Rd at Westsyde Rd
- Harrington Rd at Overlander Dr
- Overlander Dr at Reemon Dr
- Sicamore Dr at Overlander Dr
- Bank Rd at Overlander Dr
- Westsyde Rd at Dever Dr
- Westsyde Rd at Puhallo Dr
- Westsyde Rd at Palmer Pl
- Westsyde Rd at Serle Rd
- Westsyde Rd at Bissette Rd
- Westsyde Rd at Garnet Rd
- Westsyde Rd at Georgeann Rd
- Westsyde Rd at Morven Pl
- Westsyde Rd at Agassiz Rd
- Westsyde Rd at Oak Hills Blvd
- Westsyde Rd at Parkview Dr
- Westsyde Rd at Rue Chez Nous
- Westsyde Rd at Woodhaven Dr
- Westsyde Rd at McQueen Dr
- Westsyde Rd at Anderson Terr
- Westsyde Rd at Yates Rd
- Westsyde Rd at Walkem Rd
- Westsyde Rd at Westmount Dr
- Westsyde Rd at Collingwood Dr
- 8th St at Sudbury Ave
- 8th St at Lethbridge Ave
- 8th St at Selkirk Ave
- 8th St at Moncton Ave
- 8th St at Tranquille Rd
- North Shore Exch Bay B
- Fortune Dr at Holly Ave
- Fortune Dr at Oak Rd
- Fortune Dr at Aspen St
- Fortune Dr at Wood St
- Fortune Dr at Spruce Ave
- Fortune Dr at Leigh Rd
- Fortune Dr at Larch Ave
- Lansdowne Exch Bay F
- 4th Ave at Seymour St
- 4th Ave at Battle St
- 4th Ave at Nicola St
- Columbia St at 3rd Ave
- 700 Blk Sahali Terr
- Sahali Terr at Pemberton Terr
- Bestwick Dr at Anvil Cres
- McGill Rd at Monashee Crt
- 200 Blk McGill Rd
- McGill Rd at Chapperon Dr
- McGill Rd at Columbia St W
- McGill Rd at Summit Dr
- McGill Rd at University Dr
- Campus Dr at McGill Rd
- Campus Dr at WolfPack Rd
- TRU Exch Bay G
- University Dr at McGill Rd
- 1000 Blk Hillside Dr
- Hillside Dr at Notre Dame Dr
- Aberdeen Mall Bay B
- Pacific Way at Hillside Dr
- Pacific Way at Hugh Allan Dr
- Pacific Way at Pearson Pl
- Pacific Way at Howe Rd
- Pacific Way at Ravenwood Terr
- Pacific Way at Greystone Cres
- Pacific Way at Links Way
- Pacific Way at Aberdeen Dr
- 2500 Blk Pacific Way
- Abbeyglen Way at Bramble Lane
- Van Horne Dr at Aberdeen Dr
- Van Horne Dr at Laurier Dr
- Pacific Way at Greystone Cres
- Pacific Way at Ravenwood Terr
- Pacific Way at Howe Rd
- Pacific Way at Pearson Pl
- Hillside Dr at Pacific Way
- Aberdeen Mall Bay A
- Hillside Dr at Cariboo Pl
- Hillside Dr at Notre Dame Dr
- Hillside Dr at McGill Rd
- Hillside Dr at McGill Rd
- TRU Exch Bay D
- Campus Dr at WolfPack Rd
- McGill Rd at Dalhousie Dr
- McGill Rd at Summit Dr
- McGill Rd at Columbia St W
- McGill Rd at Chapperon Dr
- 200 Blk McGill Rd
- McGill Rd at Monashee Crt
- McGill Rd at Bestwick Dr
- Bestwick Dr at Greenstone Dr
- Bestwick Dr at Sahali Terr
- Sahali Terr at Pemberton Terr
- Sahali Terr at Columbia St W
- 3rd Ave at Columbia St
- 3rd Ave at Battle St
- 3rd Ave at Seymour St
- TRU Exch Bay H
- Hillside Dr at Pacific Way
- Hillside Dr at Mt Dufferin Ave
- Hillside Dr at Monterey Pl
- Hillside Dr at Mt Dufferin Dr
- Hillside Dr at Copperhead Dr
- Copperhead Dr at Iron Mask Rd
- Copperhead Dr at Kryczka Pl
- Hugh Allan Dr at Lodgepole Dr
- Lodgepole Dr at Englemann Crt
- Lodgepole Dr at Arnica St
- Lodgepole Dr at Snowberry Cres
- Copperhead Dr at Lodgepole Dr
- Copperhead Dr at Hugh Allan Dr
- Copperhead Dr at Kryczka Pl
- Copperhead Dr at Versatile Dr
- Hillside Dr at Copperhead Dr
- 1800 Blk Hillside Dr
- Hillside Dr at Davies Pl
- and 325 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
- Warning1778 instances
1778 of 1778 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning575 instances
575 of 575 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)
- Warning71 instances
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.)
Validator rule: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning14 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.)
Validator rule: 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.)
Validator rule: 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.)
Validator rule: 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 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)
- 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.)
Validator rule: 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
This feed is close to the conformance mark. 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 Met
- Service data covers the next 48 days.
- 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 2 of 575 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 48 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 78 / 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 80 / 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/bc-transit-kamloops/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.