Call-prep brief · checked 2026-09-02
Move (Vendôme)
Grade C · 71.0 / 100
Up 42.3 points since 2026-09-01 (F to C).
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 up 19.5
- Freshness up 85.0
- Rider experience up 40.3
No longer reported since the last check (8 findings):
- 4 of 733 trips don't say whether the vehicle is wheelchair accessible. (scorecard_wheelchair_accessible_unknown)
- About 108 stop names are written in ALL CAPS. (scorecard_stop_names_all_caps)
- 733 of 733 trips have no headsign, the text that tells riders where the bus is going. (scorecard_missing_headsigns)
- Some internal IDs use characters outside the basic text set. (non_ascii_or_non_printable_char)
- Some files leave out fields that GTFS asks for but does not require. (missing_recommended_field)
- Some service calendars in the feed have already ended. (expired_calendar)
- Some files contain columns that are not part of the GTFS spec. (unknown_column)
- Service data ended 1 day(s) ago. (scorecard_feed_expired)
This compares feed state. It does not identify who made a change or why.
Top three things to fix
Add feed_info.txt with feed_start_date and feed_end_date to your export.
feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Effort: Two fields, set once in export settings.
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.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
98 of 166 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Effort: A column in stops.txt; your scheduling software likely has it.
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
- feed_info.txt is missing its start/end dates (the file itself is absent)
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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
- 98 of 166 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
Key facts
- Feed URL
- https://transport.data.gouv.fr/resources/82832/download
- Last checked
- 2026-09-02
- Service window
- 2555 days of service data remain. Last service date 2033-08-31.
- Location
- Centre-Val de Loire, France
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.