GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-24

Réseau urbain L'va

Grade D · 61.7 / 100

First check for this agency, so there is no trend yet.

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

No category changes since the last check.

Top three things to fix

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

    Effort: Usually an export-tool fix, not hand editing.

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

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

    Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

Key facts

Feed URL
https://www.data.gouv.fr/api/1/datasets/r/e0831d78-5577-4cae-aa00-de5eeaf3ecb6
Last checked
2026-07-24
Service window
160 days of service data remain. Last service date 2026-12-31.
Feed version
2026-07-17 23:10:45.293365 UTC
Location
Auvergne-Rhône-Alpes, France

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