Réseau urbain TIVA

What this grade measures

The quality of the schedule data this agency publishes 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. 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.

   17 of 17 trips lack rider-facing destination or direction text. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

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

2. Review the flagged fields and fill in the ones your riders would use.

   Some files leave out fields that GTFS asks for but does not require. Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

   Estimated effort: A field at a time; not urgent.

3. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').

   Some rider-facing names are in ALL CAPS or all lowercase. ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

   Estimated effort: Often a bulk fix in your scheduling software.