← Back to the full scorecard

Call-prep brief · checked 2026-07-09

Big Blue Bus

Grade F · 44.1 / 100

Down 0.4 points since 2026-07-08 (F to F).

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.

What changed since the last check

  • Correctness no change
  • Freshness down 1.7
  • Rider experience no change
  • Realtime quality no change

Top three things to fix

  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.

    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.

    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.

    Effort: A vendor data-mapping question.

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

NTD certification readiness: Needs attention

This feed is close to NTD-ready. 1 validator error to resolve.

Published Ready
Published at a public URL.
Valid Needs attention
1 validator error to resolve.
Current Ready
Service data covers the next 42 days.

agency_id and NTD ID: Not aligned. Your feed's agency_id is 6216179; your National Transit Database ID is 90008. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 90008 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.

The bar this score answers to

The published guideline in California is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.

Key facts

Feed URL
http://gtfs.bigbluebus.com/current.zip
Last checked
2026-07-09
Service window
30 days of service data remain. Last service date 2026-08-08.
Feed version
2026-04 (Apr)_20260319
State
California

Part of the California portfolio: see where this agency sits among the state's feeds before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.1, validator 8.0.1.