San Joaquin Regional Transit District (RTD)

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-export with a validity window that reaches at least 60 days out.

   Service data runs out in 16 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

   Estimated effort: One export setting.

   Agencies here usually clear this within about 1 week (based on 61 observed fixes).

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

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

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

   Stop too far from shape using user distance (flagged by the MobilityData validator). See the linked rule for what this affects.

   Estimated effort: Varies.

   Agencies here usually clear this within about 1 week (based on 6 observed fixes).

Where this agency stands

Ahead of 52% of all tracked agencies, and ahead of 49% of mid-size agencies nationwide.