GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-19

Soléa (Mulhouse Alsace Agglomération)

Grade F · 32.8 / 100

Down 0.5 points since 2026-07-18 (F to F).

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

  1. Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

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

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

Key facts

Feed URL
https://transport.data.gouv.fr/resources/80492/download
Last checked
2026-07-19
Service window
42 days of service data remain. Last service date 2026-08-30.
Location
Grand-Est, France

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