Metro Transit

Top things to fix

Score by category

Over time

Overall score across the last 20 checks — down 0.4 since 2026-07-08.

What changed since your last check

• Correctness— no change
• Freshness▼ down 1.6
• Rider experience— no change
• Realtime quality— no change

What changed in this feed

Overall score fell 0.4 points since 2026-07-08.

Same feed file as 2026-07-08; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

What changed over time

On 2026-06-19 this feed started at grade C. On 2026-06-20 the grade moved from C to B. On 2026-06-22 the grade moved from B to C. On 2026-06-23 the grade moved from C to B. As of 2026-07-09 it holds grade B.

A plain-language history of this feed, newest first.

• 2026-07-04 Grade went C to B, freshness rose 8 points.
• 2026-07-02 Grade went B to C.
• 2026-06-27 Grade went C to B, freshness rose 10 points.
• 2026-06-26 Grade went B to C.
• 2026-06-23 Grade went C to B, realtime rose 18 points.
• 2026-06-22 Grade went B to C, realtime fell 18 points.
• 2026-06-20 Grade went C to B, freshness rose 10 points.

Everything we checked

• Warning100 instances

  100 of 243 sampled vehicle positions were far from their assigned route (worst: 11521262 m).

  A bus shown off its route usually means a wrong trip assignment; riders watch their bus drive the wrong streets.

  Fix: Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips. (A vendor support ticket with the trip ids attached.)

  Agencies here usually clear this within about 1 week (based on 31 observed fixes).

  Validator rule: scorecard_rt_vehicles_off_route

• Warning76 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)

• Warning26 instances

  26 of 8232 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)

• Warning21 instances

  Equal shape distance same coordinates (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Validator rule: equal_shape_distance_same_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  Same name and description for route (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Validator rule: same_name_and_description_for_route · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  Many of the feed's trips don't run at all in the next 7 days.

  It usually means old service periods are still in the export, making the feed bigger and harder to check.

  Fix: Trim past service periods the next time you export. (One setting in most export tools.)

  Agencies here usually clear this within about 1 week (based on 31 observed fixes).

  Validator rule: trip_coverage_not_active_for_next7_days · 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)

• Warning1 instance

  1 of 47 trips scheduled during the sampling window had no live predictions.

  Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.

  Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)

  Agencies here usually clear this within about 1 week (based on 82 observed fixes).

  Validator rule: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)

• Info19964 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)

• Info117 instances

  Platform without parent station (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Validator rule: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Info42 instances

  This feed describes station pathways, including step-free (elevator) routes.

  Riders can be routed through the station, and wheelchair users can see whether a step-free route exists.

  Fix: No action needed. (None.)

  Validator rule: scorecard_station_pathways

• Info7 instances

  Some files contain columns that are not part of the GTFS spec.

  Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

  Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

  Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Info3 instances

  Big gap in service (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Agencies here usually clear this within about 1 week (based on 13 observed fixes).

  Validator rule: big_gap_in_service · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Info2 instances

  Unknown file (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Agencies here usually clear this within about 1 week (based on 6 observed fixes).

  Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

• 7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (134, 156, 686, 765, 802, 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.

• 8123 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Chicago Ave S & 8th St S", "Chicago Ave S & 17th St E", "Chicago Ave S & 18th St E", and more).

  Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.