OmniTrans

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. Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Invalid phone number (flagged by the MobilityData validator). See the linked rule for what this affects.

   Estimated effort: Varies.

2. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').

   Some rider-facing names are in ALL CAPS or all lowercase. ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

   Estimated effort: Often a bulk fix in your scheduling software.

3. 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.

   Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).

Where this agency stands

Ahead of 70% of all tracked agencies, and ahead of 88% of large agencies nationwide.