Feed status · checked 2026-07-24
Réseau interurbain - Corrèze (19)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Nouvelle-Aquitaine, 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
Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool
Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.
⏱ Usually an export-tool fix, not hand editing.worth about +18 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
180 of 180 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.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
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.
Re-generate shape distances in your export; flag to your vendor if it persists.
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_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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.
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 358 days.
- Published accessibility data
- Accessibility information is stated for 70.6% 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 9 kinds of issue across 1285 instances (19 error, 987 warning, 279 informational).
Service data covers the next 358 days.
71% of stops state wheelchair accessibility (0% marked accessible, 71% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
71% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
24 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("ST ANTOINE LES PLANTADES (R)", "BOURG CROISEMENT RD", "BARRIERE ST LAURENT (R)", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
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.
- 225 (yellow)
- 271 (yellow)
- 224 (yellow)
- 223 (yellow)
- 239 (yellow)
- 272 (yellow)
- 221 (yellow)
- 222 (yellow)
- 273 (yellow)
- 362 (yellow)
- 364 (yellow)
- 553 (yellow)
- 555 (yellow)
- 650 (yellow)
- 1210 (yellow)
| Route | Type | Line color |
|---|---|---|
| 225 LR 225 - ST PRIVAT - ARGENTAT - BRIVE | Bus | yellow |
| 271 LR 271 - TULLE - BRIVE | Bus | yellow |
| 224 LR 224 - VAYRAC - BRIVE | Bus | yellow |
| 223 LR 223 - MEYSSAC - BRIVE | Bus | yellow |
| 239 LR 239 - LUBERSAC - OBJAT - BRIVE | Bus | yellow |
| 272 LR 272 - TULLE - LIMOGES | Bus | yellow |
| 221 LR 221 - UZERCHE - BRIVE | Bus | yellow |
| 222 LR 222 - BEAULIEU - BRIVE | Bus | yellow |
| 273 LR 273 - ARGENTAT - TULLE | Bus | yellow |
| 362 TAD 3-62 - SAINTE FORTUNADE - BRIVE | Bus | yellow |
| 364 TAD 3-64 - BEAULIEU SUR DORDOGNE - TULLE | Bus | yellow |
| 553 TAD 5-53 - BUGEAT - USSEL | Bus | yellow |
| 555 TAD 5-55 - MEYMAC - USSEL | Bus | yellow |
| 650 TAD 6-50 - MARCILLAC LA CROISILLE - TULLE | Bus | yellow |
| 1210 TAD 12-10 - NEUVIC - USSEL | Bus | yellow |
This feed has 707 stops.
List every stop
- QUAI GABRIEL PERI (R)
- LA POSTE
- LE BASTIER (R)
- LE BASTIER
- LA POSTE (R)
- LES SAGNES
- LES ESCROZES (R)
- LES ESCROZES
- PLACE DE L'ANCIENNE GARE (ABRIBUS) (R)
- PLACE DE L'ANCIENNE GARE (ABRIBUS)
- CABANIS (R)
- Chirac-3 Provinces
- CABANIS
- LES SAGNES (R)
- LES SAGNES
- GENDARMERIE (R)
- LA SERRE-THOMAS
- LE BOURG
- CHANTEGRIL
- EMBT. MAREGES
- LE BOURG (CIMETIERE)
- COLLEGE VOLTAIRE
- LPR ET LP B. DE VENTADOUR
- LE BOURG
- LE BOURG
- GARE SNCF
- LE BOURG
- BEAUNE
- PLACE HENRI QUEUILLE
- GARE SNCF
- LE BOURG
- BOURG (SALLE POLYVALENTE)
- LE BOURG
- GARE SNCF
- LE BOURG
- LA MECHAUSSIE
- LA VAYSSE
- LA CHAPELOUNE
- LE NOUAL
- LE BOURG
- LA CROIX D'EURE
- LES ROSES
- ALBUSSAC BOURG
- QUATRE ROUTES
- EYROLLES
- PLACE BRIGOULEIX
- LA SOULETIE
- POLE D'ECHANGES - GARE SNCF
- PUY DE NOIX
- LE BOURG
- LA GRAFFOUILLERE
- BEAULIEU BOURG
- TUDEILS BOURG
- CLAIRFAGE
- NONARD BOURG
- LE BOURG
- LE FEYT
- LE BOURG
- LE BOURG
- LE BOURG
- LA PRADOTTE
- LE BOURG
- LE GARDET
- CHAMP DE LA CROIX
- GARE SNCF
- LA PLATANE
- LE BOURG
- LE BOURG
- LE BOURG
- BOURG CROISEMENT RD
- OFFICE DU TOURISME
- LOTISSEMENT
- MAIRIE
- COLLEGE
- LE BOURG
- LE BOURG
- LE BOURG (EGLISE)
- LE BOURG (LA POSTE)
- ST BONNET BOURG
- LE BOURG (EGLISE)
- LE MORTIER
- LE BOURG
- 4 ROUTES (NEGUS)
- LE BOURG
- ROUTE DE SEDIERES
- MALEZE
- LE CHASTANET
- LA CIREYGEADE
- LE BOURG
- LES CAMBUSES
- LE BOURG
- PLACE JOURDAN
- NAVES BOURG
- AIRE COVOITURAGE LES BALLADOURS
- AFFIEUX BOURG
- VERGONJEANNE
- MEILHARDS BOURG (R)
- CHAMBOULIVE BOURG
- LA CAMBUSE
- GARE SNCF
- PLACE WINSTON CHURCHILL
- GARE SNCF
- LYCEE RENE CASSIN
- LE LONZAC BOURG
- LA GARE
- TREIGNAC BOURG (R)
- RILHAC TREIGNAC BOURG
- QUAI GABRIEL PERI
- PLACE SCHORNDORF
- CEYRAT
- AIRE COVOITURAGE LA COMBOTTE
- PEYRISSAC BOURG
- L.E.G.T.A.
- CHAMBERET BOURG
- CENTRE (PLACE DE L'HORLOGE)
- PONT NEUF
- AIRE COVOITURAGE LA GALAVIERE
- KOENIG
- BEYNAT BOURG
- PALISSE
- ROOSEVELT
- COLLEGE ROLLINAT
- UNIVERSITE
- MIEL
- GARE SNCF
- LES ROCHETTES
- HAUTEFAGE BOURG
- BOURG (LA POSTE)
- AVENUE DE LA GARE
- LANTEUIL BOURG
- SERVIERES BOURG
- LABENCHE
- ST PRIVAT BOURG
- CHAPELLE AUX BROCS BOURG
- PONT DU CAYRE
- BD MARECHAL LYAUTEY (R)
- POISSAC
- LA LIGNADE
- LACHAMP
- TASSIGNY
- COLLEGE JEAN LURCAT
- LE BAS DU BOURG
- ROND POINT PEYREGUDE
- PLACE DU 14 JUILLET
- LA CROIX ROUGE
- LE BOURG
- LES ALLEUX (TELLIS)
- TOUR DE SOUILHAC
- LE PERATEL ABRIBUS
- CENTRE COMMERCIAL EST
- CFA LES 13 VENTS
- GENDARMERIE
- AVENUE DE PARIS
- PEM 3 PROVINCES
- LES QUATRE ROUTES-PARKING GARE
- LE BOURG
- ST MICHEL-LE BOURG
- COLLEGE
- GARE
- TURENNE BOURG
- JUGEALS BOURG
- LP LAVOISIER
- MONTPLAISIR
- LA PLANCHE
- NOAILHAC BOURG
- LA ROUGERIE
- LA MARTINIE
- LA CORRESPONDANCE
- MEYSSAC BOURG
- PUY BOUBOU
- COLLEGE
- COLLONGES BOURG
- SOTHYS
- LE BURG
- LYCEE AGRICOLE MURAT
- VOUTEZAC BOURG
- MAIRIE
- Clairvivre
- LE BOURG (ABRIBUS)
- FIDUCIAL
- SANAS
- TROCHE BOURG
- ALLEE DES PLACES
- LE STADE (ABRIBUS)
- GARE SNCF
- AV. JULES FERRY (ABRIBUS)
- ST BONNET BOURG
- LES GRAVES BLANCHES
- BELLEVUE
- BARRIERE ST LAURENT
- LES FOMBIARDES
- D901 INTER LA PERCHE
- PLACE DU FOIRAIL
- GENDARMERIE
- PLACE JEAN LAGARDE
- LES JORDES
- FORGES BOURG
- PASTEUR
- LA CROIX DE FER
- LES QUATRE ROUTES
- INTERS. RTE DU STADE
- CHEZ GOUNET
- LA POURETTE
- ROND POINT BALADOURS
- MAUBEC
- PONT DES MALADES
- ESPEYRUT ARRET BUS
- LE BARIOLET
- LES REBIERES
- ST ANTOINE LES PLANTADES
- PONT DE LAGORCE
- CREDIT AGRICOLE
- LES TONDERIES
- LA CROIX DE LA MALEYRIE
- LE MALPAS
- LA FONSALADE
- LE GAULIAT
- PONT DES SAULIERES
- PONT DE L'HOPITAL
- LES CARS
- DONZENAC BOURG
- D15 EMBR LE PESCHER
- EMBR LE PARJADIS
- LA SOLEILLE
- MAIRIE
- MOULIN D'ABADIOL
- LE BOSPLOT
- D38 EMBT. PUY D'ARNAC
- LE PESCHER BOURG
- GARE SNCF
- LE BOURG
- LE BOURG
- Gare Routière
- Gare Routière
- Place Jourdan
- Clairvivre abri bus
- LE POTEAU (R)
- LE PLANCHAT
- MIEL (R)
- PALISSE (R)
- HAUTEFAGE BOURG (R)
- ROOSEVELT (R)
- ALBUSSAC BOURG (R)
- LES ROCHETTES (R)
- SERVIERES BOURG (R)
- ST PRIVAT BOURG (R)
- BEYNAT BOURG (R)
- LANTEUIL BOURG (R)
- PONT DU CAYRE (R)
- GARE SNCF (R)
- and 457 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
16 findings, ordered by severity.
Show every finding
- Error19 instances
Some trips have stop times whose distances along the route go backwards.
Apps can show buses jumping backwards or mis-order stops.
Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)
Validator rule: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning771 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
208 of 707 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)
- Warning180 instances
180 of 180 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)
- Warning145 instances
Same name and description for stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: same_name_and_description_for_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning30 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)
- Warning26 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.)
Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning14 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
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)
- 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)
- Info686 instances
About 686 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.)
Validator rule: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info180 instances
Trip with shape dist traveled but no shape distances (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_with_shape_dist_traveled_but_no_shape_distances' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: trip_with_shape_dist_traveled_but_no_shape_distances · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info99 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)
- 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. 1 validator error to resolve. States wheelchair access on 71% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 358 days.
- Accessible Not yet
- States wheelchair access on 71% 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 358 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 19 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 42 / 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 41 / 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-82328/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.