GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-24

Réseau urbain et interurbain Trans'Agglo

Grade F · 39.2 / 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 'start_and_end_range_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Start and end range out of order (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

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

  3. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

    258 of 263 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.

Key facts

Feed URL
https://www.data.gouv.fr/api/1/datasets/r/117daa0d-0708-43aa-a562-7d5b3d6570b0
Last checked
2026-07-24
Service window
160 days of service data remain. Last service date 2026-12-31.
Location
Provence-Alpes-Côte-d’Azur, France

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