Feed status · checked 2026-09-07
Réseau urbain Cmonbus
Based on the official feed source on file
Service mode Bus
unchanged since 2026-09-06
Catalogued in Provence-Alpes-Côte-d’Azur, 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 2 hours ago; last changed 2 hours ago.
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 9 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
Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Block trips with overlapping stop times (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 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
190 of 190 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 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
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
- Block trips with overlapping stop times (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'block_trips_with_overlapping_stop_times' 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
- 190 of 190 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
- feed_info.txt is missing its start/end dates (the file itself is absent)
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
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 'block_trips_with_overlapping_stop_times' 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.
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. See this feed's finding-clearance log.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
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 358 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 58.3% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- Realtime information
- One or more realtime feeds were reachable; live-arrival coverage is not known.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 11 kinds of issue across 9394 instances (16 error, 8768 warning, 610 informational).
Service data covers the next 358 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.
3 accessibility depth signals
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (4, 1).
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.
3 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Av. du Pont", "Av. du Pont", "Av. du Pont").
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Sampled 9 times outside service hours: 3 of 3 configured feeds healthy; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 190 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.
- 4 (purple)
- NCV2 (yellow)
- NCV1 (teal)
- B (green)
- 1 (teal)
- 3 (orange)
- C (teal)
- 2 (brown)
- CMNA (black)
- A (red)
- D (yellow)
- E (gray)
| Route | Type | Line color |
|---|---|---|
| 4 Scolaire Ligne 4 | Bus | purple |
| NCV2 Navette Centre Ville Grenouillet OT | Bus | yellow |
| NCV1 Navette Centre-ville Grenouillet Hôpital | Bus | teal |
| B Ligne B | Bus | green |
| 1 Scolaire Ligne 1 | Bus | teal |
| 3 Scolaire Ligne 3 | Bus | orange |
| C Ligne C | Bus | teal |
| 2 Scolaire Ligne 2 | Bus | brown |
| CMNA Vigneres <> Cavaillon <> Robion | Bus | black |
| A Ligne A | Bus | red |
| D Ligne D | Bus | yellow |
| E Ligne E | Bus | gray |
List every stop
- Albin Durand
- Albin Durand
- Albin Durand
- Clovis Hugues
- Craponne
- Craponne
- Craponne
- Follereau
- Follereau
- Follereau
- Hôpital
- Jacques Brel
- Agnely
- Agnely
- Office de Tourisme
- Office de Tourisme
- Germain Chauvin
- Av. du Pont
- Sadi Carnot
- Bel air
- Dunant
- Pierre Fabre
- Albizzia
- Les Vignères
- Rolland
- Gares
- Verdun
- Pôle Bio
- M.I.N.
- Avenue De Cheval Blanc
- Centre De Loisirs
- Hippodrome
- Ecole Des Ratacans
- Paul Cézanne
- Ccas
- Les Banquets
- Route de Pertuis
- Mediathèque
- Paul Gauthier
- Cimetière
- Bellevue
- Le Puits Des Gavottes
- Jean Bastide
- La Clède
- Prosper Mérimée
- Zone d'activités
- Route de l'Isle
- Ravaou
- Route de Robion
- Léon Colombier
- Les Sapins
- Les Cabedans
- Libération
- Docteur Brun
- Route des Courses
- Pablo Picasso
- Square Des Ratacans
- Auguste Bertrand
- Kennedy
- Office de Tourisme
- LMV
- Chemin de la Crau
- Victor Basch
- Saint Baldou
- Elsa Triolet
- Maternelle Camille Claudel
- Georges Ferrières
- Clémenceau
- Rolland
- Bel air
- Albizzia
- Germain Chauvin
- Verdun
- Ccas
- Sadi Carnot
- Ccas
- Albizzia
- Dunant
- Office de Tourisme
- Germain Chauvin
- Pôle Bio
- Rolland
- Victor Basch
- Verdun
- Mediathèque
- Dauphin
- Bellevue
- Le Puits Des Gavottes
- La Clède
- Les Cabedans
- Mediathèque
- Rond Point du Melon
- Collège Gauthier
- Les Vergers
- M.I.N.
- Prosper Mérimée
- Route de l'Isle
- Les Cabedans
- Paul Cézanne
- Hippodrome
- Les Vigneres
- La Canaù
- Pierre Fabre
- Léon Colombier
- Cimetière
- Route des Courses
- Les Vignères
- Docteur Brun
- Kennedy
- Elie Bonnebeau
- Vidauque
- Route de Robion
- Square Des Ratacans
- Centre De Loisirs
- Centre De Loisirs
- Bellevue
- Jean Bastide
- Pablo Picasso
- Zone d'activités
- M.I.N.
- Clinique Saint-Roch
- Les Sapins
- Léon Colombier
- Route de Robion
- Avenue De Cheval Blanc
- Paul Gauthier
- Av. du Pont
- Jean Bastide
- Les Banquets
- Auguste Bertrand
- Avenue De Cheval Blanc
- Libération
- Le Puits Des Gavottes
- Cimetière
- Route des Courses
- Taillades
- Les Sapins
- Paul Gauthier
- Gares
- Hippodrome
- Auguste Bertrand
- Kennedy
- Victor Hugo
- Zone d'activités
- Rosa Parks
- Route de Pertuis
- Ecole Des Ratacans
- Ravaou
- Route de l'Isle
- La Clède
- Paul Cézanne
- Grenouillet
- Ravaou
- Ecole Des Ratacans
- Route de Pertuis
- Office de Tourisme
- Libération
- Sadi Carnot
- Docteur Brun
- Gares
- Les Banquets
- Dumas
- Prosper Mérimée
- Square Des Ratacans
- Parcs du Luberon
- Pablo Picasso
- Agnely
- Av. du Pont
- Dunant
- Pôle Bio
- Pierre Fabre
- Bel air
- Robion
- Clémenceau
- Victor Basch
- Elsa Triolet
- Saint Baldou
- Saint Baldou
- Coulon
- Clémenceau
- LMV
- Georges Ferrières
- Chemin de la Crau
- Elsa Triolet
- Chemin de la Crau
- Maternelle Camille Claudel
- LMV
- Maternelle Camille Claudel
- Saint Jacques
- Georges Ferrières
Over time
Overall score across the last 4 checks — unchanged since 2026-09-06.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 67.2 | first check |
| 2026-08-07 | 66.9 | down 0.3 |
| 2026-09-06 | 63.7 | down 3.2 |
| 2026-09-07 | 63.7 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall grade and score held steady since 2026-09-06.
The feed file was re-published since 2026-09-06.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
What changed over time
On 2026-08-06 this feed started at grade D. On 2026-09-06 the check no longer reported: some service calendars in the feed have already ended; 17 of 635 trips lack rider-facing destination or direction text. As of 2026-09-07 it holds grade D.
A plain-language history of this feed, newest first.
- 2026-09-06 Score fell 3 points, correctness fell 15 points.
Everything we checked
17 findings, ordered by severity.
Show every finding
- Error16 instances
Block trips with overlapping stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: block_trips_with_overlapping_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5187 instances
Some rows in stop_times.txt leave the timepoint column blank.
That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.
Fix: Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1. (Usually one export setting.)
Finding code: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3530 instances
Some internal IDs use characters outside the basic text set.
These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning233 instances
233 of 559 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning190 instances
190 of 190 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)
- Warning38 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)
- Warning7 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · 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
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt 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)
- Info559 instances
Trip with shape dist traveled but no shape distances (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_with_shape_dist_traveled_but_no_shape_distances' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: trip_with_shape_dist_traveled_but_no_shape_distances · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info49 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
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus 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
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · 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
Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 58% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 358 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 58% 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 99.5% of 200 checks over the last 27 days, with 6s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 358 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 16 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 43 / 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 46 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 100 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/fr-cmonbus/2026-09-07.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-07. 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.