GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

TransLink Whitsundays (Whitsunday Transit)

Based on the feed this agency publishes

Service mode Bus

76.6 / 100

First scorecard for this agency

Catalogued in Queensland, Australia.

Covers 59 daysAccessibility gapsRealtime not yet published

One qconnect regional network feed for the Whitsundays (Proserpine, Airlie Beach, and Cannonvale); 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 11 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

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

275 of 275 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 59 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

Correctness92.0 / 100

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

Freshness98.3 / 100

Service data covers the next 59 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.

1 accessibility depth signal

  • 30 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Shute Harbour Rd near Port Dr hail 'n' ride", "Shute Harbour Rd hail 'n' ride", "Shute Harbour Rd near Whitsunday Dr hail 'n' ride", 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.

  • 860 (pink)
  • 861 (pink)
Routes in TransLink Whitsundays (Whitsunday Transit)'s feed
RouteTypeLine color
860 Proserpine - Shute HarbourBuspink
861 Cannonvale - Jubilee PocketBuspink

This feed has 77 stops.

List every stop
  • Shute Harbour Road at Orchid Road
  • Whitsunday Plaza
  • Shute Harbour Road at Adventure Whitsunday
  • Shute Harbour Road at William Murray Drive
  • Shute Harbour Road at Macarthur Drive
  • Shute Harbour Road at Manooka Drive
  • Shute Harbour Road at Pandanus Drive
  • Whitsunday shopping centre
  • Shute Harbour Road at Altmann Avenue
  • Coral Sea Marina
  • Airlie Beach Central
  • Shute Harbour Rd near Port Dr hail 'n' ride
  • Shute Harbour Road at Plantation Drive
  • Shute Harbour Road at Loop Road
  • Shute Harbour Road at Island Road Island Traders
  • Shute Harbour Road at Ferntree Road
  • Shute Harbour Road at Mandalay Road
  • Shute Harbour Road at Jasinique Drive
  • Shute Harbour Road at Flametree
  • Shute Harbour Road at Air Whitsunday Road
  • Shute Harbour Road at Conway Picnic
  • Shute Harbour Road at Conway NP
  • Shute Harbour Rd hail 'n' ride
  • Shute Harbour Rd near Whitsunday Dr hail 'n' ride
  • Shute Harbour Marine Terminal
  • Shute Harbour Rd near Whitsunday Dr hail 'n' ride
  • Shute Harbour Road at Conway NP
  • Shute Harbour Road at Conway Picnic hail 'n' ride
  • Shute Harbour Road at Air Whitsunday Road
  • Shute Harbour Road at Flametree
  • Shute Harbour Rd near Jasinique Dr hail 'n' ride
  • Shute Harbour Road at Mandalay Road
  • Shute Harbour Road at Ferntree Road
  • Shute Harbour Road at Cedar Crescent
  • Shute Harbour Road at Loop Road
  • Shute Harbour Road at Plantation Drive
  • Shute Harbour Road at Hermitage Drive
  • Airlie Beach Central
  • Shute Harbour Road at Saint Martins Lane
  • Shute Harbour Road at Stewart Drive
  • Shute Harbour Road at Manooka Drive
  • Shute Harbour Road at Willis Court
  • Shute Harbor Rd near William Murray Dr hail 'n' ride
  • Shute Harbour Rd near Orchid Rd hail 'n' ride
  • Shute Harbour Rd near Stanley Dr hail 'n' ride
  • Shute Harbour Rd near Kookaburra Dr hail 'n' ride
  • Shute Harbour Rd near Greg Cannon Valley Rd HnR
  • Shute Harbour Road at Brandy Creek Road
  • Shute Harbour Road at Rifle Range Road
  • Shute Harbour Rd near Jansen Rd hail 'n' ride
  • Camm Rd at Usher Rd
  • Shute Harbour Rd near Tyree Rd hail 'n' ride
  • Dodd St near Faust St hail 'n' ride
  • Proserpine, Mill Street
  • Taylor St near Herbert St hail 'n' ride
  • Shute Harbour Road at Tyree Road
  • Shute Harbour Road at Plemenuk Road
  • Shute Harbour Road at Brandy Creek Road
  • Shute Harbour Rd near Greg Cannon Valley Rd HnR
  • Shute Harbour Rd near Riordanvale Rd hail 'n' ride
  • Shute Harbour Rd near Rifle Range Rd hail 'n' ride
  • Shute Harbour Road at Hermitage Drive
  • Ruge St at Proserpine SHS
  • Dodd St neat Anzac St hail 'n' ride
  • Port of Airlie
  • Coconut Grove at Airlie Esplanade
  • Coconut Grove at Airlie Esplanade
  • Jubilee Pocket Rd near Sabel Bvd hail 'n' ride
  • Jubilee Pocket Rd near Aniwa Ct hail 'n' ride
  • Valley Dr near Ridge View Rd hail 'n' ride
  • Abell Rd near Parker Rd hail 'n' ride
  • Valley Dr near Ridge View Rd hail 'n' ride
  • Abell Rd near Parker Rd hail 'n' ride
  • Fuljames St at Marathon St hail 'n' ride
  • Renwick Rd at Fuljame Street hail 'n' ride
  • Renwick Rd at Stanbury Street hail 'n' ride
  • Faust St near Ann St hail 'n' ride

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

6 findings, ordered by severity.

Show every finding
  • Warning275 instances

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

  • Warning77 instances

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

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

  • 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 59 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.

Clears the Google and Apple Maps four-week coverage bar. This feed has 59 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 92 / 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 98 / 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.

TransLink Whitsundays (Whitsunday Transit) 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/translink-whitsundays/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.