Board packet · transit data quality · checked 2026-10-16
Ondéa (Aix-les-Bains)
Grade F · 56.9 / 100
Up 2.5 points since 2026-10-15 (F to F).
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
Since the previous compatible check, 4 findings were no longer reported:
- This feed models stations or entrances but has no pathways.txt.
- Some service calendars in the feed have already ended.
- Unused station (flagged by the MobilityData validator).
- Some service dates fall outside the date window set in feed_info.txt.
This records feed state, not who made a change or why.
What needs attention next
Three improvements, in priority order, each sized so the board can see what it is approving:
Re-generate shape distances in your export; flag to your vendor if it persists.
Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.
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: Usually an export-tool fix, not hand editing.
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.
This one is about the feed as a whole, so there is no share of it to count.
Estimated effort: A small file for most flat-fare systems.
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.
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: Usually one export setting.
Riders and need behind these fixes
- Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
- The served-area need overlays cover the United States and Canada, so none of them applies to this feed.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- Some trips have stop times whose distances along the route go backwards.
- Next action
- Re-generate shape distances in your export; flag to your vendor if it persists.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- The feed contains no fare information.
- Next action
- 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.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some route lines list the same point twice in a row.
- Next action
- Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/ondea-aix-les-bains/. Rubric v1.4, validator 8.0.1.