Board packet · transit data quality · checked 2026-08-01
Adelaide Metro
Grade D · 68.5 / 100
Unchanged since 2026-07-31.
What this grade measures
The quality of the schedule data this agency publishes for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.
Progress this period
No newly cleared items this period. The score and trend above reflect where the feed stands today.
What needs attention next
Three improvements, in priority order, each sized so the board can see what it is approving:
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
9167 of 9167 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.
Estimated effort: A column in stops.txt; your scheduling software likely has it.
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.
Estimated effort: A small file for most flat-fare systems.
Review the rule documentation for 'unexpected_enum_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Unexpected enum value (flagged by the MobilityData validator). See the linked rule for what this affects.
Estimated effort: Varies.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 9167 of 9167 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- The feed contains no fare information.
- Next action
- 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.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Unexpected enum value (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'unexpected_enum_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/adelaide-metro/. Rubric v1.3, validator 8.0.1.