Réseau maritime Corsica Linea

What this grade measures

The quality of the schedule data in the feed scored here 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 'point_near_origin' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Point near origin (flagged by the MobilityData validator). See the linked rule for what this affects.

   Estimated effort: Varies.

2. Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.

   786 of 786 trips have no headsign, the text that tells riders where the vessel is going. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

   Estimated effort: Usually one value per route pattern in your scheduling source.

3. Add feed_info.txt with feed_start_date and feed_end_date to your export.

   feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

   Estimated effort: Two fields, set once in export settings.