Feed status · checked 2026-07-18
T'MM (Moselle et Madon)
Based on the feed this agency publishes
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.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
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
245 of 245 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 +25 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
Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Stop too far from shape using user distance (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.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.
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.
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.
Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. · 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 42 days.
- Published accessibility data
- Accessibility information is stated for 0% 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 5 kinds of issue across 463 instances (0 error, 462 warning, 1 informational).
Service data covers the next 42 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
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.
- B (red)
- A (teal)
- D (teal)
- C (yellow)
| Route | Type | Line color |
|---|---|---|
| B Ligne B - Pont-saint-Vincent - Flavigny-sur-Moselle | Bus | red |
| A Ligne A - Chaligny - Pierreville | Bus | teal |
| D Ligne D - Marthemont - Neuves-Maisons | Bus | teal |
| C Ligne C - CHU Brabois - Viterne | Bus | yellow |
This feed has 245 stops.
List every stop
- Gare de Bainville
- Mairie
- Le Rayeul
- La Reliquée
- Thélod - Mairie
- Pont-Saint-Vincent - Marronniers
- Chaligny - Eugene Canteneur
- Moselle Rive Gauche
- Méreville - Petit Verger
- Sexey-aux-Forges - Ecole
- Place Lucette Ditsch
- Neuves-Maisons - Point Central (Salengro)
- Sexey-aux-Forges - République
- Sub Bois de Greve
- Sub Dunant
- SUB Jardin de Joncs
- Lavoir
- Sub du Lac
- Neuves-Maisons - Siege CCMM
- Messein - Coteaux
- Messein - Marronniers
- Neuves-Maisons - Cumene
- Neuves-Maisons - Victor Hugo
- Cap Fileo
- Neuves-Maisons - Louis Martin
- Bellevue crèche
- Chaligny - Carte
- Chaligny - Val Fleurion
- Chaligny - Banvoie
- Chaligny
- Chaligny - Cimetiere
- Chaligny - Val
- Chaligny - Liberté
- Jean Jaures
- Sexey-aux-Forges - Bois du Four
- Maron - Sarazine
- Chaligny - Fond du val
- Chaligny - Bellefontaine
- Messein - Mairie
- Richardménil - Roses
- Flavigny-sur-Moselle - Boulangerie
- O.H.S.
- Viterne - Cimetiere
- Bainville-sur-Madon - Eglise
- Jacques Parisot
- Castors
- Chavigny - Eglise
- Chavigny - Forestiere
- Petite Taverne
- Maron
- Bainville-sur-Madon - Filature
- Mazot
- Neuves-Maisons - Val de fer
- Gare
- Neuves-Maisons - La Plaine
- Brabois hôpitaux
- Pont Saint-Vincent
- Neuves-Maisons - Cugnot
- Chavigny - Petite Taverne
- Chavigny - Lavoir
- Xeuilley - Gare
- Neuves-Maisons - Charmilles
- Neuves-Maisons - Muguet
- Neuves-Maisons - Haut de Pesse
- Ludres - Cinéma
- CHAVIGNY - Moulin a Vent
- VITERNE - Jet d'eau
- VITERNE - Fontaine Hadié
- Champs Celieux
- Eglise
- Cimetière
- BAINVILLE-SUR-MADON - Lilas
- Neuves-Maisons - Cap Filéo
- Pierreville - Route de Xeuilley
- Frolois - Eglise
- Frolois - Acraigne
- Chaligny
- Chavigny - Eglise
- Maizieres - Cimetiere
- Neuves-Maisons - Charmilles
- Neuves-Maisons - Point Central (Jaures)
- Pont-Saint-Vincent
- Neuves-Maisons - Chanois
- Sexey-aux-Forges - Bois du Four
- Frolois - Acraigne
- Neuves-Maisons - Point Central (Salengro)
- Chavigny - Castors
- Chaligny - Bellevue
- Bainville-sur-Madon - Mairie
- Vandoeuvre-les-Nancy - CHU Brabois
- Neuves-Maisons - La Plaine
- Neuves-Maisons - La Filoche
- Richardménil - Vert Village
- Messein - Lavoir
- Xeuilley - Place
- Messein - Bois de Greve
- Neuves-Maisons - Cumene
- Sexey-aux-Forges - Ecole
- Chavigny - Moulin a vent
- Chaligny - Val
- Chavigny - Petite Taverne
- Chaligny - Val Fleurion
- Richardménil - Roses
- Maizieres - Champs Celieux
- Frolois - Acraigne
- Richardménil - Vert Village
- Chavigny - Petite Taverne
- Chaligny - Bellefontaine
- Neuves-Maisons - Val de fer
- Maizieres - Eglise
- Richardménil - Mairie
- Méreville - Petit Verger
- Méreville - Mairie
- Flavigny-sur-Moselle - Rue d'Epinal
- Messein - Coteaux
- Thélod - Reliquée
- Messein - Mairie
- Maizieres - Champs Celieux
- Maron - Sarazine
- Neuves-Maisons - Cugnot
- Sexey-aux-Forges - Bois du Four
- Bainville-sur-Madon - Filature
- Sexey-aux-Forges - Le Portail
- Viterne - Cimetiere
- Messein - Milleries
- Flavigny-sur-Moselle - Tennis
- Neuves-Maisons - Maron
- Thélod - Mairie
- Neuves-Maisons - Louis Martin
- Neuves-Maisons - Maron
- Flavigny-sur-Moselle - Boulangerie
- Méreville - Mairie
- Bainville-sur-Madon - Filature
- Chaligny - Fond du val
- Neuves-Maisons - Victor Hugo
- Messein - Mairie
- Viterne - Jet d'eau
- Messein - Marronniers
- Flavigny-sur-Moselle - Café des Pecheurs
- Messein - Milleries
- Maron - Sarazine
- Neuves-Maisons - Muguet
- Chaligny - Carte
- Flavigny-sur-Moselle - Tennis
- Neuves-Maisons - Cap Filéo
- Chavigny - Castors
- Neuves-Maisons - Cugnot
- Maron - Place
- Pont-Saint-Vincent - Gare
- Neuves-Maisons - Val de fer
- Maizieres - Eglise
- Chavigny - Eglise
- Neuves-Maisons - Gare
- Bainville-sur-Madon - Lilas
- Xeuilley - Place
- Bainville-sur-Madon - Lilas
- Neuves-Maisons - La Plaine
- Hautonchamp
- Neuves-Maisons - Cap Filéo
- Xeuilley - Gare
- Xeuilley - Gare
- Chaligny - Bellefontaine
- Messein - Lavoir
- Flavigny-sur-Moselle - Les Deux Epis
- Sexey-aux-Forges - Le Portail
- Sexey-aux-Forges - Ecole
- Pierreville - Place de la Gare
- Bainville-sur-Madon - Gare
- Messein - Bois de Greve
- Viterne - Fontaine Hadié
- Chavigny - Forestiere
- Maizieres - Cimetiere
- Messein - Jardins des Joncs
- Richardménil - Paquis
- Méreville - Petit Verger
- Flavigny-sur-Moselle - OHS
- Pont-Saint-Vincent - Gare
- Pont-Saint-Vincent - Jean Jaures
- Maron - Place
- Frolois - Eglise
- Flavigny-sur-Moselle - Les Deux Epis
- Messein - Dunant
- Neuves-Maisons - Gare
- Messein - Marronniers
- Flavigny-sur-Moselle - Rue d'Epinal
- Messein - Jardins des Joncs
- Neuves-Maisons - Haut de Pesse
- Flavigny-sur-Moselle - OHS
- Chaligny - Cimetiere
- Bainville-sur-Madon - Eglise
- Messein - Coteaux
- Richardménil - Paquis
- Neuves-Maisons - Chanois
- Neuves-Maisons - La Filoche
- Flavigny-sur-Moselle - Boulangerie
- Neuves-Maisons - Pierre et Marie Curie
- Chavigny - Lavoir
- Messein - Dunant
- Flavigny-sur-Moselle - Café des Pecheurs
- Chavigny - Lavoir
- Chaligny - Banvoie
- Vandoeuvre-les-Nancy - CHU Brabois
- Neuves-Maisons - Pierre et Marie Curie
- Richardménil - Mairie
- Chaligny - Liberté
- Pont-Saint-Vincent - Jean Jaures
- Neuves-Maisons - Victor Hugo
- Neuves-Maisons - Point Central (Salengro)
- Chavigny - Forestiere
- Chaligny - Fond du val
- Bainville-sur-Madon - Jacques Parisot
- Sexey-aux-Forges - République
- Chavigny - Moulin a vent
- Sexey-aux-Forges - République
- Neuves-Maisons - Mazot
- Méreville - Le Rayeul
- Ludres - Cinéma
- Pont-Saint-Vincent - Marronniers
- Méreville - Le Rayeul
- Brainville-sur-Madon - Jacques Parisot
- Neuves-Maisons - Mazot
- Bainville-sur-Madon - Gare
- Pont-Saint-Vincent - Marronniers
- Ludres - Cinéma
- Chaligny - Eugene Canteneur
- Moselle Rive Gauche
- Hautonchamp
- Chaligny - Eugene Canteneur
- Flavigny-sur-Moselle - Tennis
- FLAVIGNY-SUR-MOSELLE - Café des Pecheurs
- Le Paquis
- Mairie
- Vert Village
- Neuves-Maisons - Siege CCMM
- Neuves-Maisons - Siege CCMM
- Bainville-sur-Madon - Mairie
- Sexey-aux-Forges - Le Portail
- Les 2 Epis
- Flavigny-sur-Moselle - Rue d'Epinal
- Messein - Milleries
- Maron - Place
- Neuves-Maisons - Chanois
- Gare de Neuves-Maisons
- Neuves-Maisons - Pierre et Marie Curie
- La Filoche
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
- Warning424 instances
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: 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)
- Warning245 instances
245 of 245 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)
- Warning36 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.)
Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: 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 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.)
Validator rule: 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.)
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)
- Info1 instance
Trip headsign matches intermediate stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_headsign_matches_intermediate_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: 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.)
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 0% 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 42 days.
- Accessible Not yet
- States wheelchair access on 0% 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 42 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 78 / 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 70 / 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 52 / 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/tmm-moselle-madon/2026-07-18.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-18. 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.