GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-18

T'MM (Moselle et Madon)

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

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

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

    Stop too far from shape using user distance (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

Key facts

Feed URL
https://api.grandest2.cityway.fr/exs/GTFS?Key=OPENDATA&OperatorCode=TMM
Last checked
2026-07-18
Service window
42 days of service data remain. Last service date 2026-08-29.
Feed version
20260714
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.