Big Blue Bus

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. Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.

   The realtime feed's last update was about 443 days old when sampled. A realtime feed this far behind has effectively stopped. Riders see buses that already left, or apps quietly fall back to the schedule while still showing a live label.

   Estimated effort: A vendor support ticket; treat it as a feed outage.

2. Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.

   Estimated effort: Varies.

3. Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.

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

   Estimated effort: A vendor data-mapping question.

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

Where this agency stands

Ahead of 20% of all tracked agencies, and ahead of 20% of mid-size agencies nationwide.