Feed status · checked 2026-08-01
STAS (Saint-Étienne Métropole)
Based on the feed this agency publishes
Service mode Tram + Bus + Trolleybus
unchanged since 2026-07-31
Catalogued in Auvergne-Rhône-Alpes, 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 3 hours ago; last changed 13 hours ago.
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 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +24 points in its category
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 transit vehicles jumping backwards or mis-order stops.
⏱ Usually an export-tool fix, not hand editing.worth about +24 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
23501 of 23501 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.
⏱ A default or per-trip field in your export.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
- Trip distance exceeds shape distance (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- Some trips have stop times whose distances along the route go backwards.
- Next action
- Re-generate shape distances in your export; flag to your vendor if it persists.
- 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
- 23501 of 23501 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
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 'trip_distance_exceeds_shape_distance' 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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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.
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 76 days.
- Published accessibility data
- Accessibility information is stated for 56.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 12 kinds of issue across 20804 instances (628 error, 19454 warning, 722 informational).
Service data covers the next 76 days.
57% of stops state wheelchair accessibility (57% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
57% of stops state accessibility (57% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
11 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (M1, M2, M5, M7, T1, 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.
52 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("AV. ROCHETAILLEE", "AV. ROCHETAILLEE", "ST ROCH", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
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.
This feed has 2270 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.
- M1 (teal)
- M2 (purple)
- M3 (orange)
- M4 (pink)
- M5 (green)
- M6 (brown)
- M7 (brown)
- 8 (pink)
- M9 (teal)
- 10 (orange)
- 101 (brown)
- 102 (gray)
- 103 (green)
- 104 (teal)
- 105 (yellow)
- 106 (brown)
- 107 (green)
- 108 (green)
- 109 (green)
- 12 (pink)
- 13 (gray)
- 14 (gray)
- 15 (brown)
- 16 (teal)
- 17 (orange)
- N1 (white)
- N2 (pink)
- 20 (brown)
- 21 (brown)
- 22 (teal)
- 23 (orange)
- 24 (orange)
- 25 (brown)
- 27 (pink)
- 28 (pink)
- 29 (teal)
- 30 (gray)
- 31 (teal)
- 32 (pink)
- 33 (orange)
- 34 (yellow)
- 36 (green)
- 37 (teal)
- 39 (pink)
- 40 (red)
- 41 (gray)
- 42 (yellow)
- 43 (yellow)
- 44 (pink)
- 45 (gray)
- 46 (yellow)
- 47 (pink)
- 48 (teal)
- 49 (yellow)
- T1 (red)
- T2 (teal)
- T3 (green)
- 57 (green)
- T1B (red)
- T3B (green)
- S3 (orange)
- S6 (brown)
- S7 (brown)
- S9 (teal)
- S1 (teal)
- 68 (gray)
- 69 (pink)
- 70 (red)
- 71 (gray)
- 72 (gray)
- 73 (gray)
- 74 (red)
- 76 (orange)
- 77 (yellow)
- 78 (pink)
- 79 (yellow)
- 80 (pink)
- 81 (white)
- 82 (yellow)
- 83 (pink)
- 84 (gray)
- 85 (teal)
- TX3 (gray)
- TX4 (gray)
- C1 (brown)
| Route | Type | Line color |
|---|---|---|
| M1 BELLEVUE <> EGLISE CORBUSIER | Bus | teal |
| M2 GARE FIRMINY <> METARE | Bus | purple |
| M3 COTONNE <> TERRENOIRE | Trolleybus | orange |
| M4 BELLEVUE <> CHATEAUCREUX GARE | Bus | pink |
| M5 SQUARE VIOLETTE <> PLACE CHIPIER | Bus | green |
| M6 JEAN MOULIN <> IUT/FACULTE DES SCIENCES | Bus | brown |
| M7 BELLEVUE <> MICHON | Trolleybus | brown |
| 8 TERRASSE <> SAINT-SAËNS | Bus | pink |
| M9 PLACE CARNOT <> MONTREYNAUD | Bus | teal |
| 10 PLACE JEAN JAURES <> BOURG | Bus | orange |
| 101 MAISON D'ARRET <> RENE CASSIN | Bus | brown |
| 102 PLACE DU MOULIN <> LUZERNOD | Bus | gray |
| 103 GARE ROUTIERE <> LA FLECHETTE | Bus | green |
| 104 GARE ROUTIERE <> LES VIGNES | Bus | teal |
| 105 GARE ROUTIERE RDG <> MAIRIE CHATEAUNEUF | Bus | yellow |
| 106 GARE ROUTIERE RDG <> LE BAJARD | Bus | brown |
| 107 CIMETIERE <> CONDAMINE | Bus | green |
| 108 CIMETIERE <> QUERET | Bus | green |
| 109 CIMETIERE <> BOURG ST VICTOR | Bus | green |
| 12 BEL AIR <> VILLEBOEUF-LE-HAUT | Bus | pink |
| 13 LE CHASSEUR <> PORTAIL ROUGE | Bus | gray |
| 14 CHATEAUCREUX GARE <> GRAND QUARTIER | Bus | gray |
| 15 SQUARE VIOLETTE <> METROTECH | Bus | brown |
| 16 LYCEE SIMONE WEIL <> MONTPLAISIR | Bus | teal |
| 17 LA BERTRANDIERE <> MAIRIE | Bus | orange |
| N1 NOCTAMBUS : ZENITH / RUE DES ACIERIES <> TERRASSE | Bus | white |
| N2 NOCTAMBUS : HOTEL DE VILLE <> MARANDINIERE | Bus | pink |
| 20 HAUTS DE TERRENOIRE <> PERROTIERE | Bus | brown |
| 21 CRET DE MONTAUD <> PLACE DES PERES | Bus | brown |
| 22 BELLEVUE <> COTONNE | Bus | teal |
| 23 BELLEVUE <> LE BERNAY | Bus | orange |
| 24 DORIAN / HOTEL DE VILLE <> PETITES SOEURS | Bus | orange |
| 25 TERRASSE <> GARE | Bus | brown |
| 27 TERRASSE <> COLLEGE PARKING NORD | Bus | pink |
| 28 PACOTIERE <> PUITS LUCY | Bus | pink |
| 29 PLACE DU MOULIN <> CHATEAUCREUX GARE | Bus | teal |
| 30 LA MICHALIERE <> LE PERTUISET | Bus | gray |
| 31 GARE FIRMINY <> LES 3 ROUTES | Bus | teal |
| 32 GARE <> COLLEGE LA RIVE | Bus | pink |
| 33 CHAZEAU <> VERTE COLLINE | Bus | orange |
| 34 GARE <> MAIRIE | Bus | yellow |
| 36 JEAN JAURES <> BASE NAUTIQUE | Bus | green |
| 37 HOPITAL NORD <> GARE ANDREZIEUX | Bus | teal |
| 39 NAUTIFORM <> COLLEGE J. ROMAINS | Bus | pink |
| 40 CENTRE CIAL MALADIERE <> PISCINE COUDERC | Bus | red |
| 41 PLACE DU MOULIN <> CRET OEILLET HAUT | Bus | gray |
| 42 PLACE DU MOULIN <> OLLAGNIERE/LE POYET | Bus | yellow |
| 43 CRET OEILLET <> CHAVANNE BOURG | Bus | yellow |
| 44 PLACE DU MOULIN <> LA BACHASSE | Bus | pink |
| 45 PLACE DU MOULIN <> SAINT-MARTIN-EN-COAILLEUX | Bus | gray |
| 46 GARE ROUTIERE <> MAIRIE/LE MAS | Bus | yellow |
| 47 LE PLANTIER <> LA CULA | Bus | pink |
| 48 MAIRIE <> CHARLES DE GAULLE | Bus | teal |
| 49 CHARLES DE GAULLE <> MAISON FORTE | Bus | yellow |
| T1 HOPITAL NORD <> SOLAURE | Tram / light rail | red |
| T2 CITÉ DU DESIGN <> CHATEAUCREUX GARE | Tram / light rail | teal |
| T3 HOP. NORD/TERRASSE <> BELLEVUE | Tram / light rail | green |
| 57 LES MARIANNES <> LA MADELEINE | Bus | green |
| T1B BELLEVUE <> SOLAURE | Bus | red |
| T3B HOPITAL NORD <> TERRASSE | Bus | green |
| S3 COTONNE <> TERRENOIRE | Trolleybus | orange |
| S6 JEAN MOULIN <> MARANDINIERE | Bus | brown |
| S7 MICHON <> DORIAN/HOTEL DE VILLE | Trolleybus | brown |
| S9 JEAN JAURÈS <> MONTREYNAUD | Bus | teal |
| S1 BELLEVUE <> EGLISE CORBUSIER | Bus | teal |
| 68 LES 3 ROUTES <> BD HAUT FOREZ VIA ROZIER-ST NIZIER | Bus | gray |
| 69 LES 3 ROUTES <> BD HAUT FOREZ VIA ABOEN | Bus | pink |
| 70 CRET DE MARS <> JULES VALLES | Bus | red |
| 71 PONT NANTIN <> PORTAIL ROUGE | Bus | gray |
| 72 GREEN PARK <> COLLEGE A. BRIAND | Bus | gray |
| 73 ST-GENEST-LERPT <> COLLEGE GRUNER | Bus | gray |
| 74 COLLEGE LA RIVE <> LAUMIERE | Bus | red |
| 76 COLLEGE JULES ROMAINS <> BUISSONNET | Bus | orange |
| 77 BONZIEUX <> COIN CHARMILLES | Bus | yellow |
| 78 CLOS MARQUET/STELYTEC <> GARE/SAINTE-MARIE | Bus | pink |
| 79 CRET OEILLET <> LA FAYETTE | Bus | yellow |
| 80 BELLEVUE <> ROCHETAILLEE / LA BARBANCHE | Bus | pink |
| 81 BOURG <> GARE | Bus | white |
| 82 LE BESSY 2 <> COLLEGE C. EXBRAYAT | Bus | yellow |
| 83 CHATEAUCREUX GARE <> NELSON MANDELA | Bus | pink |
| 84 COLL.P.M. CURIE <> MAIRIE | Bus | gray |
| 85 COLLEGE P. M. CURIE <> BOURG | Bus | teal |
| TX3 THEY <> PLACE DU DORLAY | Bus | gray |
| TX4 MERLEY <> MAIRIE | Bus | gray |
| C1 TERRASSE <> PLACE DE GAULLE | Bus | brown |
List every stop
- ROZIER
- EGLISE CHAZEAU
- EGLISE CHAZEAU
- IMPASSE MALVAL
- IMPASSE MALVAL
- RUE DE L'ABBAYE
- CHAZEAU
- MONTESSUS
- SUPERMARCHE
- LA MARTINIERE
- LA MARTINIERE
- SUPERMARCHE
- LE CORBUSIER
- LES NOYERS
- LES NOYERS
- LES HAUTS NOYERS
- LES HAUTS NOYERS
- RUE DES NOYERS
- RUE DES NOYERS
- CASERNE POMPIERS
- CASERNE POMPIERS
- VERTE COLLINE
- LES NOISETTES
- LES NOISETTES
- CHEMIN DES PRES
- LES ROULATTES
- RUE DE ST-JUST
- LES ROULATTES
- PABLO NERUDA
- VERTE COLLINE
- RUE DE ST-JUST
- CHEMIN DES PRES
- PABLO NERUDA
- GARNAUDET
- GARNAUDET
- MARTINANGE
- MARTINANGE
- ZONE COMMERCIALE
- Z.A. PERIVAURE
- Z.A. PERIVAURE
- ZONE COMMERCIALE
- LOGIS NEUF
- LOGIS NEUF
- PL. CORNICHE
- PL. CORNICHE
- BD CORNICHE
- BD CORNICHE
- LES QUATRE VENTS
- LES QUATRE VENTS
- FAYOL
- FAYOL
- PARPOULIN
- PARPOULIN
- TALARAND
- TALARAND
- GABELON
- GABELON
- ROCHEGUT
- ROCHEGUT
- LES PERROTS
- LES PERROTS
- MAIRIE FRAISSES
- MAIRIE FRAISSES
- LA PERIVAURE
- LA PERIVAURE
- MONTESSUS BAS
- MONTESSUS BAS
- PONT-CHANEY
- PONT-CHANEY
- LYCEE A.CAMUS
- RUE DE LA LOIRE
- HOPITAL FIRMINY
- HOPITAL FIRMINY
- RUE DE LA LOIRE
- LA PATE
- LA PATE
- EGLISE CORBUSIER
- AMICALE FAYOL
- AMICALE FAYOL
- C. C. LES PRAIRIES
- C. C. LES PRAIRIES
- GAFFARD
- GAFFARD
- STADE GAFFARD
- STADE GAFFARD
- AVENUE DU PARC
- AVENUE DU PARC
- MICHALIERE
- CHARME
- CHARME
- LA POMASSE
- LA POMASSE
- EMILIEUX
- EMILIEUX
- LA SOULIERE
- LA SOULIERE
- PLACETTE GIRARDS
- PLACETTE GIRARDS
- LES GIRARDS
- LES GIRARDS
- LE SAGNON
- LE SAGNON
- PLACE JEAN RIST
- PLACE JEAN RIST
- LYCEE A.CAMUS
- PONT DU SAUZE
- PONT DU SAUZE
- CHATEAU LATOUR
- CHATEAU LATOUR
- RUE VERDIE
- PLACE DU BREUIL
- LES HALLES
- LES HALLES
- PLACE DU BREUIL
- INDUSTRIE
- PLACE DU BREUIL
- GARE FIRMINY
- GARE FIRMINY
- PLACE FERRER
- PLACE FERRER
- LE MAS
- A. BOISSIER
- A. BOISSIER
- BD D'AUVERGNE
- BD D'AUVERGNE
- LE BOUCHET
- LE BOUCHET
- LA ROMIERE
- LA ROMIERE
- PYRENEES
- PYRENEES
- TOURNEBISE
- ESPACE CAMUS
- ESPACE CAMUS
- COUBERTIN
- COUBERTIN
- LES ESSERTINES
- LES ESSERTINES
- BARBANCHE VILL
- BARBANCHE VILL
- BARBANCHE PLAT.
- BARBANCHE PLAT.
- MIZERIECQ
- MIZERIECQ
- CHATEAU LE BOIS
- CHATEAU LE BOIS
- SAINT-PAUL
- SAINT-PAUL
- NEUF PONTS
- NEUF PONTS
- MAIRIE ST-PAUL
- CROIX DU POIRIER
- CROIX DU POIRIER
- CASE AU BOIS
- CASE AU BOIS
- LA RIVE
- LA RIVE
- GARE FRAISSES
- GARE FRAISSES
- PASTEUR
- PASTEUR
- PARC HOLTZER
- PARC HOLTZER
- LE VIGNERON
- LE VIGNERON
- COMBE BLANCHE
- COMBE BLANCHE
- LE SABLAT
- LE SABLAT
- LE MAS
- LE MAS
- LE MAS
- L'ECHAPRE
- L'ECHAPRE
- RUE D. ABATTOIRS
- RUE D. ABATTOIRS
- LA MALAFOLIE
- LA MALAFOLIE
- LE BEC
- LE BEC
- LES PLATANES
- LES PLATANES
- LES MOLIERES
- CROIX BLEUE
- CROIX BLEUE
- GARE CHAMBON
- GARE CHAMBON
- LYCEE A.TESTUD
- LES MOLIERES
- CHATEAU D'EAU
- CHATEAU D'EAU
- POLE DE SERVICES
- POLE DE SERVICES
- LA COTILLE
- LA COTILLE
- MAIRIE CHAMBON 2
- EGLISE CHAMBON 2
- CIMETIERE
- LAGRANGE
- LAGRANGE
- STADE POURATTE
- STADE POURATTE
- CIMETIERE
- NIONNIERE
- NIONNIERE
- EAUX VIVES
- EAUX VIVES
- GRENIECQ
- GRENIECQ
- POMMERLET
- POMMERLET
- CHAIZENEUVE
- CHAIZENEUVE
- CROIX STE-AGATHE
- CROIX STE-AGATHE
- LE POCHET
- MAIRIE D'UNIEUX
- COLL. LA RIVE
- MAIRIE D'UNIEUX
- COLL. LA RIVE
- COLL. LA RIVE
- PONT D'UNIEUX
- PONT D'UNIEUX
- COLL. LA RIVE
- PL. DE LA BARGE
- PL. DE LA BARGE
- MAIRIE CHAMBON 1
- EGLISE CHAMBON 1
- EGLISE CHAMBON 1
- PISCINE ONDAINE
- PISCINE ONDAINE
- COLL. FOURNEYRON
- COLL. FOURNEYRON
- COLL. FOURNEYRON
- TRABLAINE
- TRABLAINE
- PONTCHARRA
- GYMNASE CHAMBON
- GYMNASE CHAMBON
- COTATAY
- PONTCHARRA
- COTATAY
- MONTRAMBERT
- MONTRAMBERT
- MELINE
- MELINE
- HAUTS ONDAINE
- HAUTS ONDAINE
- DRAMOISON BAS
- DRAMOISON BAS
- and 2020 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 32.8 | first check |
| 2026-07-30 | 32.8 | no change |
| 2026-07-31 | 32.8 | no change |
| 2026-08-01 | 32.8 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
18 findings, ordered by severity.
Show every finding
- Error498 instances
Trip distance exceeds shape distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error130 instances
Some trips have stop times whose distances along the route go backwards.
Apps can show transit vehicles 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.)
Finding code: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning23501 instances
23501 of 23501 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle 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)
- Warning13249 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.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5969 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.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning981 instances
981 of 2270 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)
- Warning201 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 path or point riders to the wrong boarding location.
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.)
Finding code: 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)
- Warning16 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.
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.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning13 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.)
Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some scheduled trips move faster between stops than a transit vehicle can.
Usually a typo'd stop time; riders get arrival times no transit vehicle 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)
- Warning2 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.)
Finding code: 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.)
Finding code: missing_recommended_file · Read the fix guide · 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.)
Finding code: 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.)
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)
- Info2249 instances
About 2249 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.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info722 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the transit vehicle ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · 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. 2 validator errors to resolve. States wheelchair access on 57% 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 76 days.
- Accessible Not yet
- States wheelchair access on 57% 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 75 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 628 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 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 37 / 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/stas-saint-etienne/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.