Adelaide Metro

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

1. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   9171 of 9171 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.

   Effort: A column in stops.txt; your scheduling software likely has it.

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

   Effort: A small file for most flat-fare systems.

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

   Effort: Varies.

Key facts

Feed URL

https://gtfs.adelaidemetro.com.au/v1/static/latest/google_transit.zip

Last checked

2026-07-13

Service window

90 days of service data remain. Last service date 2027-03-27.

Feed version

1677

Location

South Australia, Australia