GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-08-01

Big Blue Bus

Grade F · 52.0 / 100

Unchanged since 2026-07-31.

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 no change
  • 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 478 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.

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

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence
The realtime feed's last update was about 478 days old when sampled.
Next action
Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text

NTD GTFS 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 133 days.
agency_id provided Ready
agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.

agency_id equals NTD ID (optional): Different (allowed). 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. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 6216179 to NTD ID 90008, and keep the feed value stable. Do not change it solely to make the two values equal.

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-08-01
Service window
133 days of service data remain. Last service date 2026-12-12.
Feed version
2026-07-28T22:37:43Z
Location
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.3, validator 8.0.1.