Board packet · transit data quality · checked 2026-08-02
OmniTrans
Grade B · 88.0 / 100
Unchanged since 2026-08-01.
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:
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.
Estimated effort: A few minutes per flagged trip.
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.
Estimated effort: A few minutes per flagged stop.
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.
Estimated 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
- Feed evidence
- Some stops sit far from the route line they belong to.
- Next action
- Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.
- 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
- Feed evidence
- Unexpected enum value (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'unexpected_enum_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/omnitrans/. Rubric v1.3, validator 8.0.1.