GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-23

Réseau urbain TOHM

Grade D · 62.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 '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. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

    121 of 121 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.

  3. Ask your AVL vendor to publish updates at least every 20 seconds (the Caltrans guideline).

    Realtime data was up to 242 seconds old when sampled. Stale positions and predictions are worse than none: riders watch a bus that already left.

    Effort: A vendor configuration question.

Key facts

Feed URL
https://www.data.gouv.fr/api/1/datasets/r/6fdd303a-7b76-4742-b877-d0923c59505b
Last checked
2026-07-23
Service window
161 days of service data remain. Last service date 2026-12-31.
Location
Hauts-de-France, France

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