Feed status · checked 2026-07-19
BC Transit (Quesnel 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 3 hours ago; last changed 3 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
141 of 141 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
98 of 98 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 165 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 22 instances (0 error, 22 warning, 0 informational).
Service data covers the next 165 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.
1 accessibility depth signal
133 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("St Laurent Ave at Reid St", "Kinchant St at Barlow Ave", "Kinchant St at Carson 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 (black)
- 1R (black)
- 2 (black)
- 2A (black)
- 2B (black)
- 3 (black)
- 30 (black)
- 31 (black)
| Route | Type | Line color |
|---|---|---|
| 1 West Quesnel | Bus | black |
| 1R West Quesnel Reverse Route | Bus | black |
| 2 Red Bluff | Bus | black |
| 2A Red Bluff Via Carson Sub | Bus | black |
| 2B Red Bluff Via South Hills | Bus | black |
| 3 North Fraser | Bus | black |
| 30 Wells | Bus | black |
| 31 Nazko | Bus | black |
This feed has 141 stops.
List every stop
- Robertson Ave at Rolph St
- Robertson Ave at Reynard St
- Robertson Ave at Winder St
- Anderson Dr at Wade Ave
- Anderson Dr at Avery Ave
- Doherty Dr at Willis St
- Doherty Dr at Warden St
- Ritson Ave at Rolph St
- Rolph St at Roddis Dr
- Marsh Dr at Baker Dr
- Lewis Dr at Couldwell Ave
- 300 Blk Lewis Dr
- Lewis Dr at Beaubien Ave
- Lewis Dr at Palmer St
- Lewis Dr at Pierce St
- Dawson St at Lewis Dr
- Patchett St at Pentland Cres
- 500 Blk Patchett St
- Flamingo St at Pentland Cres
- Lark Ave at Pinchbeck St
- Abbott Dr at Blair St
- 900 Blk Abbott Dr
- Hartley St at English Ave
- English Ave at Baker Dr
- Baker Dr at Hill St
- Harper Ave at Hartley St
- Baker Dr at Hill St
- Elliott St at Early Ave
- Elliott St at English Ave
- N Fraser Dr at Foster Ave
- N Fraser Dr at Felker Ave
- N Fraser Dr Turnaround
- N Fraser Dr at Felker Ave
- N Fraser Dr at River-Walk Park
- N Fraser Dr at Fuller Ave
- 300 Blk N Fraser Dr
- Early Ave at Elliott St
- St Laurent Ave at Reid St
- St Laurent Ave at Vaughan St
- St Laurent Ave at Callanan St
- St Laurent Ave at Wilson St
- St Laurent Ave at Jones St
- Jones St at Shepherd Ave
- Wilson St at Shepherd Ave
- Wilson St at McNaughton Ave
- Wilson St at Bowron Ave
- Bowron Ave at Callanan St
- McNaughton Ave at Reid St
- G R Baker Memorial Hospital
- Kinchant St at Barlow Ave
- Kinchant St at Carson Ave
- G R Baker Memorial Hospital Old Entrance
- Johnston Ave at Yorston Ave
- Johnston Ave at Gardner St
- Johnston Ave at Leonard St
- Johnston Ave at Lowe St
- North Star Rd at Quesnel Rec Ctr
- North Star Rd at Campus Way
- North Star Rd at Campus Way
- North Star Rd at Quesnel Rec Ctr
- Nadeau St at Nagra Ave
- Nadeau St at Norman St
- Nason St at Nadeau St
- 600 Blk Nason St
- Nickel Ridge Ave at Netterfield Ave
- Johnston Ave at Lowe St
- Johnston Ave at Graham Ave
- Johnston Ave at Gardner St
- Johnston Ave at Yorston Ave
- Westland Rd at Hydraulic Rd
- Westland Rd at Gassoff Rd
- Westland Rd at Richardson Rd
- 500 Blk Westland Rd
- Westland Rd at Westland Close
- Dennis Rd at Westland Rd
- 500 Blk Dennis Rd
- 400 Blk Dennis Rd
- Gassoff Rd at Ryan Rd
- 2300 Blk Gassoff Rd
- Westland Rd at Hydraulic Rd
- Hydraulic Rd at Westland Rd
- Valhalla Rd at Gassoff Rd
- Valhalla Rd at Gassoff Rd
- Hydraulic Rd at Juniper Rd
- Hydraulic Rd at Coach Rd
- Hydraulic Rd at Dragon Lake Elementary
- Phillips Rd at Neighbour Rd
- 300 Blk Phillips Rd S
- 200 Blk Phillips Rd S
- Gavlin Rd at Brears Rd
- 100 Blk Coach Rd S
- Hydraulic Rd at Juniper Rd
- 500 Blk Juniper Rd
- 600 Blk Newman Rd
- Newman Rd at Balsam Ave
- South Quesnel Wal-Mart
- South Quesnel No Frills
- 1000 Blk Maple Heights Rd
- 2100 Blk Tamarack Ave
- Bass Rd at Tamarack Rd
- 1200 Blk Bass Rd
- 1300 Blk Bass Rd
- Lust Rd at Arbutus Rd
- Lust Rd at Chief Dominic Rd
- Lust Rd at Hausaman Rd
- 1200 Blk Lust Rd
- Lust Rd at Maple Dr
- Spruce St at Maple Dr
- Spruce St at Balsam Ave
- 1900 Blk Balsam Ave
- Kube Rd at Balsam Ave
- Kube Rd at Maple Dr
- Maple Dr at Maple Heights Rd
- Elm St at Maple Dr
- 600 Blk Elm St
- Elm St at Cedar Ave
- 2200 Blk Cedar Ave
- 500 Blk Juniper Rd
- 800 Blk Rita Rd
- Kinchant St at McNaughton Ave
- N Fraser Dr at Elliott St
- Nazko Band Office
- Nazko Rd at Spruce Ave
- Nazko Rd at Lakeview Dr
- Nazko Community Centre
- Mildred Ave at Wells Elementary School
- Burnett Ave at Pooley St
- Burnett Ave
- Pooley St at Sanders Ave
- Hwy 26 at Legion Dr
- Lowhee Dr at Hwy 26
- 3900 Blk Solibakke Dr
- Ski Hill Rd at Solibakke Dr
- Hong St at Solibakke Dr
- Legion Dr at Solibakke Dr
- Legion Dr at Goldquartz Dr
- Barkerville Visitor Centre
- Front St at Johnston Bridge
- Front St at Johnston Bridge
- Marsh Dr at West Park Mall
- Quesnel Transit Centre
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
- Warning141 instances
141 of 141 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)
- Warning98 instances
98 of 98 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)
- Warning12 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)
- Warning8 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)
- 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
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
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 165 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.
- 1 of 141 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 165 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 80 / 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 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-quesnel/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.