Feed status · checked 2026-09-07
Réseau interurbain BreizhGo Car — Breizhgo Car 56
Based on the official feed source on file
Service mode Bus
unchanged since 2026-09-06
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.3, validator 8.0.1.
Checked for changes 4 hours ago; last changed 4 hours 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.
Top things to fix
Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +24 points in its category
Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Equal shape distance diff coordinates (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
339 of 458 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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +18 points in its category
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
- Trip distance exceeds shape distance (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'trip_distance_exceeds_shape_distance' 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
- Feed evidence
- Equal shape distance diff coordinates (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'equal_shape_distance_diff_coordinates' 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
- Feed evidence
- 339 of 458 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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.
Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · 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. 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 299 days.
- Published accessibility data
- Accessibility information is stated for 26% of stops and 78.5% of trips. This measures published data, not whether stops or vehicles 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.
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 10 kinds of issue across 487 instances (83 error, 245 warning, 159 informational).
Service data covers the next 299 days.
26% of stops state wheelchair accessibility (26% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
26% of stops state accessibility (26% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (608, 606, 601, 615, 616, and more).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
9 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Lycées st Joseph - Notre Dame de la paix", "Lycées Dupuy de Lôme - St Louis", "Lycées Dupuy de Lôme - St Louis", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 458 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 220 (white)
- 603 (yellow)
- 602 (yellow)
- 619 (white)
- 607 (blue)
- 608 (teal)
- 605 (red)
- 610 (blue)
- 606 (gray)
- 617 (red)
- 611 (brown)
- 609 (orange)
- 615 (gray)
- 601 (brown)
- 616 (gray)
- 604 (brown)
- 618 (brown)
| Route | Type | Line color |
|---|---|---|
| 220 Loudéac - Rostrenen - Carhaix | Bus | white |
| 603 Vannes-Pontivy-Loudéac-St Brieuc | Bus | yellow |
| 602 Baud - Camors - Grand-Champ - Vannes | Bus | yellow |
| 619 Auray-Carnac | Bus | white |
| 607 Auray - Vannes | Bus | blue |
| 608 La Roche Bernard - Muzillac - Vannes | Bus | teal |
| 605 Baud - Auray | Bus | red |
| 610 Pénestin - La Roche Bernard - Redon | Bus | blue |
| 606 Vannes - Auray | Bus | gray |
| 617 Pontivy - Baud - Lorient | Bus | red |
| 611 St-Jean-Brévelay - Plumelec - Monterblanc - Vannes | Bus | brown |
| 609 Rochefort-en-Terre - Questembert - Vannes | Bus | orange |
| 615 Carhaix - Gourin - Le Faouet - Lorient | Bus | gray |
| 601 Auray-Quiberon | Bus | brown |
| 616 Lorient - Kervignac - Etel | Bus | gray |
| 604 Ploermel - Malestroit - Vannes | Bus | brown |
| 618 Auray-Etel | Bus | brown |
List every stop
- Collège Edouard Herriot
- Aire de Covoiturage La Ville Louis
- Aire de Covoiturage La Ville Louis
- Gendarmerie
- Piscine
- Pont Herbot
- Champ de Foire
- Centre
- Centre
- Leinhon
- Leinhon
- La Pie
- La Pie
- Keroguiou
- Keroguiou
- L'Enseigne
- L'Enseigne
- Centre
- Centre
- La Montagne
- La Montagne
- Le Carbon Centre
- Le Carbon Centre
- Tachen Ar Groas
- Tachen Ar Groas
- Bourg
- Centre
- Centre
- Guénaric
- Guénaric
- Lanhellen
- Lanhellen
- Croix Julou
- Croix Julou
- Centre
- Centre
- Lycée Rosa Parks
- Lycée Rosa Parks
- Croix Madeleine
- Croix Madeleine
- Hôpital
- Hôpital
- Centre
- Centre
- Centre
- Centre
- Kernévez
- Kernévez
- Bon Repos
- Bon Repos
- Ty Bris
- Ty Bris
- Chapelle Saint-Golven
- Eglise
- Eglise
- Mûr de Bretagne place Ste-Suzanne
- Mûr de Bretagne place Ste-Suzanne
- Mûr de Bretagne Coët Prat
- Mûr de Bretagne Coët Prat
- Rue Nationale
- Rue Nationale
- Ker Hervé
- Ker Hervé
- Champ de Foire
- Kerberri
- Chapelle Saint-Golven
- Quilliou-Gueguen
- Eglise
- Hôpital
- Hôpital
- Lycée Diwan
- Lycée Paul Sérusier
- Gare SNCF
- Kennedy
- Kennedy
- PEM - REHUMPOL
- Place Villa Vicentina
- Collec
- Collec
- Bd de Bretagne
- Place de l'église
- Gare Maritime - Port Maria
- Gare SNCF
- Saint Julien
- Saint Julien
- Le Rohu
- Le Rohu
- Keridenvel
- Keridenvel
- Centre culturel
- Centre culturel
- Kerhostin
- Kerhostin
- Penthièvre
- Penthièvre
- Place De Gaulle
- Place De Gaulle
- Les Sables Blancs
- Les Sables Blancs
- Purgatoire
- Purgatoire
- Kergroix
- Kergroix
- Plage - office du tourisme
- Plage - office du tourisme
- Les Salines
- Illertissen
- Beaumer
- Gare Routière
- Porte Océane
- Porte Océane
- Le Ballon - JF Kennedy
- Le Ballon - JF Kennedy
- Corn Er Hoët
- Corn Er Hoët
- Les 4 Chemins
- les 4 Chemins
- Talhouet
- Talhouet
- La Gare
- La Gare
- Le Vorlen
- Le Vorlen
- Gare Routière
- Gare Routière
- La Barrière
- La Barrière
- Locoal-Camors
- Locoal-Camors
- Rond point du Pratel
- Rond point du Pratel
- Ste Avoye
- Ste Avoye
- Mériadec Kerhouil
- Mairie
- Mairie
- La Poste
- La Poste
- Kerdeliau
- Kerdeliau
- Cheval Blanc
- Cheval Blanc
- Mériadec Centre
- Lann Guerban
- Lann Guerban
- Kerfontaine
- Kerfontaine
- Gare Ste Annne
- Gare Ste Anne
- Bibliothèque
- Bibliothèque
- Mériadec Kerhouarn
- Mériadec Kerhouarn
- Mériadec Kerhouil
- Mériadec St-Roch
- Mériadec St-Roch
- Kerluherne
- Kerluherne
- Rue de Floranges
- Rue de Floranges
- Place de l'église
- Place de l'église
- Le Poteau
- Le Poteau
- Lann Guinet
- Lann Guinet
- Champolion
- Champolion
- Bd du stade
- Bd du stade
- Gare Routière
- Place de la Libération
- Kerniol
- Kerniol
- Giratiore de Kerchopine
- Giratiore de Kerchopine
- ESAT
- ESAT
- Kersec
- Kersec
- Renaudot
- Renaudot
- Troadec
- Troadec
- Le Fourchêne
- Rue Raymond Marcellin
- Rue Raymond Marcellin
- Saint Léonard
- Saint Léonard
- Le Poulfanc
- Le Poulfanc
- Bas du bourg
- Bas du bourg
- Centre
- Centre
- Saint Gourlais
- Saint Gourlais
- Pen Mur
- Pen Mur
- Le Parc
- Le Parc
- Hinzal
- Hinzal
- Pl. De La Duchesse Anne
- Aire de covoiturage - Giratoire Bel Air
- Hôtel Albatros
- Av. Charles De Gaulle
- Kerhellec
- Aire de covoiturage de la corne du cerf
- Barrage
- Centre
- Espace Littoral
- Espace Littoral
- Requerio
- Requerio
- Sainte Julitte
- Sainte Julitte
- Centre
- Centre
- Le Roscoêt
- Le Roscoêt
- Le Saindo
- Le Saindo
- Talhouêt
- Talhouêt
- Salarun
- Salarun
- Turluman
- Turluman
- Laverdon
- Laverdon
- Rue St Hernin
- Rue St Hernin
- Bel Air - Questembert Communauté
- Bel Air - Questembert Communauté
- Lenruit
- Lenruit
- Mairie
- Saint -Roch
- Saint -Roch
- Cimetière
- Cimetière
- Coêt Ruel
- Coêt Ruel
- Lamboux
- Bel Orient
- Bel Orient
- Giratoire Loïc Bouvard
- Giratoire Loïc Bouvard
- Place Queinnec
- and 208 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-09-06.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 51.8 | first check |
| 2026-08-07 | 51.8 | no change |
| 2026-09-06 | 48.7 | down 3.1 |
| 2026-09-07 | 48.7 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-09-06.
The feed file was re-published since 2026-09-06 (+1 KB).
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
What changed over time
On 2026-08-06 this feed started at grade F. On 2026-09-06 the check no longer reported: some route colors don't contrast with their text color. As of 2026-09-07 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-09-06 Score fell 3 points, correctness fell 6 points.
Everything we checked
15 findings, ordered by severity.
Show every finding
- Error78 instances
Trip distance exceeds shape distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error5 instances
Equal shape distance diff coordinates (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: equal_shape_distance_diff_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning339 instances
339 of 458 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.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning147 instances
Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning110 instances
110 of 511 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning57 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning19 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning17 instances
Unexpected enum value (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unexpected_enum_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unexpected_enum_value · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 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.)
Finding code: mixed_case_recommended_field · Read the fix guide · 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.)
Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · 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 · 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 · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info159 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · 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).
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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
Two requirements remain for this feed to earn the conformance mark. 2 validator errors to resolve. States wheelchair access on 26% of stops and 78% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Met
- Service data covers the next 299 days.
- Accessible Not yet
- States wheelchair access on 26% of stops and 78% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 299 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 83 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 23 / 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 56 / 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/fr-pan-81464/2026-09-07.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-09-07. 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.