Metro Transit

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:

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

2. Turn on 'remove unused shapes' (or the like) in your export tool.

   The feed contains route shapes no trip uses. Harmless to riders, but it bloats the feed and suggests stale export data.

   Estimated effort: One setting.

3. Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips.

   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.

   Estimated effort: A vendor support ticket with the trip ids attached.

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

Where this agency stands

Ahead of 81% of all tracked agencies, and ahead of 94% of large agencies nationwide.