Arcadia Transit

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

Since the previous compatible check, 1 finding was no longer reported:

• 1 of 3 trips scheduled during the sampling window had no live predictions.

This records feed state, not who made a change or why.

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.

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

   Fixing this covers all 85 stops in the feed.

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

2. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

   164 of 164 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

   Fixing this covers all 164 trips in the feed.

   Estimated effort: A default or per-trip field in your export.

3. Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.

   164 of 164 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

   Fixing this covers all 164 trips in the feed.

   Estimated effort: Usually one value per route pattern in your scheduling source.

This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.