Réseau maritime Corsica Ferries

What this grade measures

The quality of the schedule data this agency publishes for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

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

   Missing required field (flagged by the MobilityData validator). See the linked rule for what this affects.

   Estimated effort: Varies.

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

   18 of 18 terminals 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.

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

3. Populate trip_headsign to match the published sailing destination.

   5020 of 5020 trips have no headsign. Riders at the terminal can't tell which destination a sailing serves.

   Estimated effort: Usually a bulk edit in your scheduling software.