TBK (Quimperlé)

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 fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

   The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

   Estimated effort: A small file for most flat-fare systems.

2. Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language.

   Some internal IDs use characters outside the basic text set. These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.

   Estimated effort: A planned ID change, not a quick text cleanup.

3. 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.