Réseau urbain agglo'Bus

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_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

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

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

2. Delete the empty calendars or set their service days.

   Some service calendars have no days of the week switched on. Trips tied to these calendars never run; they are dead data that can mask real schedule problems.

   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 few minutes in your scheduling software.

3. Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar.

   The feed has a stretch of two weeks or more with no service running. A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

   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 of your calendar dates.