GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-08-02

OmniTrans

Grade B · 88.0 / 100

Unchanged since 2026-08-01.

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

Top three things to fix

  1. Check the flagged stop times for transposed minutes.

    Some scheduled trips move faster between stops than a bus can. Usually a typo'd stop time; riders get arrival times no bus can meet.

    Effort: A few minutes per flagged trip.

  2. Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.

    Some stops sit far from the route line they belong to. Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.

    Effort: A few minutes per flagged stop.

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

    Unexpected enum value (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

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
Some scheduled trips move faster between stops than a bus can.
Next action
Check the flagged stop times for transposed minutes.
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: Ready

Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Ready
Service data covers the next 154 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): Not checked yet. This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.

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://www.omnitrans.org/google/google_transit.zip
Last checked
2026-08-02
Service window
154 days of service data remain. Last service date 2027-01-03.
Feed version
20260810_20260710a
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.