GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-24

Réseau urbain et scolaire T'CAP — dsp24data-gtfs-2024-09-23-15-45-06.zip

Grade C · 72.1 / 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. Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Stop time with arrival before previous departure time (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://www.data.gouv.fr/api/1/datasets/r/ba477c37-93d1-4900-8958-baf3c6de9d57
Last checked
2026-07-24
Service window
68 days of service data remain. Last service date 2026-09-30.
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.