Call-prep brief · checked 2026-07-19
TAO (Orléans Métropole)
Grade D · 63.1 / 100
Down 0.4 points since 2026-07-18 (D to D).
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
Top three things to fix
Populate trip_headsign to match what the transit vehicle displays.
50543 of 50543 trips have no headsign. Riders at the stop can't tell which direction a transit vehicle is going.
Effort: Usually a bulk edit in your scheduling software.
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.
Effort: A small file for most flat-fare systems.
Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.
Some stops sit far from the route line they belong to. Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.
Effort: A few minutes per flagged stop.
Key facts
- Feed URL
- https://transport.data.gouv.fr/resources/83751/download
- Last checked
- 2026-07-19
- Service window
- 42 days of service data remain. Last service date 2026-08-30.
- Location
- Centre-Val de Loire, France
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.2, validator 8.0.1.