Feed status · checked 2026-07-24
Réseau urbain Distribus
Based on the feed this agency publishes
Service mode Bus
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
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
216 of 216 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 +25 points in its category
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.
Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +8 points in its category
Re-generate shape_dist_traveled on export so stop and shape distances use the same units.Likely your export tool
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.
⏱ Usually an export-tool fix, not hand editing.worth about +8 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.
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. Self-check a feed before you publish.
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.
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.
Re-generate shape_dist_traveled on export so stop and shape distances use the same units. · 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 160 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- 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 7 kinds of issue across 3058 instances (0 error, 2763 warning, 295 informational).
Service data covers the next 160 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Citadine 2, Estivale 5, Estivale 6, Estivale 7, Chrono Parc d'Activité de La Tourelle).
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.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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.
Fares are applied to trips.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- Citadine 1 (green)
- Citadine 2 (gray)
- Terre & Mer 3 (brown)
- Terre & Mer 4 (brown)
- Estivale 5 (teal)
- Chrono Parc d'Activité de La Tourelle (orange)
- Estivale 6 (green)
- Estivale 7 (pink)
| Route | Type | Line color |
|---|---|---|
| Citadine 1 Armor - Gendarmerie | Bus | green |
| Citadine 2 Rond-Point de Lanjouan - Gare SNCF via Clémenceau | Bus | gray |
| Terre & Mer 3 Lamballe-Armor - Pléneuf-Val-André | Bus | brown |
| Terre & Mer 4 Lamballe-Armor - Erquy | Bus | brown |
| Estivale 5 Navette estivale de Pléneuf-Val-André | Bus | teal |
| Chrono Parc d'Activité de La Tourelle Lamballe Armor - Parc d'Activité de La Tourelle | Bus | orange |
| Estivale 6 Navette estivale Erquy et Plurien | Bus | green |
| Estivale 7 Navette estivale de Erquy | Bus | pink |
This feed has 216 stops.
List every stop
- Camping du Vieux Moulin
- Armor
- Bouin
- Général Leclerc
- Clémenceau
- Croix de la Mission
- Croix de la Mission
- Croix de la Mission
- Aire de Camping Car Le Guen
- Camping des Pins
- Aire de Camping Car Le Guen
- Charner
- 115 Rue Clémenceau
- 115 Rue Clémenceau
- Rond-point de Lanjouan
- Rond-point de Lanjouan
- Collège S.Veil
- Résidence séniors
- Résidence séniors
- Résidence séniors
- Mille-Club-Kennedy
- Mille-Club-Kennedy
- Salle Guémadeuc
- Salle Guémadeuc
- Salle Guémadeuc
- Charner
- Charner
- Plages des Vallées
- Plages des Vallées
- Maison de la Santé
- Maison de la Santé
- Maison de la Santé
- Parking La Moinerie
- Parking La Moinerie
- Camping Les Salines
- Penthièvre
- Ville-ès-Lan
- Camping Saint-Pabu
- Aire de Camping Car Le Guen
- Jeu de Paume
- Cimetière
- Camping des Hautes Grées
- Camping des Hautes Grées
- Camping des Hautes Grées
- Camping Saint-Michel
- Camping Saint-Michel
- Camping Les Salines
- Stade
- Lourmel
- Ateliers Pifaudais
- Parking La Moinerie
- Parking des Caps
- Parking des Caps
- Les Jeannettes - rue des Jeannettes
- Les Jeannettes - rue des Jeannettes
- Croix de la Mission
- Armor
- Armor
- Mairie
- Rond-point de Lanjouan
- Le Poirier - route de Saint-Alban
- Camping Saint-Pabu
- Camping Les Roches
- Camping Les Roches
- Camping Les Roches
- Camping La Vallée
- Camping La Vallée
- Camping La Vallée
- Camping Bellevue
- Camping Bellevue
- Camping Bellevue
- Camping Saint-Pabu
- Les Jeannettes - rue de Clairville
- Général de Gaulle
- Haras
- Général de Gaulle
- Rue Georges Le Breton
- Rue Georges Le Breton
- Liffré
- Liffré
- Liffré
- Stade
- Stade
- Collège S.Veil
- Lanjouan
- Lanjouan
- Lanjouan
- Lanruen
- Lanruen
- Bouin
- Camping du Val
- Camping du Val
- Camping du Val
- Parking-Relais La Princelle
- Parking-Relais La Princelle
- Becquerel
- Becquerel
- Pierre et Marie Curie
- Pierre et Marie Curie
- Eglise
- Les Hôpitaux
- Camping du Vieux Moulin
- Caroual
- La Couture
- La Croix du Val
- Olympiades
- Gare
- Penthièvre
- Stade L.Hingant
- Lycée Henri Avril
- Ateliers Pifaudais
- Saint-Aaron Centre
- Lycée Saint-Joseph
- Gendarmerie
- Lavergne
- Place du Marché
- Ville-ès-Lan
- Beaulieu
- Plan d'eau
- Plessix
- Béloir
- Haras
- Les Grands Jardins
- La Poste
- Cimetière
- Maréchal Foch
- Pot au Chat
- Jeu de Paume
- Mairie
- Centre
- Collège Jean Richepin
- Collège Sainte-Anne - Saint-Joseph
- Dahouët Le Minihy
- Dahouët Le Port
- Eglise
- La Boulaie
- La Caderie
- Centre
- Le Poirier - route de Pléneuf
- Les Jeannettes - rue des Jeannettes
- La Vollée
- Haras
- Saint-Aaron Centre
- Saint-Aaron Centre
- Centre
- Centre
- Le Poirier - route de Pléneuf
- Eglise
- Eglise
- Les Jeannettes - rue de Clairville
- Les Jeannettes - rue de Clairville
- Caroual
- Caroual
- La Couture
- Les Hôpitaux
- La Croix du Val
- La Croix du Val
- Clémenceau
- Pot au Chat
- Penthièvre
- Stade L.Hingant
- Les Grands Jardins
- Beaulieu
- Lavergne
- Béloir
- Général Leclerc
- Place du Marché
- Jeu de Paume
- Général de Gaulle
- Cimetière
- Olympiades
- Lycée Henri Avril
- Plan d'eau
- Maréchal Foch
- Ateliers Pifaudais
- La Poste
- Ville-ès-Lan
- Gare
- Gare Routière
- Eglise
- Lourmel
- Dahouët Le Port
- Dahouët Le Port
- Dahouët Le Minihy
- Dahouët Le Minihy
- La Boulaie
- La Boulaie
- Collège Jean Richepin
- La Caderie
- Centre
- Camping du Vieux Moulin
- Camping des Pins
- La Couture
- Les Hôpitaux
- Mairie
- Collège Sainte-Anne - Saint-Joseph
- Le Poirier - route de Saint-Alban
- Le Poirier - route de Saint-Alban
- Lycée Saint-Joseph
- Plessix
- Olympiades
- Gendarmerie
- La Vollée
- La Vollée
- Gare Routière
- Place du Marché
- Plessix
- Stade L.Hingant
- Maréchal Foch
- Plan d'eau
- Lycée Henri Avril
- Général de Gaulle
- Beaulieu
- Les Grands Jardins
- Lycée Saint-Joseph
- Lavergne
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
9 findings, ordered by severity.
Show every finding
- Warning2345 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.)
Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning279 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.)
Validator rule: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning216 instances
216 of 216 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning134 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Validator rule: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 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)
- Warning1 instance
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.)
Validator rule: unexpected_enum_value · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Validator rule: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info295 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.)
Validator rule: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 160 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% 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 160 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 63 / 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 100 / 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 75 / 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-79528/2026-07-24.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-07-24. 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.