Redding Area Bus Authority

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. Re-generate shape_dist_traveled on export so stop and shape distances use the same units.

   On some trips the stop distances run a little past the end of the route line. The stop and shape distance values don't quite line up, so any math that uses them can drift.

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

2. Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.

   Some route lines list the same point twice in a row. Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.

   Estimated effort: Usually one export setting.

3. Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'.

   Some route long names repeat the route's short name inside them. Apps show both names together, so riders see the number twice, like '5 5 Downtown'.

   Estimated effort: One field per flagged route.

This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.