Ride Connection

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.

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

   677 of 677 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 677 trips in the feed.

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

3. Remove retired stops from the export, or add them back to the trips that should serve them.

   Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.

   This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

   Estimated effort: A review pass in your scheduling software.

Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.