Feed status · checked 2026-07-24
Cars Régionaux 23 — Creuse
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
167 of 167 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 92.8% 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 10 kinds of issue across 476 instances (8 error, 201 warning, 267 informational).
Service data covers the next 358 days.
93% of stops state wheelchair accessibility (0% marked accessible, 93% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
93% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (250, 252, 254, 259, 284, 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.
82 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Face X D22/VC Neuville", "Les 4 Routes / RD942", "Pt Breuil Face AB/D982", 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.
- 212 (teal)
- 282 (red)
- 285 (yellow)
- 254 (red)
- 257 (purple)
- 258 (gray)
- 250 (pink)
- 210 (purple)
- 259 (brown)
- 281 (teal)
- 284 (teal)
- 255 (black)
- 252 (gray)
- 253 (red)
- 211 (brown)
| Route | Type | Line color |
|---|---|---|
| 212 212-DUN LE PALESTEL-LA SOUTERRAINE | Bus | teal |
| 282 282-AUZANCES-AUBUSSON-FELLETIN | Bus | red |
| 285 285-FAUX LA MONTAGNE-FELLETIN-AUBUSSON | Bus | yellow |
| 254 254-EVAUX LES BAINS-GUERET | Bus | red |
| 257 257-MONTLUCON-AUZANCES-AUBUSSON | Bus | purple |
| 258 258-MONTLUCON-AUBUSSON-FELLETIN-USSEL | Bus | gray |
| 250 250-DUN LE PALESTEL-GUERET | Bus | pink |
| 210 210-LA SOUTERRAINE-GUERET-FELLETIN | Bus | purple |
| 259 259-FELLETIN-AUBUSSON-CLERMONT FERRAND | Bus | brown |
| 281 281-AUZANCES-FONTANIERES-AHUN | Bus | teal |
| 284 284-BOUSSAC-CHAMBON-BOURGANEUF | Bus | teal |
| 255 255 BOUSSAC-GOUZON-GUERET | Bus | black |
| 252 252-ROYERE-BOURGANEUF-GUERET | Bus | gray |
| 253 253-AIGURANDE-BONNAT-GUERET | Bus | red |
| 211 211-LA SOUTERRAINE-BOURGANEUF | Bus | brown |
This feed has 391 stops.
List every stop
- Place Eglise Abribus
- Place de la Gare AB
- Gare Routière
- Pl. A. Lefaure
- Gare SNCF Quais Bus
- Face Mairie Abribus
- Bourg Face AB
- Mnts aux Morts AB
- LeMarouzeau XD951/Vc LaRue
- Mairie Abribus
- Bourg AB
- Bg Face Parking AB
- Place fontaine
- Gare Routière
- Neuvialle X D988/D27
- Coudeleix XD988/Vc
- ChezLatour Face XD988/VcChaud
- Mairie AB
- Mairie Abribus
- Neuvialle X D988/D27
- Mairie Face AB
- Place de la Bascule
- Brg Face Bascule
- ChezLatour XD988/VcChaud
- Coudeleix XD988/Vc
- Le Chiroux X RD26
- Brg Park.Monument AB
- La Clide AB
- Brg Face Abribus
- X D992 / VC Les Fougères
- Pl.Delamarre AB
- Bourg Abribus Hospice
- Brg Face Abribus Hospice
- Gare
- Gare Dvt Resto
- Bg Eglise AB
- Bg Face Stade AB
- Bg Eglise Face AB
- Bourg Abribus
- Les 4 Routes / RD942
- Eglise
- Mairie
- Brg Face Mairie
- Les 4 Routes / RD942
- Gare SNCF
- Bg Place Eglise
- Bourg Monument
- Place du Marché
- Gare S.N.C.F
- Gare
- Lycée Mme de Staël A
- Lycée P. Constans AB
- FaceLycéeP.Constans
- Place Eglise
- X D982/VC Laveix
- Les 3 Ponts Délaissé X RD982/RD31
- La Poste
- LeFranceix AB Lot.
- AB
- Le Petit Laval AB
- LeFranceix AB Délais
- X D982/VC Les Gasnes
- LePetitLaval X FaceA
- Notre Dame Face AB
- Daubech Délaissé
- Place H. Queuille AB
- FELLETIN - GARE SNCF
- Lycée Ventadour
- Notre Dame AB
- Daubech Arrêt Bus
- Bourg AB
- Létrieix AB
- Létrieix Bascule
- Séglière Aire Covoiturage AB
- Les 3 Ponts X D982/D31
- Mairie AB
- LP Roussillat
- Eglise AB
- Poste AB
- X D22/VC Neuville
- Face X D22/VC Le Mont AB
- Le Peyroux Dvt.n°9
- Le Peyroux Arrêt Bus
- X D22/VC LeMont AB
- Luchaudes Face AB
- Face Eglise AB
- Le 3 et Demi 5 Aire Covoiturage
- Létrade X D941/RteGare
- Bourg Face Gymnase
- Gare Routière
- Gare Routière
- 1erMai AB Av.Républi
- Vulcania
- Face AB Pl. Républiq
- Bourg Rond Point AB
- Bourg AB
- Bourg Gymnase
- Place République AB
- Bg Face AB
- Létrade FaceXD941/VcGare
- Face Eglise
- Bourg AB
- Bg Face AB
- Arrêt Quartier Pasteur
- LP D. Gay
- La charrette bleue
- Marque X D940/D60
- Colombourg Aire de Repos
- Bourg Dvt.Boulangerie
- RD940/Rte Masrivet
- Colombourg Aire de Repos
- Station Essence Face AB
- Bourg Eglise
- Le Breuil abribus
- Station Essence AB
- Le Breuil Arrêt Car
- Masbaraud Bg AB
- Bourg Poste AB
- Aire Covoiturage AB
- Grandsagne X Pann.Aff.Cnal
- Domaine Rochetaillade AB
- Bordas AB
- Péchadoire Dvt.n°2
- Bourg AB
- La Pimparlière XD46/Vc
- Bordas Face AB
- X RD940/RD6 Face CasseAuto
- Champ de Foire AB
- La Pimparlière XD46/Vc LeCharrioux
- Grandsagne X Bte PTT
- Domaine Rochetaillade Face AB
- Face X D940/D63
- Dvt.Casse Auto
- Mersolle XD46/D6
- Place du marché AB
- Brg Face Salle Po.
- Abribus Ecole
- Brg Salle Po. AB
- Mairie StDizier
- Masbaraud Bg Face AB
- Brg X D1/D74 AB
- Bg Magasin Proxi XD1/D74
- Face AB Place du marché
- Gare SNCF AB
- Face Mairie StDizier
- Brg Parking Ent.Nord
- Ex Gare SNCF
- X D8 / VC Bourg
- Face X D8 / VC Bourg
- Gare SNCF (arret car)
- Brg Face Pl. 2107ème
- Face Pl.Champ de Foire
- Bourg Parking AB
- Luchaudes AB
- Collège B. Bord
- AB Eglise
- Face X D22/VC Neuville
- Face AB Eglise
- Lycée Agricole Park
- Mairie Face AB
- Pl. Champ de Foire AB
- Bourg RD996
- Bg Stade AB
- La Clide Face AB
- L.M.B. AB
- Ecole AB
- Eglise
- Bg Monument
- Bg La Poste
- Bourg place
- Café de la Gare
- Bg Place Monument
- Bourg Centre AB
- Bourg Abribus
- Gare Routière
- Le Compeix Face AB
- X D940/D52 Face AB
- Face Mment aux Morts
- X D940/D52 AB
- Bridiers AB
- Aire Covoiturage AB
- La Mersolle / Dégagement D6
- X Tuilerie Pouligny
- Bel Air Abribus
- PoteauTemple XD48/D15
- X D940/D63
- Le Pont AB
- Le Pont Face AB
- Pl. Mnts aux Morts Face AB
- Péchadoire Dvt.n°12
- Croisement RD912 / RD912A1
- XD951/Vc Peuplat
- LeMarouzeau XD951/Vc
- Bourg AB Face Mairie
- Brg Bascule
- XD951/Vc LeCluzeau
- Bourg Abribus
- L.M.B
- X D992 / VC Gioux
- Villemoneix 2 Calvaires
- Bourg Eglise
- Feuyas Dvt. n°12
- Feuyas Dvt. n°10
- Parsac Bg AB
- Bourg Rte d'Aubusson AB
- Fourneaux AB
- Bg Arrêt Dvt n°16
- Bg Arrêt Dvt n°11
- La Croix Blanche Face Clinique
- La Croix Blanche Clinique Entrée Parking
- Bourg X D28 AB
- Chp de foire AB72
- Chp de foire AB71
- Pt Breuil Face AB/D982
- Gare Face AB
- La Grattade Mairie
- Fourneaux Face AB
- Pl. Champ de Foire AB
- Bourg Pl. 2107ème AB
- XD951/Vc Chateneuil
- Bridiers Face AB
- XD951/VC LaForest
- Villemoneix Face 2 Calvaires
- Bourg Face Eglise
- Pl. Champ de Foire Face AB
- Parsac Bg Prox. Mairie
- Bourg Rte d'Aubusson Face AB
- Bourg RD996
- Mairie AB
- Gare AB
- Pt Breuil AB/D982
- Bourg X D28 Face AB
- La Grattade Face Mairie
- BOURG CROISEMENT RD
- Bourg Mairie
- Le Breuil X RD8/VC
- Le Compeix Abribus
- Bel Air Face Abribus
- Bourg Devant Ets. Cottaz
- Pl. Champ de Foire AB
- Poste AB
- Bourg Parking AB
- Luchaudes Face AB
- Collège B. Bord
- Face AB Eglise
- Lycée Agricole Park
- GOUZON - Champ de foire AB
- Bg Stade AB
- Bg Face AB
- Gare Routière
- and 141 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
- Error8 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)
- Warning180 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)
- Warning167 instances
167 of 167 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)
- Warning28 instances
28 of 391 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)
- Warning15 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)
- Warning2 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)
- Warning1 instance
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
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)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Validator rule: trip_coverage_not_active_for_next7_days · 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)
- Info167 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)
- Info100 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 93% 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 93% 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 8 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 46 / 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 61 / 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/cars-regionaux-23-creuse/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.