GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-10-16

Réseau urbain de la zone Centre (CACEM)

Grade F · 54.3 / 100

Up 4.7 points since 2026-10-15 (F to F).

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

  • Correctness no change
  • Freshness no change
  • Rider experience no change
  • Realtime quality up 23.9

No longer reported since the last check (3 findings):

  • The trip updates realtime feed failed during sampling. (scorecard_rt_trip_updates_unreachable)
  • The vehicle positions realtime feed failed during sampling. (scorecard_rt_vehicle_positions_unreachable)
  • The service alerts realtime feed failed during sampling. (scorecard_rt_service_alerts_unreachable)

This compares feed state. It does not identify who made a change or why.

Top three things to fix

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

    Block trips with overlapping stop times (flagged by the MobilityData validator). See the linked rule for what this affects.

    This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

    Effort: Varies.

  2. Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out.

    67 of 83 trips scheduled during the sampling window had no live predictions. Riders on those trips get schedule times labeled as live. Caltrans asks that every trip you run shows up in TripUpdates.

    This was measured over a realtime sampling window, so it has no feed-wide share.

    Effort: A vendor data-mapping question.

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

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

    Fixing this covers all 2,255 stops in the feed.

    Effort: A column in stops.txt; your scheduling software likely has it.

Riders and need behind these fixes

  • Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
  • The served-area need overlays cover the United States and Canada, so none of them applies to this feed.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence
Block trips with overlapping stop times (flagged by the MobilityData validator).
Next action
Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text

Key facts

Feed URL
https://www.data.gouv.fr/api/1/datasets/r/6e599077-0719-44b4-82ad-0da90a282846
Last checked
2026-10-16
Service window
76 days of service data remain. Last service date 2026-12-31.
Location
Martinique, France

Part of the France portfolio: see where this agency sits among the other feeds in that group before the call.

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