Feed status · checked 2026-10-15
Réseau maritime Corsica Linea
Based on the official feed source on file
Service mode Ferry
unchanged since 2026-10-14
Cataloged in Corse, France.
Source feed: https://www.data.gouv.fr/api/1/datasets/r/13977931-86ae-4b7a-9598-d222333a5fbd
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.4, validator 8.0.1.
Checked for changes 6 hours ago; last changed 2 days ago.
Measured 3 of 4 score categories from the official feed URL on file.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the official feed URL on file.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
About this feed
Réseau maritime Corsica Linea’s published feed lists 3 ferry routes, 1,649 scheduled trips and 9 stops. The published file last changed on 2026-10-14.
Top things to fix
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.
1649 of 1649 trips have no headsign, the text that tells riders where the vessel is going. A trip counts when it has trip_headsign or a stop_headsign at every terminal. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fixing this covers all 1,649 trips in the feed.
⏱ Usually one value per route pattern in your scheduling source.worth about +15 points in its category
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
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.
This one is about the feed as a whole, so there is no share of it to count.
⏱ Two fields, set once in export settings.worth about +15 points in its category
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.
This one is about the feed as a whole, so there is no share of it to count.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested change.
- 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
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Fix 01 · Read the fix guide for scorecard_missing_headsigns
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Fix 02 · Read the fix guide for scorecard_missing_feed_info_dates
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Fix 03 · Read the fix guide for scorecard_no_fare_data
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 332 days.
- Published accessibility data
- Accessibility information is stated for 100% of terminals and 100% of trips. This measures published data, not whether terminals or vessels are physically usable.
- Fare information
- No fare information is published in the feed.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Ungraded capability read
Ferry data profile
A ferry-specific view of what this GTFS feed publishes. Schedule measurements use ferry routes and trips only; fare and realtime facts are labeled as whole-feed. Unknown values are not treated as no.
- Ferry service
- 3 routes · 1,649 trips
- Terminal structure
- 9 ferry boarding locations; no parent-station hierarchy is published.
- Terminal access
- Not applicable: no ferry boarding location is linked to a parent station, so stop_access is not permitted here.
- Published accessibility
- 100% of ferry boarding locations publish a value; 100% of all ferry boarding locations explicitly say allowed (9 of 9). Unstated values remain unknown. 100% of ferry trips publish a value; 100% of all ferry trips explicitly say allowed (1,649 of 1,649). Unstated values remain unknown. This reports published values, not verified physical usability.
- Bicycles
- 100% of ferry trips publish a value; 100% of all ferry trips explicitly say allowed (1,649 of 1,649). Unstated values remain unknown.
- Cars
- 100% of ferry trips publish a value; 100% of all ferry trips explicitly say allowed (1,649 of 1,649). Unstated values remain unknown.
- Fares
- Whole feed: no applied fare data is published. This is not evidence that ferry service is free.
- Realtime
- Whole feed: no GTFS-Realtime endpoints are configured in this scorecard.
Descriptive only. This profile does not change the grade or verify vessels, terminal facilities, vehicle carriage, fares, or accessibility in the real world. Field meanings follow the GTFS Schedule reference.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 2 kinds of issue across 2 instances (0 error, 2 warning, 0 informational).
Service data covers the next 332 days.
100% of terminals state wheelchair accessibility (100% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a terminal is physically usable. Fare data is not published.
100% of terminals state accessibility (100% marked accessible). Reflects what the feed states, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and terminals
This feed has no route shapes, so the map shows its terminals only.
This feed has 9 terminals.
The route and terminal data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and terminals: this agency's GTFS feed.
| Route | Type | Line color |
|---|---|---|
| Algérie Lignes France <--> Algérie | Ferry | teal (no shape in feed) |
| Corse DSP Lignes Corse <--> Continent DSP | Ferry | teal (no shape in feed) |
| Tunisie Lignes France <--> Tunisie | Ferry | teal (no shape in feed) |
List every terminal
- AJACCIO
- ALGER
- BéJAïA
- BASTIA
- L'ÎLE-ROUSSE
- MARSEILLE
- PROPRIANO
- SèTE
- TUNIS
Over time
Overall score across the last 14 checks — unchanged since 2026-10-14.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-02 | 66.6 | first check |
| 2026-10-03 | 66.8 | up 0.2 |
| 2026-10-04 | 66.6 | down 0.2 |
| 2026-10-05 | 66.8 | up 0.2 |
| 2026-10-06 | 68.5 | up 1.7 |
| 2026-10-07 | 68.5 | no change |
| 2026-10-08 | 77.4 | up 8.9 |
| 2026-10-09 | 77.4 | no change |
| 2026-10-10 | 77.4 | no change |
| 2026-10-11 | 77.4 | no change |
| 2026-10-12 | 77.4 | no change |
| 2026-10-13 | 77.4 | no change |
| 2026-10-14 | 77.4 | no change |
| 2026-10-15 | 77.4 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-10-14 to 2026-10-15 (2 checks) | 1476991c5297 | 2027-09-12 | Current rubric: see the trend above |
| 2026-10-13 | ae2748c850c5 | 2027-09-12 | Current rubric: see the trend above |
| 2026-10-09 to 2026-10-12 (4 checks) | fa09090884ef | 2027-09-12 | Current rubric: see the trend above |
| 2026-10-08 | 4013a0d3224f | 2027-09-12 | Current rubric: see the trend above |
| 2026-10-07 | c1f25d491e41 | 2027-09-12 | Current rubric: see the trend above |
| 2026-10-06 | 5fd5c39c806e | 2027-09-12 | Current rubric: see the trend above |
| 2026-10-04 to 2026-10-05 (2 checks) | 36084cfa6e51 | 2027-09-12 | Current rubric: see the trend above |
| 2026-10-03 | bfc5618e2611 | 2027-09-12 | Current rubric: see the trend above |
| 2026-10-02 | 5020f6f90c2a | 2027-09-12 | Current rubric: see the trend above |
| 2026-09-30 to 2026-10-01 (2 checks) | 113dbfbe7cf2 | 2027-09-12 | D, 66.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-09-27 to 2026-09-29 (3 checks) | 302484c3409c | 2027-09-12 | D, 68.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-09-26 | dc69aead897c | 2027-09-12 | D, 68.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
Showing the 12 most recent of 35 periods.
What changed over time
On 2026-10-02 this feed started at grade D. On 2026-10-08 the grade moved from D to C. As of 2026-10-15 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-10-08 Grade went D to C, correctness rose 20 points.
Everything we checked
7 findings, ordered by severity.
Show every finding
- Warning1649 instances
1649 of 1649 trips have no headsign, the text that tells riders where the vessel is going. A trip counts when it has trip_headsign or a stop_headsign at every terminal.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: 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. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide for scorecard_missing_headsigns · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide for missing_recommended_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide for scorecard_missing_feed_info_dates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: 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. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info7 instances
About 7 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide for scorecard_stop_names_all_caps · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Awarded
This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every terminal and trip.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 332 days.
- Accessible Met
- States wheelchair access on 100% of terminals and 100% of trips.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every terminal and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every terminal and trip. Accessibility here measures what the feed publishes, not whether a terminal is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 331 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.
- Correctness 92 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
- Freshness 85 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
- Rider experience 51 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Part of the France portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Corse
Other scorecards in Corse, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/fr-pan-83510/2026-10-15.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-10-15. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.