Feed status · checked 2026-07-19
BC Transit (Comox Valley 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
267 of 267 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
548 of 548 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 49 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 5 kinds of issue across 115 instances (0 error, 85 warning, 30 informational).
Service data covers the next 49 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, 7, 8, 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.
244 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("5th St at Simms Park", "Old Island Hwy at Puntledge Rd", "Anderton Ave at 3rd St", 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 (brown)
- 11 (purple)
- 12 (gray)
- 13 (pink)
- 14 (gray)
- 15 (yellow)
- 2 (gray)
- 20 (purple)
- 3 (orange)
- 4 (teal)
- 5 (red)
- 6 (purple)
- 7 (yellow)
- 8 (pink)
- 99 (green)
| Route | Type | Line color |
|---|---|---|
| 1 Comox Mall / Anfield Centre via N.I.C. | Bus | teal |
| 10 Fanny Bay / Deep Bay / Downtown Courtenay | Bus | brown |
| 11 Airport via Powell R. Ferry / Downtown | Bus | purple |
| 12 Oyster River / Downtown Courtenay | Bus | gray |
| 13 Merville-Seal Bay Shuttle | Bus | pink |
| 14 Union Bay Shuttle | Bus | gray |
| 15 Comox Mall via Back Rd/Aquatic Centre via Back Rd | Bus | yellow |
| 2 Cumberland / Anfield Centre | Bus | gray |
| 20 Cumberland via Royston | Bus | purple |
| 3 Comox Local | Bus | orange |
| 4 Driftwood Mall / Comox Mall via Comox Rd | Bus | teal |
| 5 Vanier | Bus | red |
| 6 Uplands | Bus | purple |
| 7 Arden | Bus | yellow |
| 8 Downtown / Anfield Centre | Bus | pink |
| 99 VMP Connector | Bus | green |
This feed has 267 stops.
List every stop
- Clarkson Ave at Eyre Rd
- Hwy 19A at White Rd
- Hwy 19A at Hayward Ave
- Hwy 19A at McLeod Rd
- Hwy 19A at Buckley Bay Rd
- Hwy 19A at Herondale Rd
- Hayward Ave at Hwy 19A
- Marine Dr at Greig Ave
- Hwy 19A at Hilton Rd
- Comox Rd at Scott Rd
- 2700 Blk Comox Rd
- 2700 Blk Comox Rd
- Ryan Rd E at Little River Rd
- Deep Bay Marina
- Veterans Memorial Pky at Caledon Cres
- Lerwick Rd at Waters Pl
- Comox Valley Senior's Village
- Lerwick Rd at Waters Pl
- Ryan Rd at Back Rd
- Hwy 19A at Buckley Bay Rd
- Hwy 19A at Garvin Rd
- Hwy 19A at Spindrift Rd
- Hwy 19A at Gartley Rd
- Comox Rd at Scott Rd
- Anderton Rd at Greenwood Cres
- Bates Rd at Seal Bay Park
- Tammy Rd at MacAuley Rd
- Miracle Beach Dr at Hwy 19A
- Bates Rd at Coleman Rd
- Merville Rd at Hwy 19A
- Hwy 19A at Spindrift Rd
- Hwy 19A at Union Bay
- Hwy 19A at Royston Rd
- Anderton Rd at Galleon Way
- Comox Valley Sports Centre
- Cliffe Ave at 8th St
- Cliffe Ave at 11th St
- Downtown Courtenay Bay C
- Comox Mall Bay B
- Anderton Rd at Robb Ave
- Rodello St at Fairbairn Ave
- Beaufort Ave at Church St
- Beaufort Ave at Wilcox St
- Beaufort Ave at Nordin St
- Balmoral Ave at Anderton Park
- Balmoral Ave at Pritchard Rd
- Fitzgerald Ave at 19th St
- Hwy 19A at Krueger Rd
- Hwy 19A at Black Creek Rd
- Hwy 19A at Black Creek Rd
- Comox Rd at Queneesh Rd
- Hwy 19A at Virginia Dr
- Hwy 19A at Virginia Dr
- Woods Ave at 2nd St
- Hwy 19A at Ships Point Rd
- Torrence Rd at Casey Rd
- Clarkson Ave at Maple Dr
- Clarkson Ave at Beach Cres
- Back Rd at Tatpoos Rd
- Back Rd at Tatpoos Rd
- Back Rd at Sahtloot Cres
- Back Rd at Sahtloot Cres
- Back Rd at McDonald Rd
- Back Rd at McDonald Rd
- Back Rd at 10th St E
- Cowichan Ave at 5th St E
- Menzies Ave at 2nd St
- McPhee at 11th St
- Farmers Market
- Farmers Market
- Comox Valley Senior's Village
- McPhee at 13th St
- McPhee at 17th St
- Piercy at 18th St
- McPhee at 16th St
- Cumberland at 9th
- Cumberland at Lewis
- Downtown Courtenay Bay B
- Fitzgerald Ave at 8th St
- Fitzgerald Ave at 18th St
- Fitzgerald Ave at 21st St
- Fitzgerald Ave at 23rd St
- Anfield Centre
- Kilpatrick Ave at 30th St
- Kilpatrick Ave at 29th St
- Driftwood Mall Bay A
- Fitzgerald Ave at 21st St
- Fitzgerald Ave at 16th St
- Fitzgerald Ave at 13th St
- Fitzgerald Ave at 8th St
- Fitzgerald Ave at 5th St
- Royston Rd at Carlisle Lane
- Dunsmuir Ave at 6th St
- Dunsmuir Ave at 4th St
- Dunsmuir Ave at 1st St
- Egremont Rd at Dunsmuir Ave
- Egremont Rd at Ulverston Ave
- Windermere Ave at 1st St
- Cumberland Rd at Stockand Lane
- Old Island Hwy at Puntledge Rd
- Ryan Rd at Puntledge Rd
- 1000 Blk Ryan Rd
- NIC Campus
- Lerwick Rd at Malahat Dr
- Lerwick Rd at Valley View Dr
- Lerwick Rd at Blue Jay Pl
- Guthrie Rd at Aspen Grove Centre
- Guthrie Rd at Stadacona Dr
- Anderton Rd at Guthrie Rd
- Anderton Rd at Bolt Ave
- Comox Ave at Stewart St
- Comox Mall Bay A
- Comox Ave at Ellis St
- Anderton Rd at Buena Vista Ave
- Anderton Rd at Robb Ave
- Robb Ave at Thistle Crt
- Robb Ave at Rodello St
- Aitken St at McKenzie Ave
- Downey Ave at Aitken St
- Downey Ave at Rodello St
- Comox Ave at St Joseph's Hospital
- Comox Rd at Queneesh Rd
- Cliffe Ave at 19th St
- Cliffe Ave at 19th St
- Comox Rd at St Joseph's Hospital
- Anderton Rd at McKenzie Ave
- Anderton Rd at Buena Vista Ave
- Comox Ave at Ellis St
- Balmoral Ave at Donovan Dr
- Torrence Rd at Albatross Ave
- Torrence Rd at Noel Ave
- Torrence Rd at Hillside Ave
- Torrence Rd at Ridgemount Dr
- Guthrie Rd at Skeena Dr
- Pritchard Rd at Guthrie Rd
- Pritchard Rd at Skeena Dr
- Pritchard Rd at Noel Ave
- Pritchard Rd at Dogwood Ave
- Robb Ave at Stewart St
- 1700 Blk Robb Ave
- Robb Ave at Megin Way
- Church St at Hemlock Ave
- Noel Ave at Holly Pl
- Anderton Rd at Bolt Ave
- Anderton Rd at Guthrie Rd
- Guthrie Rd at Stadacona Dr
- Guthrie Rd at Aspen Rd
- Lerwick Rd at Inverclyde Way
- 2100 Blk Lerwick Rd
- 2100 Blk Lerwick Rd
- Lerwick Rd at Idiens Way
- Lerwick Rd at Ryan Rd
- 800 Blk Ryan Rd
- Ryan Rd at Puntledge Rd
- Old Island Hwy at Puntledge Rd
- 5th St at Simms Park
- Cliffe Ave at 11th St
- Cliffe Ave at 14th St
- Back Rd at Tunner Dr
- Sitka Ave at 10th St E
- Sitka Ave at Malahat Dr
- Thorpe Ave at Malahat Dr
- Thorpe Ave at Griffin Dr
- Valley View Dr at Partridge Pl
- Mission Rd at Walbran Dr
- Mission Rd at Shetland Pl
- Muir Rd at Anna Pl
- Muir Rd at Cruickshank Ave
- McLauchlin Dr at MacIntyre Ave
- McLauchlin Dr at Panorama Pl
- Centennial Dr at Back Rd
- 5th St at Leighton Ave
- Menzies Ave at 3rd St
- 1st St at Urquhart Ave
- 1st St at Embleton Cres
- 1st St at Mitchell Pl
- Embleton Cres at Rod and Gun Rd
- Woods Ave at 2nd St
- Woods Ave at Martin Pl
- 5th St at Willemar Ave
- 2100 Blk 20th St
- Willemar Ave at 20th St
- 21st St at Urquhart Ave
- 21st St at Stewart Ave
- 2300 Blk Piercy Ave
- Piercy Ave at 26th St
- 26th St at Piercy Ave
- 26th St at Kilpatrick Ave
- Menzies Ave at 8th St
- Pidcock Ave at Bryan Way
- 10th St at Willemar Ave
- 10th St at Willemar Ave
- 10th St at Stewart Ave
- Cumberland Rd at Piercy Ave
- Cumberland Rd at 16th St
- 1800 Blk Willemar Ave
- 26th St at Kilpatrick Ave
- Piercy Ave at 21st St
- Piercy Ave at 18th St
- 17th St at Willemar Ave
- Cumberland Rd at 16th St
- Cumberland Rd at Piercy Ave
- Piercy Ave at Cumberland Rd
- 10th St at Stewart Ave
- 5th St at Urquhart Ave
- 5th St at Kilpatrick Ave
- Hwy 19A at Russell St
- Hwy 19A at Ships Point Rd
- Hwy 19A at Fanny Bay
- Hwy 19A at Kingfisher Resort
- Ryan Rd at Crown Isle Plaza
- Little River Ferry Terminal
- Military Row at Ryan Rd E
- Military Row at Rose Ave
- Comox Valley Airport
- 10th St E at Glen Urquhart Dr
- Back Rd at 6th St E
- Arden Rd at 1st St
- Cliffe Ave at Mansfield Dr
- 2000 Blk Lake Trail Rd
- McLauchlin Dr at Dingwall Rd
- 2200 Blk Embleton Cres
- Embleton Cres at Osprey Pl
- 20th St at Cousins Ave
- Back Rd at 10th St E
- Fitzgerald Ave at 13th St
- Ryan Rd at Crown Isle Blvd
- NIC / Aquatic Centre Bay B
- Lerwick Rd at Ryan Rd
- Lerwick Rd at Malahat Dr
- Cowichan Ave at 4th St E
- Valley View Dr at Lerwick Rd
- Hwy 19A at Royston Rd
- Downtown Courtenay Bay A
- Fitzgerald Ave at 5th St
- Anderton Ave at 3rd St
- Cliffe Ave at 17th St
- 1st St at Embleton Cres
- Vanier Dr at Comox Valley Sports Ctr
- Cliffe Ave at Mansfield Dr
- 1st St at Rydal Ave
- Egremont Rd at Rydal Ave
- 3rd St at Kendal Ave
- 4th St at Ulverston Ave
- Ulverston Ave at 7th St
- 7th St at Penrith Ave
- Royston Rd at Ulverston Ave
- Cumberland Rd at Stockand Lane
- Croydon Rd at Upland Rd
- Fitzgerald Ave at 16th St
- and 17 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
9 findings, ordered by severity.
Show every finding
- Warning548 instances
548 of 548 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)
- Warning267 instances
267 of 267 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)
- Warning67 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)
- Warning16 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)
- Info30 instances
Unsorted stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules 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 49 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 267 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 49 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 77 / 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 82 / 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-comox-valley/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.