Feed status · checked 2026-07-19
BC Transit (Sunshine Coast 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 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
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
300 of 300 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
342 of 342 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 50 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 31 instances (0 error, 19 warning, 12 informational).
Service data covers the next 50 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
281 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Cowrie St at Trail Ave", "Cowrie St at Trail Ave", "Trail Ave at Spindrift 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 (black)
- 2 (black)
- 3 (black)
- 4 (black)
- 90 (black)
| Route | Type | Line color |
|---|---|---|
| 1 Sechelt-Gibsons/Langdale Ferry | Bus | black |
| 2 West Sechelt | Bus | black |
| 3 Sechelt Arena | Bus | black |
| 4 Halfmoon Bay | Bus | black |
| 90 Sechelt-Gibsons/Langdale Ferry Express | Bus | black |
This feed has 300 stops.
List every stop
- Norwest Bay Rd at Nickerson Rd
- Nickerson Rd at Oracle Rd
- Nickerson Rd at Tyler Rd
- Tyler a Rd at Tower Rd
- Emerson Rd at Lloyde Ave
- Hwy 101 at Sechelt Hospital
- Ocean Ave at Mermaid St
- Fairway Ave at Ripple Way
- Hwy 101 at Matukwum Lane North
- Gower Point Rd at South Fletcher Rd
- North Rd at Boyle Rd
- Mercer Rd at Secret Cove Rd
- Harbour Way at Lookout Ave
- Solar Rd at Field Rd
- Hwy 101 at Oceanview Dr
- North Rd at Chamberlin Rd
- North Rd at Boyle Rd
- North Rd at Bridgeman Rd
- North Rd at Twin Isles Dr
- Cowrie St at Clayton Rd
- North Rd at Marine Dr
- North Rd at St Andrews Rd
- North Rd at Bridgeman Rd
- North Rd at Chamberlin Rd
- North Rd at Stewart Rd
- Tower Road Loop
- Cowrie St at Peregrine Cres
- North Rd at Reed Rd
- Dolphin St at Inlet Ave
- Marlene Rd at Beach Ave
- Marlene Rd at Spruce Rd
- Hwy 101 at Westley Rd
- Hwy 101 at Nestman Rd
- Shorncliffe Ave at Barnacle St
- Mason Rd at Jasper Rd
- Hwy 101 at Sea Fiddler Rd
- Hwy 101 at Trail Island Dr
- Redrooffs Rd at Frances Rd
- 8300 Block Redrooffs Rd
- 8600 Block Redrooffs Rd
- 9000 Block Redrooffs Rd
- Mercer Rd at Hwy 101
- Derby Rd at Granite Rd
- Field Rd at Gun Club Rd
- Field Rd at Gun Club Rd
- Field Rd at Wilson Rd
- Field Rd at Wilson Rd
- North Rd at Seacot Way
- North Rd at Marine Dr
- Gibsons Way at Bals Lane
- Marine Dr at Seaview Lane
- Marine Dr at Harvey Rd
- 1200 Block Marine Dr
- North Rd at Cemetery Rd
- Field Rd at Hwy 101
- Lower Rd at Roberts Creek Rd
- Pratt Rd at Hwy 101
- Redrooffs Rd at Annex Rd
- Derby Rd at Cowrie St
- Hwy 101 at Joe Rd
- Hwy 101 at Orange Rd
- Cowrie St at Wharf Rd
- Cowrie St at Trail Ave
- Cowrie St at Trail Ave
- Dolphin St at Trail Ave
- Hwy 101 at Selma Park Rd
- Hwy 101 at Snodgrass Rd
- Hwy 101 at Nestman Rd
- Hwy 101 at Havies Rd
- Hwy 101 at Heather Rd
- Hwy 101 at Bay Rd
- Hwy 101 at Davis Bay Rd
- Hwy 101 at Westley Rd
- Hwy 101 at Chestnut Rd
- Hwy 101 at Field Rd
- Hwy 101 at Tyson Rd
- Hwy 101 at Jack Rd
- Hwy 101 at 3800 block
- Hwy 101 at Roberts Creek Park
- Hwy 101 at Pell Rd
- Flume Rd at Spruce Rd
- Beach Ave at Flume Rd
- Beach Ave at Marlene Rd
- Beach Ave at Paggio Rd
- Beach Ave at Cedar Grove Rd
- 3200 Block Beach Ave
- Beach Ave at Edmonds Rd
- 3100 Block Beach Avenue
- Roberts Creek Rd at Lower Rd
- Lower Rd at Largo Rd
- Lower Rd at Stephens Rd
- Lower Rd at Metcalfe Rd
- Lower Rd at Woodly Rd
- Lower Rd at Bayview Rd
- Lower Rd at Cheryl-Ann Park Rd
- Lower Rd at Joe Rd
- Lower Rd at Maskell Rd
- Lower Rd at Geddes Rd
- Lower 2190 block
- Lower Rd at Conrad Rd
- Lower Rd at Gulf Rd
- Lower Rd at Tenuchin Rd
- Lower Rd at Grandview Rd
- Hwy 101 at Pine St
- Hwy 101 at Oceanview Dr
- Hwy 101 at Clifton Vale Lane
- Hwy 101 at Veterans Rd
- Veterans Rd at Marion Pl
- Fitchett Rd at King Rd
- King Rd at Kearton Rd
- King Rd at Chaster Rd
- Chaster Rd at Cedar Grove Elementary
- Pratt Rd at Fraser Rd
- Pratt Rd at Fircrest Rd
- Gibsons Way at Pratt Rd
- Gibsons Way at Park Rd
- Gibsons Way at Shaw Rd
- Gibsons Way at School Rd
- Gibsons Way at Wyngaert Rd
- Gibsons Way at N Fletcher Rd
- Gibsons Way at Seaview Rd
- Gower Point Rd at Winn Rd
- Dougall Rd at Prowse Rd
- Headlands Rd at Skyline Dr
- Headlands Rd at Burns Rd
- Gower Point Rd at Glassford Rd
- Gower Point Rd at Blain Lane
- Gower Point Rd at Winn Rd
- Marine Dr at Jacks Lane
- Marine Dr at Armours Beach
- Marine Dr at Central Ave
- Marine Dr at Trant Rd
- Marine Dr at Soames Hill Park
- Marine Dr at Cartwright Rd
- Marine Dr at Hopkins Rd
- Marine Dr at North Rd
- Port Mellon Hwy at Smith Rd
- Langdale Ferry Terminal
- Port Mellon Hwy at Forbes Rd
- Forbes Rd at Port Mellon Hwy
- Johnson Rd at Forbes Rd
- Johnson Rd at Wharf Rd
- Marine Dr at Hopkins Rd
- 1200 Block Marine Dr
- Marine Dr at Cartwright Rd
- Marine Dr at Trant Rd
- Marine Dr at Central Ave
- Marine Dr at Harvey Rd
- Marine Dr at Armours Beach
- Marine Dr at Jacks Lane
- Franklin Rd at Cochrane Rd
- Gibsons Way at Seaview Rd
- Gibsons Way at Hicks Lane
- Gibsons Way at Wyngaert Rd
- North 742 block
- North Rd at Stewart Rd
- North Rd at Cemetery Rd
- Gibsons Way at Farnham Road
- Gibsons Way at Seamount Way
- Pratt Rd at Fircrest Rd
- Pratt Rd at Fraser Rd
- Pratt Rd at Chaster Rd
- Chaster Rd at Cedar Grove Elementary
- King Rd at Chaster Rd
- King Rd at Kearton Rd
- King Rd at Fitchett Rd
- Veterans Rd at Carol Pl
- Hwy 101 at Payne Rd
- Hwy 101 at Veterans Rd
- Hwy 101 at Clifton Vale Lane
- Lower Rd at Pine St
- Lower Rd at Tenuchin Rd
- Lower Rd at Leek Rd
- Lower Rd at Conrad Rd
- Lower Rd at Geddes Rd
- Lower Rd at Agnes Rd
- Lower Rd at Joe Rd
- Lower Rd at Cheryl-Ann Park Rd
- Lower Rd at Bayview Rd
- Lower Rd at Woodly Rd
- Lower Rd at Metcalfe Rd
- Lower Rd at Blackburn Rd
- Lower Rd at Largo Rd
- Beach Ave at Edmonds Rd
- 3200 Block Beach Ave
- Beach Ave at Cedar Grove Rd
- Beach Ave at Paggio Rd
- Hwy 101 at Lockyer Rd
- Hwy 101 at Pell Rd
- Hwy 101 at Roberts Creek Provincial Park
- Hwy 101 at 3810 block
- Hwy 101 at Jack Rd
- Hwy 101 at Tyson Rd
- Hwy 101 at Blower Rd
- Hwy 101 at Field Rd
- Hwy 101 at Chestnut Rd
- Hwy 101 at Davis Bay Rd
- Hwy 101 at Bay Rd
- Hwy 101 at Heather Rd
- Hwy 101 at Havies Rd
- Hwy 101 at Snodgrass Rd
- Hwy 101 at Selma Park Rd
- Hwy 101 at Matukwum Lane South
- Hwy 101 at Matukwum Lane North
- Hwy 101 at Roberts Creek Rd
- Hwy 101 at Largo Rd
- Hwy 101 at Neilson Rd
- Hwy 101 at Crowe Rd
- Hwy 101 at Maskell Rd
- Hwy 101 at Gail Rd
- Hwy 101 at 2040 block
- Hwy 101 at Leek Rd
- Hwy 101 at Sullivan Rd
- Hwy 101 at Sullivan Rd
- Hwy 101 at Leek Rd
- Hwy 101 at Conrad Rd
- Hwy 101 at Byng Rd
- Hwy 101 at Crowe Rd
- Hwy 101 at Neilson Rd
- Hwy 101 at Largo Rd
- Hwy 101 at Roberts Creek Rd
- Teredo St at Burley Pl
- Hwy 101 at Norwest Bay Rd
- Norwest Bay Rd at Julmar Rd
- Norwest Bay Rd at Derby Rd
- Norwest Bay Rd at Winter Rd
- Norwest Bay Rd at Emerson Rd
- Norwest Bay Rd at Mason Rd
- Mason Rd at Norwest Bay Rd
- Mason Rd at Meier Rd
- Hwy 101 at Mason Rd
- Hwy 101 at Mills Rd
- Hwy 101 at Derby Rd
- Trail Ave at Spindrift St
- Trail Ave at Neptune Rd
- Trail Ave at Surf Circle
- Anchor Rd at Trail Ave
- Marine Way at Trail Ave
- Trail Ave at Marine Way
- Trail Ave at Turnstone Cres
- Trail Ave at Reef Rd
- Reef Rd at Spray St
- Reef Rd at Shoal Way
- Fairway Ave at Shoal Way
- Fairway Ave at Beacon Lane
- Fairway Ave at Ripple Way
- Reef Rd at Driftwood Pl
- Reef Rd at Spray St
- Marine Way at Heron Pl
- Wharf Ave at Osprey St
- and 50 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
- Warning342 instances
342 of 342 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)
- Warning300 instances
300 of 300 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)
- 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)
- Warning5 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)
- Info12 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 50 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 300 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 50 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 81 / 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 83 / 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-sunshine-coast/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.