GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

BC Transit (Hazelton, Kitimat, and Terrace)

Based on the feed this agency publishes

Service mode Bus

71.7 / 100

First scorecard for this agency

Catalogued in British Columbia, Canada.

Covers 343 daysAccessibility gapsRealtime not yet published

One BC Transit regional transit system feed for Hazelton, Kitimat, and Terrace; counted as one feed record.

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 5 hours ago; last changed 5 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

Fix 01

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

293 of 293 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

Fix 02

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

1102 of 1102 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

Fix 03

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.

  1. 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.

  2. 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.

  3. 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 343 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

Correctness80.0 / 100

The MobilityData validator flagged 4 kinds of issue across 36 instances (0 error, 36 warning, 0 informational).

Freshness100.0 / 100

Service data covers the next 343 days.

Rider experience37.5 / 100

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.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 13 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1A, 1B, 2, 3, 4, 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.

  • 51 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Sparks St at Park", "Kalum at Paul Clark Dr", "Kalum at Paul Clark 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.

Realtime qualityNot yet measured

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 data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • 11 (pink)
  • 12 (purple)
  • 13 (purple)
  • 14 (yellow)
  • 163 (black)
  • 164 (black)
  • 1A (gray)
  • 1B (orange)
  • 2 (teal)
  • 3 (yellow)
  • 31 (black)
  • 32 (black)
  • 4 (green)
  • 41 (brown)
  • 42 (gray)
  • 43 (pink)
  • 44 (gray)
  • 45 (teal)
  • 46 (orange)
  • 99 (gray)
Routes in BC Transit (Hazelton, Kitimat, and Terrace)'s feed
RouteTypeLine color
11 Terrace-Kitimat ConnectorBuspink
12 Kitamaat VillageBuspurple
13 KitsumkalumBuspurple
14 Gitaus/QueenswayBusyellow
163 Hazeltons/SmithersBusblack
164 Hazeltons/TerraceBusblack
1A Kitimat Route 1 ClockwiseBusgray
1B Kitimat Route 1 Counter ClockwiseBusorange
2 NechakoBusteal
3 KildalaBusyellow
31 GitseguklaBusblack
32 West ConnectorBusblack
4 CrosstownBusgreen
41 College/HalliwellBusbrown
42 City ShuttleBusgray
43 SouthsideBuspink
44 NorthsideBusgray
45 ThornhillBusteal
46 College ExpressBusorange
99 SpecialBusgray

This feed has 293 stops.

List every stop
  • Gitsaex St Mid Block
  • Lakelse at Skeena Mall
  • Haugland nearside Tetrault
  • Feeny farside Hwy 16
  • Feeny at Hwy 16
  • West Kalum Rd at Hwy 16
  • Kilby Road Loop
  • Kshish Street at Tsunyow St
  • Clark St at Paquette
  • Lakelse at 4655 Safeway
  • Kalum at Lazelle
  • Park Ave at Kalum
  • Park at Sparks
  • Lazelle at Eby
  • Kalum at Paul Clark Dr
  • Kalum at Paul Clark Dr
  • Kalum at Olson
  • Kalum at Olson
  • Kalum at Straume
  • Kalum at Straume
  • Sparks at Kerby
  • Sparks at Kerby
  • Halliwell at Sparks
  • Halliwell at Sparks
  • Halliwell at Benner
  • Halliwell at Benner
  • Halliwell at Munroe
  • Halliwell at Munroe
  • Thomas at Halliwell
  • Twedle at Terrace
  • Munroe at Twedle
  • Thomas at Twedle
  • Thomas at Twedle
  • Thomas at Hundal
  • Thomas at Hundal
  • McConnell at Cory
  • McConnell at Cory
  • McConnell at Marshall
  • McConnell at Marshall
  • McConnell at Floyd
  • McConnell at Floyd
  • Coast Mountain College
  • Bailey at McConnell
  • Bailey at Hallock
  • Bailey at Gordon
  • Mountain Vista at Eagle Pl
  • Mountain Vista at Floyd
  • Mountain Vista at 5328 Blk
  • Mountain Vista at Kalum Lake Rd
  • Lakelse at Atwood
  • Lakelse at Clinton
  • Apsley at Park
  • Johnstone at Birch
  • Pedrini at Maroney
  • Park Ave at Aquatic Centre
  • Sparks St at Park
  • Sparks at Loen
  • Sparks at Olson
  • Sparks at Hamer
  • Tuck at Sparks
  • Tuck at Eby
  • Tuck at Munroe
  • Munroe at Straume
  • Munroe at Olson
  • Walsh at Munroe
  • Walsh at 4934 Blk
  • Walsh at 4934 Blk
  • Lanfear at Thomas
  • Park at Brooks
  • Park at Kenney
  • Kenney at Lazelle
  • Lazelle at Kenney
  • Lazelle at Munroe
  • Lazelle at 4823 Blk
  • Eby at Park
  • Walsh at Sparks
  • Walsh at Eby
  • Walsh at 4818 Blk
  • Walsh at 4809 Blk
  • Walsh at 4826 Blk
  • Skeena at Haugland
  • Haugland at Skeena
  • Haugland at 5220 Blk
  • Braun at Agar
  • Agar at 5133 Blk
  • Agar at 5041 Blk
  • Kenney at Pohle
  • Keith at UNBC
  • Molitor at Haugland
  • Haugland at Eby
  • Haugland at 4616 Blk
  • Haugland at 4616 Blk
  • Kalum at Haugland
  • Kalum at Haugland
  • Kalum at Feeney
  • Kalum at Feeney
  • Feeney at Keefer
  • Feeney at Keefer
  • Pear at Weber
  • Pear at Graham
  • Graham at Tetrault
  • Graham at Eby
  • Graham at Beach
  • Kenney at Graham
  • Medeek at Kenney
  • Medeek at 5038 Blk
  • Medeek at Craig
  • Tuck Avenue Seniors Centre
  • Queensway at 1885 Blk
  • Queensway at 1885 Blk
  • Queensway at 4562 Blk
  • Queensway at Kirsch
  • Lowrie at Maple
  • Beaver at Copper
  • Beaver at 4636 Blk
  • Queensway at 4421 Blk
  • Queensway at 4402 Blk
  • Woeste at Lodgepole
  • Marion at Lodgepole
  • Hwy 37 at MacKenzie
  • Hwy 37 at MacKenzie
  • Terminal at Bristol
  • Old Lakelse at Paquette
  • Old Lakelse at 3932 Blk
  • Clark at Old Lakelse
  • Muller at Clark
  • Century at Pine
  • Paquette at Century
  • Otter at Copper
  • Thornhill at Old Lakelse
  • Aspen at Laurel
  • Hemlock at Aspen
  • Hemlock at Hawthorne
  • Hemlock at Larch
  • Furlong at Parameter
  • Edlund at McNeil
  • Walker at Edlund
  • Dobbie at 3867 Block
  • River at 3747 Blk
  • River at 3413 Blk
  • River and Clark
  • River at Wren
  • Skeena Dr in Gossen Subdivsion
  • Clark at Paquette (NB)
  • Clark at Paquette (SB)
  • Paquette at Thornhill Ftg Rd (WB)
  • Thornhill Frntg Rd at Seaton
  • Coast Mountain College
  • Ksyen Regional Hospital
  • Kitimat City Centre
  • S Lahakas at Haisla
  • S Lahakas at 780 Blk
  • S Lahakas at 825 Blk
  • S Lahakas at 825 Blk
  • S Lahakas at Wakashan
  • S Lahakas at Wakashan
  • S Lahakas at Kitimat Hospital
  • Quatsino at S Lahakas
  • Wakashan at Library
  • Wakashan at 948 Blk
  • Wakashan at Tsimishian
  • Tsimshian at Wakashan
  • Quatsino at Loganberry
  • Quatsino at Cranberry
  • E Columbia at Quatsino
  • E Columbia at Stikine
  • E Columbia at Saquenay
  • E Columbia at Kootenay
  • E Columbia at Kitlope
  • E Columbia at Capilano
  • E Columbia at Babine
  • W Columbia at Dease
  • W Columbia at A Rd
  • W Columbia at Riverlodge Rec Centre
  • Kuldo at Dease
  • Kuldo at Konigus
  • Kuldo at Liard
  • Kuldo at Nadina
  • Kuldo at Omenica
  • Albatross at Kingfisher
  • Albatross at 1530 Blk
  • Albatross at Cormorant
  • Albatross at 1308 Blk
  • N Lahakas at Bittern
  • N Lahakas at Bunting
  • N Lahakas at Cormorant
  • N Lahakas at Cormorant
  • N Lahakas at Gyrfalcon
  • N Lahakas at Gyrfalcon
  • N Lahakas at Eagle
  • N Lahakas at Eagle
  • N Lahakas at Egret
  • N Lahakas at Egret
  • Nalabila at N Lahakas
  • Nalabila at N Lahakas
  • Tweedsmuir at Farrow
  • Tweedsmuir at Farrow
  • Tweedsmuir at Gwyn
  • Tweedsmuir at Gwyn
  • Tweedsmuir at 1220 Blk
  • Tweedsmuir at Dunn
  • Tweedsmuir at 1134 Blk
  • Tweedsmuir at 1135 Blk
  • Tweedsmuir at Davy
  • Tweedsmuir at Davy
  • Nalabila at Duncan
  • Nalabila at Duncan
  • Alexander at Anderson
  • Alexander at Anderson
  • Alexander at Baxter
  • Alexander at Baker
  • Alexander at Bartholomew
  • Alexander at Braun
  • Alexander at Charles
  • Alexander at Charles
  • Alexander at Banyay
  • Alexander at 1352 Blk
  • Alexander at 1352 Blk
  • Kingfisher at Currie
  • Kingfisher at Margetts
  • Kingfisher at Stein
  • Kingfisher at Oersted
  • Kingfisher at White
  • Kingfisher at Whittlesey
  • Kingfisher at Wohler
  • Kingfisher at Meldrum
  • Kingfisher at Nalabila
  • Kingfisher at Wohler
  • Kingfisher at Heron
  • Kingfisher at Heron
  • Kingfisher at Hawk
  • Kingfisher at Mallard
  • Kingfisher at 1220 Blk
  • Kingfisher at Oriole
  • Gyrfalcon at Kingfisher
  • Gyrfalcon at Grebe
  • Gyrfalcon at Gander
  • Gyrfalcon at N Lahakas
  • Gyrfalcon at Gander
  • Gyrfalcon at Grebe
  • Nalabia at Swan
  • Nalabila at Swan
  • Nalabila at Starling
  • Nalabila at Swallow
  • Nalabila at Teal
  • Nalabila at Wren
  • Haisla at Kitamaat Village Rd
  • Haisla at 1631 Blk Hillcrest Pl
  • Haisla at Ptarmigan
  • Haisla at 1211 Blk Haisla Crt
  • and 43 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
  • Warning1102 instances

    1102 of 1102 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

  • Warning293 instances

    293 of 293 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

  • Warning20 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

  • Warning13 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

  • 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

  • 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

  • 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

  • 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

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 343 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 293 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 343 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.

BC Transit (Hazelton, Kitimat, and Terrace) GTFS data quality grade: C

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-hazelton-kitimat-terrace/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.