UTA

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. Re-generate shape distances in your export; flag to your vendor if it persists.

   Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.

   Estimated effort: Usually an export-tool fix, not hand editing.

2. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

   The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

   Estimated effort: A small file for most flat-fare systems.

3. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   2894 of 5435 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

   Estimated effort: A column in stops.txt; your scheduling software likely has it.

Where this agency stands

Ahead of 32% of all tracked agencies, and ahead of 44% of large agencies nationwide.