Feed status · checked 2026-07-19
BC Transit (Bulkley-Nechako and Prince George Transit Systems)
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 9 hours ago; last changed 9 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
492 of 492 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
1004 of 1004 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 57 instances (0 error, 57 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 (5, 10, 11, 15, 16, 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.
443 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("N Nechako Rd at Arend Dr", "N Nechako Rd at Churchill Rd", "Tyner Blvd at University Heights Dr", 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 (orange)
- 11 (teal)
- 15 (green)
- 16 (pink)
- 161 (black)
- 162 (black)
- 19 (yellow)
- 46 (gray)
- 47 (pink)
- 5 (gray)
- 55 (gray)
- 88 (teal)
- 89 (orange)
- 91 (gray)
| Route | Type | Line color |
|---|---|---|
| 1 Heritage | Bus | teal |
| 10 Downtown/Spruceland | Bus | orange |
| 11 Heritage | Bus | teal |
| 15 UNBC/Downtown | Bus | green |
| 16 UNBC/College Heights | Bus | pink |
| 161 Prince George / Burns Lake | Bus | black |
| 162 Smithers / Burns Lake | Bus | black |
| 19 UNBC/Westgate | Bus | yellow |
| 46 Queensway | Bus | gray |
| 47 Reverse Queensway | Bus | pink |
| 5 Victoria/5th | Bus | gray |
| 55 5th/Victoria | Bus | gray |
| 88 Westgate | Bus | teal |
| 89 Hart | Bus | orange |
| 91 Spruceland/Hart | Bus | gray |
This feed has 492 stops.
List every stop
- Downtown Exch Bay C
- Downtown Exch Bay B
- Downtown Exch Bay A
- Nicholson Exch Bay D
- Nicholson Exch Bay B
- Nicholson Exch Bay C
- Domano Blvd at Moriarty Cres
- Domano Blvd at McGill Cres
- Hart Exchange Bay A
- Pine Centre Exch Bay B
- Pine Centre Exch Bay A
- Spruceland Exch Bay B
- Spruceland Exch Bay D
- Spruceland Exch Bay C
- UNBC Exch Bay A
- Westgate Exch Bay A
- College Rd at CNC
- College Rd at CNC
- Nicholson St at 18th Ave
- Ospika Blvd at Campbell Ave
- Ospika Blvd at Docherty Ave
- Nicholson Exch Bay A
- Carney St at Ellison Dr
- Winnipeg St at Yew St
- 17th Ave at Tamarack St
- 17th Ave at Upland St
- Quebec St at 2nd Ave
- 15th Ave at Ingledew St
- Gorse St at 15th Ave
- Gorse St at 20th Ave
- Queensway at 15th Ave
- Nicholson St at 18th Ave
- La Salle Ave at Queensway
- La Salle Ave at Lillooet St
- Pilot St at 5th Ave
- Pilot St at Eaglenest Cres
- Queensway at Royal Cres
- Range Rd at Wiebe Rd
- Ferry Ave at Spruce St
- Ferry Ave at Clapperton St
- Vance Rd at Blakley Rd
- 3900 Blk Wiebe Rd
- Malaspina Ave at Newcastle Cres
- Malaspina Ave at Loyola Cres
- Loyola Dr at Rochester Cres
- Gladstone Dr at Loyola Dr
- Gladstone Dr at Jean De Brebeuf Cres
- Gladstone Dr at Hartford Cres
- Simon Fraser Ave at Fairmont Cres
- Tyner Blvd at Baker Rd
- Tyner Blvd at University Heights Dr
- Tyner Blvd at University Heights Dr
- 5th Ave at Tabor Blvd
- 5th Ave at Lacoma St
- 15th Ave at Foothills Blvd
- Simon Fraser Ave at Delhi Pl
- 15th Ave at Nation Cres
- Simon Fraser Ave at Acadia Pl
- Massey Dr at Westwood Dr
- 15th Ave at Central St E
- 15th Ave at Gillett St
- 15th Ave at Irwin St
- 15th Ave at Ewert St
- 15th Ave at Carney St
- 15th Ave at Spruce St
- 15th Ave at Alward St - UHNBC
- Ahbau St at 8th Ave
- 15th Ave at Tabor Blvd
- 15th Ave at Jarvis St
- 15th Ave at Drummond St
- 15th Ave at Nation Cres
- 5th Ave at Kerry St
- 5th Ave at Ruggles St
- 15th Ave at Liard Dr
- 15th Ave at Central St W
- 15th Ave at Johnson St
- 15th Ave at Gillett St
- 15th Ave at Ewert St
- 15th Ave at Carney St
- 15th Ave at Alward St - UHNBC
- 15th Ave at Spruce St
- 15th Ave at Victoria St
- Dominion St at 6th Ave
- Dominion St at 4th Ave
- Dominion St at 2nd Ave
- 1st Ave at Quebec St
- Victoria St at 3rd Ave
- Moyie St at Proppe Lane
- Victoria St at 5th Ave
- Ahbau St at 5th Ave
- 5th Ave at Nicholson St
- 5th Ave at Patterson St
- 5th Ave at Quinn St
- 5th Ave at Ospika Blvd
- 5th Ave at Brigade Dr
- 5th Ave at Voyageur Dr
- 5th Ave at Tabor Blvd
- Pilot St at 5th Ave
- Pilot St at Selwyn Cres
- Ochakwin Cres at Robson Ave
- Foothills Blvd at Cascade Ave
- University Way at Foothills Blvd
- 5900 Blk Dakelh-Ti
- Foothills Blvd at 15th Ave
- Foothills Blvd at Limestone Cres
- Foothills Blvd at Ochakwin Cres
- Pilot St at Ochakwin Cres
- Victoria St at Strathcona Ave
- Tabor Blvd at Jackpine Ave
- 5th Ave at Douglas St
- 5th Ave at Burden St
- 5th Ave at Tabor Blvd
- Victoria St at 20th Ave
- Victoria St at 17th Ave
- Victoria St at 11th Ave
- Victoria St at 9th Ave
- Victoria St at 7th Ave
- 4th Ave at Edmonton St
- 5th Ave at Melville Ave
- 5th Ave at Wainwright St
- 6th Ave at Alward St
- 5th Ave at Burden St
- Victoria St at 6th Ave
- Victoria St at 9th Ave
- Victoria St at 11th Ave
- 5th Ave at Douglas St
- 5th Ave at Freeman St
- N Nechako Rd at Aspen Lane
- 5th Ave at Wainwright St
- 5th Ave at Melville Ave
- 3rd Ave at Winnipeg St
- 4th Ave at Prince Rupert St
- 5th Ave at Harper St
- 5th Ave at Johnson St
- Berwick Dr at Langley Cres
- Highland Dr at Berwick Dr
- Nixon Cres at Berwick Dr
- Wildwood Cres at Ridgeview Dr
- Ospika Blvd at CN Centre
- 3rd Ave at Vancouver St
- Victoria St at Porter Ave
- Pearson Ave at Upland St
- Victoria St at Diefenbaker Dr
- Killarney Dr at Wildwood Cres
- Wildwood Cres at Sussex Lane
- Killarney Dr at Carleton Lane
- Glengarry Rd at Killarney Dr
- Wildwood Cres at Carlisle Way
- Ridgeview Dr at McKenney Cres
- Kelly Rd S at Handlen Rd
- Hwy 97 at Bellamy Rd
- Croft Rd at Winslow Dr
- 5th Ave at Freeman St
- Croft Rd at Hepting Rd
- Cook Cres at Birchwood Trailer Park
- Hwy 97 at Monterey Rd
- Hwy 97 at Collins Rd
- Hwy 97 at Noranda Rd E
- Hwy 97 at Kenworth Rd E
- Eden Dr at Langer Cres
- Foothills Blvd at Glen Shee Rd
- Austin Rd E at Driftwood Rd
- Austin Rd E at Hwy 97
- Eden Dr at Adam Dr
- Eden Dr at Glenview Dr
- Eden Dr at Dagg Rd
- Dagg Rd at Eden Dr
- Dagg Rd at Rundstrom Rd
- Weisbrod Rd at Dagg Rd
- Hwy 97 at Austin Rd W
- Lethbridge St at UHNBC
- Edmonton St at 15th Ave - UHNBC
- 4th Ave at Brunswick St
- 4th Ave at Vancouver St
- 10th Ave at Vancouver St
- Winnipeg St at 13th Ave
- Lethbridge St at UHNBC
- Laurier Cres at Lethbridge St
- 10th Ave at Alward St
- 10th Ave at Douglas St
- 10th Ave at Freeman St
- 10th Ave at Harper St
- 10th Ave at Johnson St
- Ahbau St at Rainbow Dr
- Upland St at Abbott Cres
- Upland St at Emmet Ave
- Upland St at Rebman Cres
- Ferry Ave at Lansdowne Rd
- Ferry Ave at Hwy 16
- Ferry Ave at Westwood Dr
- Ferry Ave at Melody Cres
- Ospika Blvd at James Dr
- Ospika Blvd at Christopher Cres
- Ospika Blvd at Gould Cres
- Ospika Blvd at Massey Dr
- Massey Dr at Vanier Dr
- Massey Dr at Ospika Blvd
- Ospika Blvd at Dufferin Ave
- Ospika Blvd at Pinewood Ave
- Ospika Blvd at Ferry Ave
- Ferry Ave at Westwood Dr
- Ferry Ave at Recplace Dr
- Lansdowne Rd at Runnalls Ave
- Lansdowne Rd at Sinclair Rd
- Ferry Ave at Upland St
- Upland St at McKenzie Ave
- Ospika Blvd at Forest Ave
- Lansdowne Rd at McInnis Ave
- Upland St at Rebman Cres
- 5th Ave at Patterson St
- 5th Ave at Nicholson St
- Simon Fraser Ave at Caledonia Cres
- Simon Fraser Ave at Rideau Dr
- Simon Fraser Ave at Trent Dr
- Simon Fraser Ave at Cowart Rd
- Eton Ave at Simon Fraser Ave
- Eton Ave at Cambridge Rd
- McGill Cres at Eton Ave
- McGill Cres at Monahan Cres
- Marleau Rd at Lalonde Rd
- 17th Ave at Upland St
- Spruce St at 15th Ave
- Queensway at 15th Ave
- 15th Ave at Ingledew St
- Gorse St at 15th Ave
- Gorse St at 20th Ave
- 20th Ave at Gorse St
- 20th Ave at Cuddie Cres
- 17th Ave at Larch St
- 17th Ave at Queensway
- Queensway at 20th Ave
- Queensway at Houston Lane
- Queensway at La Salle Ave
- Queensway at Quadrant Cres
- Ferry Ave at Williams Cres
- Westwood Dr at Andres Rd
- Bear Rd at Aldeen Rd
- Massey Dr at Griffiths Ave - Stadium
- 2900 Blk Griffiths Ave
- Massey Dr at Del Laverdure Way - Stadium
- Westwood Dr at John McInnis Secondary
- Westwood Dr at Merritt Rd
- Bear Rd at Westgate Ave
- Ospika Blvd N at Blair Cres
- Ospika Blvd N at McIntyre Cres
- Ospika Blvd N at McRae Ave
- Ospika Blvd at Nugget Ave
- Ospika Blvd at Pioneer Ave
- Ospika Blvd at Pioneer Ave
- Ospika Blvd at 2nd Ave
- and 242 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
- Warning1004 instances
1004 of 1004 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)
- Warning492 instances
492 of 492 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)
- Warning40 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)
- Warning15 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 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.
- 1 of 492 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 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 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-bulkley-nechako-prince-george/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.