Feed status · checked 2026-08-01
Car Jaune (La Réunion)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in La Réunion, 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 80 minutes ago; last changed 80 minutes ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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_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
4380 of 4380 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
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.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 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
- 4380 of 4380 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- feed_info.txt is missing its start/end dates (the file itself is absent)
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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
- The feed contains no fare information.
- Next action
- 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.
- 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.
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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. · 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 366 days.
- Published accessibility data
- Accessibility information is stated for 98.9% 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
- One or more realtime feeds were reachable; live-arrival coverage is not known.
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 6 kinds of issue across 4439 instances (0 error, 16 warning, 4423 informational).
Service data covers the next 366 days.
99% of stops state wheelchair accessibility (36% marked accessible, 63% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
99% of stops state accessibility (36% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (O2, S1, S4, S6, E2).
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.
4 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Poste/Mairie de Ste-Anne", "Poste/Mairie de Ste-Anne", "Poste/Mairie de Ste-Anne", 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.
Sampled 9 times outside service hours: 3 of 3 configured feeds healthy; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 468 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.
- O2 (teal)
- O3 (blue)
- S1 (orange)
- S2 (red)
- E1 (gray)
- S3 (red)
- S4 (pink)
- S5 (purple)
- S6 (white)
- T (yellow)
- E1X (gray)
- O1X (white)
- TX (yellow)
- E2 (green)
- E3 (green)
- O1 (white)
| Route | Type | Line color |
|---|---|---|
| O2 St-Denis / St-Pierre | Bus | teal |
| O3 St-Denis / St-Paul | Bus | blue |
| S1 St-Benoît / St-Pierre par le Grand Brûlé | Bus | orange |
| S2 St-Benoît / St-Pierre par les Plaines | Bus | red |
| E1 St-Denis / St-Benoît | Bus | gray |
| S3 Le Tampon / St-Pierre / St-Joseph | Bus | red |
| S4 St-Paul / St-Pierre par les Hauts | Bus | pink |
| S5 St-Pierre / Entre-Deux | Bus | purple |
| S6 Le Tampon / St-Joseph par Petite-Île | Bus | white |
| T Aéroport Roland Garros / St-Pierre par les Plages | Bus | yellow |
| E1X Express St-Denis / St-Benoît | Bus | gray |
| O1X Express St-Denis / St-Pierre | Bus | white |
| TX Express Aéroport Roland Garros / St-Pierre | Bus | yellow |
| E2 St-Denis / St-Benoît par Campus | Bus | green |
| E3 St-Denis / St-André | Bus | green |
| O1 St-Denis / St-Pierre par Route des Tamarins | Bus | white |
List every stop
- Avenue de L'Océan
- Gare de St-Philippe
- Pierrefonds
- Poste/Mairie de Ste-Anne
- Portail
- Mairie de La Possession
- Plaine des Palmistes
- Pôle Sanitaire
- Pointe au Sel
- Pointe du Tremblet
- Pyramide Fleurie
- Les Azalées
- Quatre Robinets
- R.N.7
- Ravine Ango
- Rico Carpaye
- RDT Aire du Tabac
- Parc Relais
- Barachois
- Rivière de L'Est
- Boucan Canot
- Rivière des Roches
- Ste-Rose
- Rond-Point 17ème km
- Rond-Point La Marine
- RDT Colimaçons
- RDT L'Éperon
- RDT Étang-Salé
- RDT Portail
- Bourg du 23ème
- Les Sables
- Sentier Ady
- La Saline les Bains
- Souris Chaude
- Sacré Cœur
- St-Gilles les Bains
- Souffleur d'Arbonne
- Ste-Rose Bois Blanc
- Stella
- Stade Terre Sainte
- Chemin Boussole
- Mahatma Gandhi
- Technopole
- Université du Tampon
- Village du 14ème
- Rue Vienne
- Les Vilebrequins
- Chemin Vimbaye
- Eglise Vincendo
- Vierge Parasol
- Butor
- Barachois
- St-Jacques
- Grande Chaloupe
- Félix Guyon
- Jardin de l'État
- Météo Chaudron
- Chaudron
- Butor
- Gymnase
- Technopole
- Chemin Cabris
- Cafés de Chine
- Futura
- Aéroport Roland Garros
- Lastic-La Mare
- Église Ste-Marie
- Hôtel de Ville de Ste-Marie
- Pôle d'Échanges de Duparc
- Cimetière
- Bras des Calumets
- Rond-Point La Marine
- École Quartier Français
- Hôtel de Ville de Ste-Suzanne
- Mairie de La Possession
- Mahatma Gandhi
- Pôle d'Échanges Le Port
- R.N.7
- Rico Carpaye
- Cambaie
- Gervais Barret
- Les Vilebrequins
- Sacré Cœur
- Pont de l'Étang
- Hôpital Gabriel Martin
- Piton Défaud
- Cambaie
- Case Basse Vallée
- St-Gilles les Bains
- Boucan Canot
- La Saline les Bains
- Filaos St-Gilles
- RDT L'Éperon
- Les Aigrettes
- Maison Bourbon
- Cafés de Chine
- RDT Aire du Tabac
- Souris Chaude
- Grande Ravine
- Pointe au Sel
- Gendarmerie de St-Leu
- Kélonia - Ferme Corail
- RDT Colimaçons
- Mairie de St-Leu
- Mairie du Piton
- Chemin de la Petite Plaine
- Portail
- RDT Portail
- Piton Église
- Quatre Robinets
- Deux Chemins
- Stella
- Chemin Boussole
- Chemin A. Hoarau
- Allée des Cèdres
- Chemin Cabris
- Sentier Ady
- Avirons Bois Blanc
- Chemin Maurice
- Ferblantier
- Sentier des Pêcheurs
- Gare des Avirons
- Avenue de l'Océan
- Chemin de Ceinture
- Mairie de l'Étang-Salé
- RDT Étang-Salé
- Les Sables
- Gare de St-Louis
- Allée des Cèdres
- Aérodrome
- Pierrefonds
- Chemin Vimbaye
- Gare de St-Pierre
- Hôpital de Terre Sainte
- Parc Relais
- Stade Terre Sainte
- Croisée Petite-Île
- Grande Anse
- Gare de l'Entre-Deux
- Fanjan
- Rue Vienne
- Office du Tourisme
- Marché Couvert du Tampon
- Chapelle du Tremblet
- Université du Tampon
- Village du 14ème
- GR Piton des Neiges
- Maison du Volcan
- École du 19ème
- Rond-Point 17ème km
- Bourg du 23ème
- Gare de St-Joseph
- Manapany les Bains
- Lycée Agricole
- Chaudron
- Église Vincendo
- Centre Multiservices
- Gare de St-Philippe
- Souffleur d'Arbonne
- Coulée 1986
- Pointe du Tremblet
- Chapelle du Tremblet
- Nattes
- Ravine Ango
- Poste Basse Vallée
- Cimetière
- Case Basse Vallée
- Anse des Cascades
- Ste-Rose Bois Blanc
- Vierge Parasol
- Église Piton Ste-Rose
- École Ravine Glissante
- Ste-Rose
- Rivière de l'Est
- Pyramide Fleurie
- Grotte de Lourdes
- Centre Multiservices
- Bras des Calumets
- Plaine des Palmistes
- Chemin de la Petite Plaine
- Pôle Sanitaire
- Chemin de Ceinture
- Grand Étang
- Émile Passouka
- Poste/Mairie de Ste-Anne
- Rivière des Roches
- Coulée 1986
- Giratoire des Plaines
- Coopérative de Vanille
- Mairie de Bras-Panon
- Poste Cambuston
- Les Azalées
- Barachois
- Grande Chaloupe
- Anse des Cascades
- Kélonia - Ferme Corail
- Félix Guyon
- Jardin de l'État
- Météo Chaudron
- Chaudron
- Butor
- Gymnase
- Technopole
- Cafés de Chine
- Futura
- Croisée Petite-Île
- Aéroport Roland Garros
- Lastic-La Mare
- Église Ste-Marie
- Hôtel de Ville de Ste-Marie
- Cimetière
- Rond-Point La Marine
- Rond-Point 17ème km
- École Quartier Français
- Coopérative de Vanille
- Hôtel de Ville de Ste-Suzanne
- Mairie de La Possession
- Mahatma Gandhi
- Pôle d'Échanges Le Port
- R.N.7
- Rico Carpaye
- Gervais Barret
- Les Vilebrequins
- Sacré Cœur
- Pont de l'Étang
- Hôpital Gabriel Martin
- Piton Défaud
- Cambaie
- St-Gilles les Bains
- Boucan Canot
- La Saline les Bains
- Filaos St-Gilles
- RDT L'Éperon
- Les Aigrettes
- Maison Bourbon
- RDT Aire du Tabac
- Souris Chaude
- Grande Ravine
- Pointe au Sel
- Gendarmerie de St-Leu
- Kélonia - Ferme Corail
- RDT Colimaçons
- Deux Chemins
- Mairie de St-Leu
- Mairie du Piton
- Portail
- RDT Portail
- Piton Église
- Quatre Robinets
- Deux Chemins
- and 218 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-31 | 80.6 | first check |
| 2026-08-01 | 80.6 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall grade and score held steady since 2026-07-31.
The feed file was re-published since 2026-07-31.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
12 findings, ordered by severity.
Show every finding
- Warning4380 instances
4380 of 4380 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)
- Warning11 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.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
5 of 468 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)
- Warning3 instances
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.)
Finding code: expired_calendar · 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
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
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)
- 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.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info4380 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.)
Finding code: trip_with_shape_dist_traveled_but_no_shape_distances · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info43 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).
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.)
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
This feed is close to the conformance mark. States wheelchair access on 99% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 366 days.
- Accessible Not yet
- States wheelchair access on 99% 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.
Realtime reliability
The realtime feed responded on 100.0% of 100 checks over the last 15 days, with 6s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 366 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 80 / 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 62 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 100 / 100
- 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/car-jaune-reunion/2026-08-01.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-08-01. 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.