GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-10-16

Amelys (Montargis)

Grade C · 76.3 / 100

Unchanged since 2026-10-15.

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 no change
  • Rider experience no change

Top three things to fix

  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.

    This one is about the feed as a whole, so there is no share of it to count.

    Effort: A small file for most flat-fare systems.

  2. Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1.

    Some rows in stop_times.txt leave the timepoint column blank. That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.

    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.

    Effort: Usually one export setting.

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

    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.

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

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

Key facts

Feed URL
https://www.data.gouv.fr/api/1/datasets/r/39240e80-d3f4-4702-ba93-520fae414649
Last checked
2026-10-16
Service window
65 days of service data remain. Last service date 2026-12-20.
Feed version
20260701-105809
Location
Centre-Val de Loire, France

Part of the France portfolio: see where this agency sits among the other feeds in that group before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.