Feed status · checked 2026-07-24
Réseau urbain Linéotim
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
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 +24 points in its category
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.
⏱ Varies.worth about +24 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
581 of 583 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
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 '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. Self-check a feed before you publish.
Review the rule documentation for 'point_near_origin' 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.
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.
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 149 days.
- Published accessibility data
- Accessibility information is stated for 0.3% of stops and 0% 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 14 kinds of issue across 15387 instances (139 error, 15026 warning, 222 informational).
Service data covers the next 149 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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
17 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (L1, L3, L3, L4, N2, 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.
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.
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.
- L1 (red)
- L2 (green)
- L3 (teal)
- L3 (teal)
- L4 (purple)
- L5 (orange)
- L6 (teal)
- N1 (pink)
- N2 (green)
- L20B (green)
- L20 (green)
- L40E (red)
- L40 (brown)
- L50 (orange)
- L60 (purple)
- L70 (green)
- L80 (red)
| Route | Type | Line color |
|---|---|---|
| L1 LIGNE 1 | Bus | red |
| L2 LIGNE 2 | Bus | green |
| L3 LIGNE 3 | Bus | teal |
| L3 LIGNE 3 - ajout des 3 arrêts plj | Bus | teal |
| L4 LIGNE 4 | Bus | purple |
| L5 L5 MORLAIX - PLOURIN LES MORLAIX | Bus | orange |
| L6 L6 MYRTILLES - PLACE CORNIC | Bus | teal |
| N1 NAVETTE 1 | Bus | pink (no shape in feed) |
| N1 L N1 ST FRANCOIS - VAL FLEURI | Bus | pink |
| N2 L N2 GARE - PLACE CORNIC | Bus | green |
| L20B L 20+ PLOUGASNOU - PLOUEZOC'H | Bus | green (no shape in feed) |
| L20B L 20+ PLOUGASNOU - PLOUEZOC'H | Bus | green |
| L20 L 20 MORLAIX - ST JEAN DU DOIGT | Bus | green |
| L40E LIGNE 40 EXPRESS | Bus | red |
| L40 LIGNE 40 MORLAIX - BOTSORHEL | Bus | brown (no shape in feed) |
| L40 LIGNE 40 MORLAIX - BOTSORHEL | Bus | brown |
| L50 L50 CLOITRE- PLOURIN LES MORLAIX | Bus | orange |
| L60 L60 MORLAIX - PLOUNEOUR MENEZ | Bus | purple |
| L70 L70 ST THEGONNEC - MORLAIX | Bus | green (no shape in feed) |
| L70 L70 ST THEGONNEC - MORLAIX | Bus | green |
| L80 LIGNE 80 CARANTEC - MORLAIX | Bus | red (no shape in feed) |
| L80 LIGNE 80 CARANTEC - MORLAIX | Bus | red (no shape in feed) |
| L80 LIGNE 80 CARANTEC - MORLAIX | Bus | red |
This feed has 552 stops.
List every stop
- Les 100 Marches
- Les 100 Marches
- Aéroport
- AFPA
- AFPA
- Albert le Grand
- Albert le Grand
- Auberge de Jeunesse
- Auberge de Jeunesse
- Ancien Lycée
- Castoret
- Clinique de la Baie
- Clinique de la Baie
- C. Cial. La Boissière
- C. Cial. La Boissière
- C. Cial. La Boissière
- CCI
- CCI
- Cézanne
- Cézanne
- Le Château
- Cluzeret
- Cluzeret
- Mendès France
- Mendès France
- Centre Multi-Services
- Centre Multi-Services
- Coat Serho
- Coat Serho
- Cordelière
- Rue de Callac
- Rue de Callac
- Dupoux
- Dupoux
- Les Écureuils
- Les Écureuils
- Kerozar
- Émile Souvestre
- Émile Souvestre
- Émile Zola
- Émile Zola
- Val Fleuri
- Val Fleuri
- Gambetta
- Gambetta
- Guillaume Le Jean
- Grand Monarque
- Grand Monarque
- Gare SNCF Sud
- Gare SNCF Sud
- Gare SNCF Nord
- Gare SNCF Nord
- Les Hermines
- Les Hermines
- Hôpital
- Hôpital
- IUT
- IUT
- Jackson
- Jackson
- Jean Jaurès
- Jean Jaurès
- Jean Caerou
- Jean Caerou
- Kerfraval
- Kerfraval
- Kergariou
- Kergariou
- Kerosar
- Kerscoff
- Kerscoff
- Kerveguen
- Kersaint Gilly
- Langevin
- Langevin
- Courbet
- Courbet
- Les Écluses
- Les Écluses
- L'Orée Du Bois
- L'Orée Du Bois
- La Madelaine
- La Madelaine
- Hôtel de Ville
- Marc'Hallach
- Les Morlaisiennes
- Les Morlaisiennes
- Pont Bellec
- Pont Bellec
- Penlan
- Palais de Justice
- Palais de Justice
- Place Cornic Tregor
- Place Cornic
- Place St-Fiacre
- Place St-Fiacre
- Place Pouliet
- Place Pouliet
- Poulfanc
- Poulfanc
- République
- République
- Maison de Retraite
- Maison de Retraite
- Roz Ar Hoat
- Roz Ar Hoat
- Rue de Ploujean
- Rue de Ploujean
- Rampe St-Augustin
- Rampe St-Augustin
- Serusier
- Serusier
- Sew - Manufacture
- Sew - Manufacture
- Ste-Marthe
- Ste-Marthe
- Solidarité
- St-François
- St-Germain
- St-Germain
- St-Joseph
- St-Nicolas
- St-Nicolas
- Théâtre
- Théâtre
- Traon en Velin
- Traon en Velin
- Traoulen
- Traoulen
- Trévidy
- Truro
- Truro
- Rue des Tulipes
- Rue des Tulipes
- De Vinci
- De Vinci
- Villeneuve
- Villeneuve
- Vierge Noire
- Vierge Noire
- Rue de la Baie
- Ploujean Église
- Keredern
- Kermahotou
- Kermaria
- Les Perdrix
- Pervenche
- Ploujean Place
- Pont Coz
- Pont Coz
- Plourin Bourg
- C. Cial. St-Fiacre
- Espace Aquatique
- Guy Le Normand
- Guy Le Normand
- Kersody
- Kersody
- Papillons
- Papillons
- Le Pilion
- Le Pilion
- Lycée Tristan Corbière
- Lycée Tristan Corbière
- Les 100 Marches
- Aéroport
- AFPA
- Albert le Grand
- Auberge de Jeunesse
- Ancien Lycée
- Castoret
- Clinique de la Baie
- C. Cial. La Boissière
- CCI
- Cézanne
- Le Château
- Cluzeret
- Mendès France
- Centre Multi-Services
- Coat Serho
- Cordelière
- Rue de Callac
- Dupoux
- Les Écureuils
- Kerozar
- Émile Souvestre
- Émile Zola
- Val Fleuri
- Gambetta
- Guillaume Le Jean
- Grand Monarque
- Gare SNCF Sud
- Gare SNCF Nord
- Les Hermines
- Hôpital
- IUT
- Jackson
- Jean Jaurès
- Jean Caerou
- Kerfraval
- Kergariou
- Kerosar
- Kerscoff
- Kerveguen
- Kersaint Gilly
- Langevin
- Courbet
- Les Écluses
- L'Orée Du Bois
- La Madelaine
- Morlaix Hôtel de Ville
- Marc'Hallach
- Les Morlaisiennes
- Pont Bellec
- Penlan
- Palais de Justice
- Place Cornic
- Place St-Fiacre
- Place Pouliet
- Poulfanc
- République
- Maison de Retraite
- Roz Ar Hoat
- Rue de Ploujean
- Rampe St-Augustin
- Serusier
- Sew - Manufacture
- Ste-Marthe
- Solidarité
- St-François
- St-Germain
- St-Joseph
- St-Nicolas
- Théâtre
- Traon en Velin
- Traoulen
- Trévidy
- Truro
- Rue des Tulipes
- De Vinci
- Villeneuve
- Vierge Noire
- Rue de la Baie
- Ploujean Église
- Keredern
- Kermahotou
- Kermaria
- Les Perdrix
- Pervanche
- Ploujean Place
- Pont Coz
- and 302 more (see the full list on the map or in the GeoJSON)
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
19 findings, ordered by severity.
Show every finding
- Error75 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.)
Validator rule: equal_shape_distance_diff_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error64 instances
Point near origin (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'point_near_origin' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: point_near_origin · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning14153 instances
Missing timepoint value (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_timepoint_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning762 instances
762 of 762 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning581 instances
581 of 583 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)
- Warning519 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)
- Warning208 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)
- Warning95 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus 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)
- Warning31 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)
- Warning8 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.)
Validator rule: unexpected_enum_value · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Validator rule: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Validator rule: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Two or more routes share the same name.
Riders can't tell the routes apart in apps.
Fix: Give each route a distinct short or long name. (One field per route.)
Validator rule: duplicate_route_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Validator rule: missing_feed_contact_email_and_url · 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)
- 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)
- Info221 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 valid beyond total service window (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'feed_valid_beyond_total_service_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: feed_valid_beyond_total_service_window · 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 Not yet
This feed is close to the conformance mark. 2 validator errors to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Met
- Service data covers the next 149 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% 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 149 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 139 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 0 / 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 38 / 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-82291/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.