Feed status · checked 2026-07-24
Réseau urbain TCL
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
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
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
⏱ Often a bulk fix in your scheduling software.worth about +8 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.
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.
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. Self-check a feed before you publish.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · 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 86 days.
- Published accessibility data
- Accessibility information is stated for 93.2% of stops and 100% 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 4 kinds of issue across 11985 instances (0 error, 4850 warning, 7135 informational).
Service data covers the next 86 days.
93% of stops state wheelchair accessibility (45% marked accessible, 48% 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 (45% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
17 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 8, 10, 12, 13, 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.
39 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Av. de Louyat", "Pont St André", "L.P. St Exupéry", 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.
- AERO (teal)
- 1 (teal)
- 10 (red)
- 11 (teal)
- 12 (orange)
- 13 (green)
- 15 (pink)
- 16 (purple)
- 17 (orange)
- 18 (purple)
- 19 (pink)
- 2 (teal)
- 20 (brown)
- 23 (teal)
- 24 (orange)
- 25 (teal)
- 26 (yellow)
- 27 (teal)
- 28 (white)
- 29 (pink)
- 30 (gray)
- 31 (gray)
- 32 (yellow)
- 33 (yellow)
- 34 (yellow)
- 36 (teal)
- 37 (yellow)
- 38 (gray)
- 39 (brown)
- 4 (yellow)
- 41 (white)
- 42 (gray)
- 43 (gray)
- 45 (gray)
- 5 (blue)
- 6 (brown)
- 60 (green)
- 61 (purple)
- 8 (green)
- D1 (teal)
- D10 (red)
- D4 (yellow)
- D5 (blue)
- D8 (green)
- N1 (red)
- N2 (green)
- R2 (teal)
| Route | Type | Line color |
|---|---|---|
| AERO Navette Gare <> Aéroport via Pl. W. Churchill | Bus | teal |
| 1 PANAZOL Rte de Lyon <> Pte de Louyat | Bus | teal |
| 10 L. Serpollet <> Ch. Le Gendre | Bus | red |
| 11 COUZEIX Océalim <>LIMOGES Landouge | Bus | teal |
| 12 ISLE L. Aragon <> CONDAT sur VIENNE Versanas | Bus | orange |
| 13 FEYTIAT Plein Bois <> LE PALAIS Vert Vallon | Bus | green |
| 15 Pôle La Bastide <> Pôle St Lazare | Bus | pink |
| 16 Pôle La Bastide <> La Valoine | Bus | purple |
| 17 Pl. W. Churchill <> VERNEUIL Pennevayre | Bus | orange |
| 18 LIMOGES Ciel <> Beaune | Bus | purple |
| 19 Pl. W Churchill <> PANAZOL Manderesse | Bus | pink |
| 2 P. Curie <> Pôle La Bastide | Bus | teal |
| 20 Pl. W. Churchill <> Pôle Fougeras | Bus | brown |
| 23 ZI Nord 3 <> LE PALAIS Puy Neige | Bus | teal |
| 24 Pl. W. Churchill / Pôle St Lazare <> Fontgeaudrant | Bus | orange |
| 25 Pl. W. Churchill <> Mas Blanc | Bus | teal |
| 26 Pl. W. Churchill <> PEYRILHAC Banèche | Bus | yellow |
| 27 ISLE Les Champs <> Ch. Le Gendre | Bus | teal |
| 28 LIMOGES Ciel <> VERNEUIL Les Vaseix | Bus | white |
| 29 Pôle Fougeras <> RILHAC RANCON Bramaud | Bus | pink |
| 30 Pôle Fougeras <> RILHAC RANCON Cassepierre École | Bus | gray |
| 31 Pôle St Lazare <> EYJEAUX Bourg | Bus | gray |
| 32 Pôle St Lazare <> SOLIGNAC Bourg via LE VIGEN | Bus | yellow |
| 33 Pl. W. Churchill <> VEYRAC Les 5 Routes | Bus | yellow |
| 34 LIMOGES CIEL <> ST JUST LE MARTEL Grateloube | Bus | yellow |
| 36 Pôle St Lazare <> BOISSEUIL Z.A. La Plaine | Bus | teal |
| 37 Pôle La Bastide <> BONNAC Le Masbatin | Bus | yellow |
| 38 Pl. W. Churchill <> COUZEIX Anglard | Bus | gray |
| 39 Montjovis <> CHAPTELAT Le Theillol | Bus | brown |
| 4 Montjovis <> Pôle St Lazare | Bus | yellow |
| 41 Pl. W. Churchill <> Mas Gigou | Bus | white |
| 42 Pl. W. Churchill <> ST JUST LE MARTEL Fontaguly | Bus | gray |
| 43 Pl. W. Churchill <> FEYTIAT Mas Gauthier | Bus | gray |
| 45 Pôle La Bastide <> Le Theil | Bus | gray |
| 5 La Cornue <> J. Gagnant | Bus | blue |
| 6 Mal Juin <> Pôle La Bastide | Bus | brown |
| 60 Villagory <> PANAZOL Manderesse | Bus | green |
| 61 PANAZOL Mairie <> PANAZOL Manderesse | Bus | purple |
| 8 Mal Joffre <> Pl. W. Churchill | Bus | green |
| D1 PANAZOL Rte de Lyon <> Pte de Louyat | Bus | teal |
| D10 L. Serpollet <> Ch. Le Gendre | Bus | red |
| D4 Mal Juin <> Pôle St Lazare | Bus | yellow |
| D5 La Cornue <> Cité R. Dautry | Bus | blue |
| D8 Mal Joffre <> Puy Ponchet | Bus | green |
| N1 L. Serpollet <> Ch. Le Gendre | Bus | red |
| N2 Puy Ponchet <> Mal Joffre | Bus | green |
| R2 Ch. Le Gendre <> P. Curie | Bus | teal |
This feed has 1651 stops.
List every stop
- P. Curie
- Ronsard
- Ronsard
- Pôle La Bastide quai B
- Pôle La Bastide quai C
- Laubaudie
- Laubaudie
- Les Planchettes
- Les Planchettes
- Les Aulières
- Les Aulières
- Fontaine Caillaud
- Fontaine Caillaud
- Pinson
- Pinson
- Fauvette
- Fauvette
- Uzurat
- Uzurat
- L'Hermiterie Village
- L'Hermiterie Village
- Pôle Fougeras Quai E
- Ciel - Quai 14
- Ciel - Quai 5
- Aéroport
- Pte de Louyat
- Pte de Louyat
- Pte de Louyat
- Encombe Vineuse
- Encombe Vineuse
- Cité L. Blum
- Cité L. Blum
- Rue de Toulouse
- Rue de Toulouse
- Rue de Toulouse
- Beaupeyrat
- Beaupeyrat
- Beaupeyrat
- Tabacs
- Tabacs
- Tabacs
- G. Péri
- G. Péri
- Sts Anges
- Sts Anges
- Mairie
- Mairie
- Mairie
- Mairie
- Rectorat
- Rectorat
- Céramique
- Céramique
- Pl. Carnot
- Pl. Carnot
- Pl. Carnot
- Pl. Carnot
- Pl. Carnot
- Rue de Feytiat
- Rue de Feytiat
- Panazol Rte de Lyon
- Rte de Lyon
- Rte de Lyon
- Pl. d'Aine
- Pl. d'Aine
- Chastaingt
- Chastaingt
- Auzette
- Auzette
- Pl. D. Dussoubs
- Pl. D. Dussoubs
- Mas Loubier
- Mas Loubier
- Tuilières
- Tuilières
- Montarauds
- Montarauds
- Lycée Renoir
- Lycée Renoir
- Ch. Le Gendre
- Ch. Le Gendre
- Pôle Fougeras quai C
- Pôle Fougeras quai A
- Pôle Fougeras quai B
- Pôle Fougeras quai D
- Pôle Fougeras quai E
- Pôle Fougeras quai C
- Pôle Fougeras quai E
- Prieur
- Prieur
- E.N.S.I.L.
- E.N.S.I.L.
- Av. Foucaud
- Av. Foucaud
- Pl. Jourdan
- Pl. Jourdan
- Pl. Jourdan
- Pl. Jourdan
- Beaubreuil C.C.
- Beaubreuil C.C.
- Beaubreuil C.C.
- Beaubreuil C.C.
- A. Briand
- A. Briand
- Viollet Le Duc
- Viollet Le Duc
- Mélèzes
- Le Cluzeau
- Le Cluzeau
- Le Cluzeau
- Ester Legrand
- Ester Legrand
- Ester Limoges Technopole
- Ester Limoges Technopole
- Cité du Mas Neuf
- Cité du Mas Neuf
- Skylab
- Skylab
- Opéra
- Opéra
- Opéra
- A. Dubouché
- A. Dubouché
- R. Loewy
- R. Loewy
- H. Lagrange
- H. Lagrange
- H. Lagrange
- L'Aquapolis
- L'Aquapolis
- J. Montalat
- J. Montalat
- J. Montalat
- Dr Marcland
- Dr Marcland
- Gare des Bénédictins
- Gare des Bénédictins
- Gare des Bénédictins
- Gare des Bénédictins
- H. Dunant
- H. Dunant
- H. Dunant
- Vanteaux
- Vanteaux
- Vanteaux
- Vanteaux
- Vanteaux
- Puy Ponchet
- Puy Ponchet
- Puy Ponchet
- Puy Ponchet
- L. Delhoume
- L. Delhoume
- Av. de Naugeat
- Av. de Naugeat
- L. Serpollet
- L. Serpollet
- L. Serpollet
- Carr. Beaupeyrat
- Carr. Beaupeyrat
- Homère
- Homère
- Montplaisir
- Montplaisir
- Suffren
- Suffren
- Bosmathé
- Bosmathé
- Bosmathé
- Bosmathé
- Le Coudert
- Le Coudert
- Pl. W. Churchill quai B
- Pl. W. Churchill quai A
- Pl. W. Churchill quai D
- Pl. W. Churchill quai A
- Pl. W. Churchill quai J
- Pl. W. Churchill quai D
- Pl. W. Churchill quai H
- Pl. W. Churchill quai G
- Pl. W. Churchill quai I
- Pl. W. Churchill quai C
- Les Roses
- Les Roses
- Champollion
- Champollion
- Les Lucioles
- Les Lucioles
- Couzeix Océalim
- La Fontaine
- La Fontaine
- Chambeau
- Chambeau
- Proviseur Storck
- Proviseur Storck
- J. Macé
- J. Macé
- Gorceix
- Gorceix
- Pasteur
- Pasteur
- Les Courrières
- LIMOGES Les Courrières
- Les Courrières
- Val Pré Vert
- Val Pré Vert
- Val Pré Vert
- Cité L. Betoulle
- Cité L. Betoulle
- Cité L. Betoulle
- Cité L. Betoulle
- Le Buis
- Le Buis
- Moulin Roux
- Moulin Roux
- P. Brasseur
- P. Brasseur
- Rue de Metz
- Rue de Metz
- Moulin Blanc
- Moulin Blanc
- Les Tailles
- Les Tailles
- Couzeix Mairie
- Couzeix Mairie
- Landouge Centre
- Landouge Centre
- Landouge Centre
- Bel Font
- Bel Font
- Couzeix La Croix d'Anglard
- Couzeix La Croix d'Anglard
- Gare Montjovis
- Gare Montjovis
- Mas Bilier
- Mas Bilier
- Clos Rocher
- Clos Rocher
- Montjovis
- Montjovis
- Montjovis
- A. Dutreix
- A. Dutreix
- Eric Tabarly
- Eric Tabarly
- L. Cladel
- L. Cladel
- La Lande Fournier
- La Lande Fournier
- Le Ponteix
- and 1401 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
9 findings, ordered by severity.
Show every finding
- Warning4848 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)
- Warning113 instances
113 of 1651 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)
- 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
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)
- Info7135 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)
- 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 Awarded
This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 86 days.
- Accessible Met
- States wheelchair access on 93% of stops and 100% of trips.
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 86 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 83 / 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 76 / 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-82348/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.