Feed status · checked 2026-07-17
Brittany Ferries
Based on the feed this agency publishes
Service mode Ferry
First scorecard for this agency
Catalogued in Bretagne, France.
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.2, validator 8.0.1.
Measured 3 of 4 score categories from the agency's own feed.
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 agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Populate trip_headsign to match the published sailing destination.Likely your export tool
6219 of 6219 trips have no headsign. Riders at the terminal can't tell which destination a sailing serves.
⏱ Usually a bulk edit in your scheduling software.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.
⏱ 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.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
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.
Populate trip_headsign to match the published sailing destination. · Read the fix guide
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. Self-check a feed before you publish.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide
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. Self-check a feed before you publish.
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. · Read the fix guide
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. Self-check a feed before you publish.
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 368 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 labelled as whole-feed. Unknown values are not treated as no.
- Ferry service
- 27 routes · 6,219 trips
- Terminal structure
- 12 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 (12 of 12). Unstated values remain unknown. 100% of ferry trips publish a value; 100% of all ferry trips explicitly say allowed (6,219 of 6,219). 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 (6,219 of 6,219). Unstated values remain unknown.
- Cars
- 100% of ferry trips publish a value; 100% of all ferry trips explicitly say allowed (6,219 of 6,219). 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 7 kinds of issue across 6316 instances (0 error, 97 warning, 6219 informational).
Service data covers the next 368 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.
Skip to route and terminal dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and terminals: this agency's GTFS feed.
| Route | Type | Line color |
|---|---|---|
| FR LEH-GB PME LE HAVRE-PORTSMOUTH | Ferry | teal (no shape in feed) |
| ES BIO-IE ROE BILBAO-ROSSLARE | Ferry | teal (no shape in feed) |
| ES BIO-GB PME BILBAO-PORTSMOUTH | Ferry | teal (no shape in feed) |
| IE ORK-FR ROS CORK-ROSCOFF | Ferry | teal (no shape in feed) |
| FR CER-GB POO CHERBOURG-POOLE | Ferry | teal (no shape in feed) |
| FR CER-IE ROE CHERBOURG-ROSSLARE | Ferry | teal (no shape in feed) |
| FR CER-GB PME CHERBOURG-PORTSMOUTH | Ferry | teal (no shape in feed) |
| GB POO-FR CER POOLE-CHERBOURG | Ferry | teal (no shape in feed) |
| FR SML-GB PME ST MALO-PORTSMOUTH | Ferry | teal (no shape in feed) |
| FR OUI-GB PME OUISTREHAM-PORTSMOUTH | Ferry | teal (no shape in feed) |
| IE ROE-ES BIO ROSSLARE-BILBAO | Ferry | teal (no shape in feed) |
| IE ROE-FR CER ROSSLARE-CHERBOURG | Ferry | teal (no shape in feed) |
| IE ROE-ES SDR ROSSLARE-SANTANDER | Ferry | teal (no shape in feed) |
| GB PME-FR LEH PORTSMOUTH-LE HAVRE | Ferry | teal (no shape in feed) |
| GB PME-ES BIO PORTSMOUTH-BILBAO | Ferry | teal (no shape in feed) |
| GB PME-FR CER PORTSMOUTH-CHERBOURG | Ferry | teal (no shape in feed) |
| GB PME-FR SML PORTSMOUTH-ST MALO | Ferry | teal (no shape in feed) |
| GB PME-FR OUI PORTSMOUTH-OUISTREHAM | Ferry | teal (no shape in feed) |
| GB PME-FR ROS PORTSMOUTH-ROSCOFF | Ferry | teal (no shape in feed) |
| GB PME-ES SDR PORTSMOUTH-SANTANDER | Ferry | teal (no shape in feed) |
| FR ROS-IE ORK ROSCOFF-CORK | Ferry | teal (no shape in feed) |
| FR ROS-GB PLY ROSCOFF-PLYMOUTH | Ferry | teal (no shape in feed) |
| ES SDR-GB PME SANTANDER-PORTSMOUTH | Ferry | teal (no shape in feed) |
| ES SDR-GB PLY SANTANDER-PLYMOUTH | Ferry | teal (no shape in feed) |
| GB PLY-FR SML PLYMOUTH-ST MALO | Ferry | teal (no shape in feed) |
| GB PLY-FR ROS PLYMOUTH-ROSCOFF | Ferry | teal (no shape in feed) |
| GB PLY-ES SDR PLYMOUTH-SANTANDER | Ferry | teal (no shape in feed) |
This feed has 12 terminals.
List every terminal
- Bilbao
- Santander
- Cherbourg
- Le Havre
- Caen - Ouistreham
- Roscoff
- Saint-Malo
- Plymouth
- Portsmouth
- Poole
- Cork
- Rosslare
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
11 findings, ordered by severity.
Show every finding
- Warning6219 instances
6219 of 6219 trips have no headsign.
Riders at the terminal can't tell which destination a sailing serves.
Fix: Populate trip_headsign to match the published sailing destination. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning54 instances
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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning27 instances
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 instances
Some scheduled trips move faster between stops than a vessel can.
Usually a typo'd stop time; riders get arrival times no vessel can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 instances
Fast travel between far stops (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'fast_travel_between_far_stops' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Leading or trailing whitespaces (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'leading_or_trailing_whitespaces' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules 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.)
Validator rule: missing_recommended_file · Read the fix guide · 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.)
Validator rule: scorecard_missing_feed_info_dates · Read the fix guide · 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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info6219 instances
Unsorted stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: scorecard_no_feed_contact · Read the fix guide · 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 368 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 368 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 65 / 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 62 / 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.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
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/brittany-ferries/2026-07-17.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-17. 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.