San Joaquin Regional Transit District (RTD)

What this grade measures

The quality of the schedule data in the feed scored here 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. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

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

2. Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips.

   9 of 9 sampled vehicle positions were far from their assigned route (worst: 2808 m). A bus shown off its route usually means a wrong trip assignment; riders watch their bus drive the wrong streets.

   Estimated effort: A vendor support ticket with the trip ids attached.

3. Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.

   Some stops sit far from the route line, going by the feed's own distance values. Trip planners may draw the route down the wrong streets or point riders to the wrong corner.

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