Feed status · checked 2026-09-01
Réseau urbain TAC
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Grand-Est, 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.
Measured 4 of 4 score categories from the official feed URL on file.
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 3 snapshots.
- The feed was downloaded from the official feed URL on file.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to 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.
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
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
382 of 896 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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +11 points in its category
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.Likely your export tool
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 streets or point riders to the wrong corner.
⏱ Usually an export-tool fix, not hand editing.worth about +8 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
- 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
- Feed evidence
- 382 of 896 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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 stops sit far from the route line, going by the feed's own distance values.
- Next action
- Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.
- 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.
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.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · 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.
Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. · 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 306 days.
- Published accessibility data
- Accessibility information is stated for 57.4% 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
- Live-arrival data covered 90.5% of scheduled trips in the sampled window.
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 2845 instances (0 error, 2511 warning, 334 informational).
Service data covers the next 306 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
14 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 11, 13, 14, 17, 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.
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 3 times: 1 of 1 configured feed healthy; 90.5% of scheduled trips had live predictions; predictions ran a median of 0s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 896 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.
- 1 (teal)
- 10 (purple)
- 11 (teal)
- 12 (teal)
- 13 (gray)
- 14 (gray)
- 15 (black)
- 16 (brown)
- 17 (pink)
- 18 (teal)
- 2 (red)
- 2C (black)
- 3 (pink)
- 4 (gray)
- 5 (green)
- 6 (blue)
- 7 (yellow)
- 8 (gray)
- 9 (orange)
- A (red)
- A1 (black)
- A2 (yellow)
- B (green)
- C (teal)
- M (pink)
- N (yellow)
| Route | Type | Line color |
|---|---|---|
| 1 Ligne 1 | Bus | teal |
| 10 Ligne 10 | Bus | purple |
| 11 Ligne 11 | Bus | teal |
| 12 Ligne 12 | Bus | teal |
| 13 Ligne 13 | Bus | gray |
| 14 Ligne 14 | Bus | gray |
| 15 Ligne 15 | Bus | black |
| 16 Ligne 16 | Bus | brown |
| 17 Ligne 17 | Bus | pink |
| 18 Ligne 18 | Bus | teal |
| 2 Ligne 2 | Bus | red |
| 2C Ligne 2C | Bus | black |
| 3 Ligne 3 | Bus | pink |
| 4 Ligne 4 | Bus | gray |
| 5 Ligne 5 | Bus | green |
| 6 Ligne 6 | Bus | blue |
| 7 Ligne 7 | Bus | yellow |
| 8 Ligne 8 | Bus | gray |
| 9 Ligne 9 | Bus | orange |
| A Ligne A | Bus | red |
| A1 Ligne A1 | Bus | black |
| A2 Ligne A2 | Bus | yellow |
| B Ligne B | Bus | green |
| C Ligne C | Bus | teal |
| M Ligne M | Bus | pink |
| N Ligne N | Bus | yellow |
List every stop
- La Brouette
- Bazeilles Lycée
- PLACE
- Cimetiere de Torcy
- Dugauguez
- Cité des Forges
- Frenois Ecole
- Frenois Lavoir
- Gernelle
- Maréchal Foch
- François Sommer
- Illy
- Rumel
- Beauregard
- Elaire Mairie
- Dom-le-Mesnil Mairie
- Rue du pont
- Avenue de Toulon
- Général de Gaulle
- Le Gaulier
- Hôpital
- Place de la Machere
- Fleuranges
- Eglise Saint-Vincent
- Place Voltaire
- Saint-Menges
- La Fosse
- Rue Rogissart
- Place Mitterrand
- Rue Zola
- Jacques Wentzel
- Mairie de Floing
- Issancourt
- Saint-Albert
- Chemin de Boutry
- Chene Brisé
- Ecole Bellevue
- Rue de Metz
- Mohon Place
- Jardin Botanique
- Belval
- Derniere Cartouche
- Pont-a-Bar
- College Le Lac
- Flize
- Ecossais
- Faraday
- J.B. Lefort
- Fond de Givonne
- Pont Maugis
- Noyers
- La Hachette
- Ballastieres
- Mac Mahon
- Navaux
- Flamanville
- Auberge de Jeunesse
- Capucines
- Centre commercial La Croisette
- Chaulette
- Coispine
- CRS 23
- Foyer des Jeunes
- George Sand
- Grande Terre
- Hôpital Manchester
- Léon Bourgeois
- Métropolis
- Monument
- Parc Animalier
- Parc Expositions
- Pepiniere d'entreprises
- Place Marceau
- Scamaroni
- Sévigné
- Damouzy
- Les gobiettes
- Chemin du Loup
- Fleigneux
- Flize - Rue du Port
- Givonne Ecole
- La Grandville Mairie
- Haudrecy
- Houldizy
- Waridon
- Rosiers
- Poterie
- Lycée Agricole
- Saint-Menges Croix Blanche
- Avenue Stackler
- Parc a Fourrage
- Turenne - Goulden
- Thelonne Centre
- Thelonne Grande Rue
- Tournes Mairie
- Europe
- Louise Michel
- Villers Mairie
- Villers Stade
- Jacquemard
- Granges Pavant
- Les Granges Bertholet
- Lucien Pierquin
- Warcq
- Arreux
- 12eme RC
- Briand
- Place Nassau
- L'Entrevue
- Bellevue du Nord
- Bois Mottin
- Château d'eau
- CHARROUE
- Z.I. n°3
- Z.I. n°1
- Z.I. n°2
- Montjoly
- Abattoir
- 3 Obus
- Devant Nouzon
- Monge
- Albert Poulain
- Nevers
- Pont des Deux Villes
- Place d'Arches
- Carnot
- Val de Vence
- J.P. Sartre
- Sutiaux
- P. Neruda
- Mogador
- Village
- Beauséjour
- Gambetta
- Les Clairons
- Lumes Mairie
- La Joie de vivre
- Lumes Rult
- Mazy
- Villers Village
- Centre commercial Villers
- Camille Didier
- Z.I. Mohon
- Centre de Réadaptation
- Romery
- Californie
- Lavoir
- Ban de Mézieres
- Haut du Theux
- Les Abeilles
- Pont de Venise
- Cité du Bossu
- Froide Fontaine
- Neufmanil Centre
- Neufmanil HLM
- Gespunsart
- La Houillere
- Luxembourg
- César Franck
- Moulinet
- Léon Dehuz
- Madeleine Sylvain
- R. Bruxelle
- Place Verte
- Saint-Julien
- ARRET MACE
- Cimetiere
- Moulin a Vent
- Libreville
- Mignolet
- De Gaulle
- Mellier
- Favée
- Campagne
- Vieille Meuse
- Jacques Félix
- Six Chemins
- Ecluse
- Pierrard
- Bonaventure
- Granges Moulues
- Fieullen
- Gailly
- Poste
- Les Sources
- Les Hautes Voies
- Les Campanules
- Emeraude
- Bruneau
- Chalandry
- Place René ORSAT
- Les Ayvelles Mairie
- Le Bourg
- Turenne
- Clinique
- Marronniers
- Dauphine
- La Havetiere
- Meillier Fontaine
- Jeanne d'Arc
- Trois Chemins
- Croix du Moulin
- Saint-Eloi
- Les Vieux Prés
- Biscuiterie
- Grand Rulut
- Piscine
- LEP Charles de Gonzague
- Les Fauvettes
- P. Richier
- J. Fuzelier
- Pôle de Santé
- Patte D'Oie
- Presbytere
- Aiglemont Mairie
- Pasteur
- Rimbaud
- Jean Moulin
- Le Château
- Clos Paul
- Hôpital Bélair
- La Vilette
- Pâquis
- Mont Olympe
- Alhambra
- Aragon
- Artistic
- Auriol
- Avenue De Gaulle
- Boutet
- Centre Aquatique
- Citadelle
- Clouet
- Couronne Champagne
- Etion Village
- Ferroul
- Horizon
- Hôtel de Ville
- La Culbute
- La Warenne
- ARRET LAMARTINE
- Emile Nivelet
- Les Bouleaux
- Mésanges
- Muguet
- Place Dunant
- Point Central
- Renaudin
- Rouget de Lisle
- St-Louis
- and 646 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
- Warning2093 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 streets or point riders to the wrong corner.
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)
- Warning382 instances
382 of 896 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)
- Warning331 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)
- Warning43 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)
- Warning33 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)
- Warning7 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)
- Warning2 instances
2 of 21 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule times labeled as live. Caltrans asks that every trip you run shows up in TripUpdates.
Fix: Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out. (A vendor data-mapping question.)
Finding code: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning1 instance
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · 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 to link entrances, platforms, and elevators. Give each one a level. (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)
- Warning1 instance
Realtime data was up to 62 seconds old when sampled.
Stale positions and predictions are worse than none: riders watch a bus that already left.
Fix: Ask your AVL vendor to send updates at least every 20 seconds. That is the Caltrans guideline. (A vendor configuration question.)
Finding code: scorecard_rt_stale
- Info334 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
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
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 57% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 306 days.
- Accessible Not yet
- States wheelchair access on 57% of stops and 100% 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 4 checks over the last 1 day, with 44s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Live predictions vs schedule
Arrival predictions ran right on the schedule, and stayed within 240s nine times in ten. They were on time (about a minute early to five late) 92.4% of the time.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
Clears the Google and Apple Maps four-week coverage bar. This feed has 306 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 49 / 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 100 / 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 67 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 96 / 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/fr-pan-80451/2026-09-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-09-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.