Feed status · checked 2026-07-23
Réseau urbain Grandole Mobilités
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Bourgogne-Franche-Comté, 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.
Checked for changes 1 hours ago; last changed 1 hours ago.
Measured 4 of 4 score categories from the agency's own feed.
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 6 snapshots.
- 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
338 of 416 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 +20 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
656 of 656 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 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
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.
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. Self-check a feed before you publish.
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.
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 69 days.
- Published accessibility data
- Accessibility information is stated for 18.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
- 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 7 kinds of issue across 138 instances (0 error, 110 warning, 28 informational).
Service data covers the next 69 days.
19% of stops state wheelchair accessibility (19% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
19% of stops state accessibility (19% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
12 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 3, LZ, 10, 11, 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.
4 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Biarne St Vivant", "Biarne St Vivant", "Damparis Rue du Moulin (Rd Point.)", 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.
Sampled 6 times outside service hours: 2 of 2 configured feeds healthy; vehicle position plausibility was not measurable; predictions ran a median of 10s behind schedule.
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.
- 1 (pink)
- 10 (green)
- 11 (teal)
- 12 (gray)
- 13 (pink)
- 14 (red)
- 15 (gray)
- 16 (teal)
- 17 (yellow)
- 18 (purple)
- 2 (teal)
- 20 (yellow)
- 21 (purple)
- 22 (yellow)
- 3 (green)
- LZ (orange)
| Route | Type | Line color |
|---|---|---|
| 1 Choisey Autoroute <> Dole Grandes Epenottes 1 | Bus | pink |
| 10 Saint-Aubin <> Dole | Bus | green |
| 11 Biarne <> Dole | Bus | teal |
| 12 Moissey <> Dole | Bus | gray |
| 13 Champagney <> Dole | Bus | pink |
| 14 Villers-Robert > Dole / Dole > Villers-Robert > Nevy-Lès-Dole | Bus | red |
| 15 Tavaux <> Dole | Bus | gray |
| 16 Champvans <> Dole | Bus | teal |
| 17 Lavans-Lès-Dole <> Dole | Bus | yellow |
| 18 Romange > Dole / Dole > Romange > Auxange | Bus | purple |
| 2 Tavaux Collège <> Dole Gare | Bus | teal |
| 20 Saint-Aubin <> Tavaux | Bus | yellow |
| 21 Saint-Aubin <> Damparis | Bus | purple |
| 22 Sampans <> Damparis | Bus | yellow |
| 3 Dole Lycée Duhamel <> Dole La Paule | Bus | green |
| LZ Tavaux Solvay <> Rochefort Zone des Toppes | Bus | orange |
This feed has 416 stops.
List every stop
- Abergement Carrefour de Damparis
- Abergement Carrefour de Damparis
- Abergement Rue du Centre
- Abergement Rue du Centre
- Abergement Rue de Samerey
- Abergement Rue de Tavaux
- Abergement Rue de Tavaux
- amange abribus
- AMANGE Ecole
- Amange Ecole
- Amange Ecole
- Archelange Centre
- Archelange Centre
- Archelange Ecole
- Archelange Eglise
- Audelange Centre
- Audelange Centre
- Aumur Eglise
- Aumur Eglise
- Authume Autoroute
- Authume Chemin Blanc
- Authume Mairie
- Authume Mairie
- Authume Stade
- Authume Stade
- Auxange Centre
- baverans grande rue
- Baverans Rue des Crêts
- Baverans Rue des Crêts
- Baverans Ecole
- Baverans Ecole
- Baverans lot.Parc
- Biarne Ecole
- Biarne St Vivant
- Biarne St Vivant
- Brevans Grande Rue
- Brevans Grande Rue
- Brevans Mairie
- Brevans Mairie
- Parc de Brevans
- Parc de Brevans
- Brevans Rue des Vignes
- Brevans Rue des Vignes
- Champvans Rue de Damparis
- Champvans Rue de Damparis
- Champvans Ecole
- Champvans Huffenhardt
- Champvans Huffenhardt
- Champvans Le Luminaire
- Champvans Le Luminaire
- Champvans Atelier Municipal
- Champvans Atelier Municipal
- Champagney Nilieu
- Champvans Pont SNCF
- Champvans Stade
- Champvans Stade
- Champdivers Rue du Finage
- Champdivers Rue du Finage
- champagney nilieu
- Champagney Place
- Champagney Tuilerie
- Choisey Autoroute
- Choisey Eglise
- Choisey Eglise
- Choisey Gagnières
- Choisey Gagnières
- Choisey Larges Pierres
- Choisey Larges Pierres
- Choisey Paradis
- Choisey Rougelots
- Champdivers Ecole
- Châtenois Centre
- Chevigny
- Chevigny
- Crissey Les Baraques
- Crissey Les Baraques
- Crissey La Boutière
- Crissey La Boutière
- Crissey Combotte
- Crissey Combotte
- Crissey Rue du Loup
- Crissey Rue du Loup
- Crissey Mairie
- Crissey Mairie
- Crissey Meix Brulés
- Crissey Meix Brulés
- Crissey Ronceraie
- Crissey Ronceraie
- Damparis Park. Abbaye
- Damparis Belvoye
- Damparis Belvoye
- Damparis Casanova
- Damparis Collège
- Damparis Collège
- Damparis Concorde
- Damparis Concorde
- Damparis Rue des Cosaques
- Damparis Allée des Fleurs
- Damparis Rue Gabriel Péri
- Damparis HLM Les Moules
- Damparis Malnouhe
- Damparis Malnouhe
- Damparis Rue du Moulin (Carf Beauregard)
- Damparis Monument
- Damparis Monument
- Damparis Rue du Moulin (Rd Point.)
- Damparis Rue du Moulin (Cab tel.)
- Damparis Place du 1er Mai (ecole primaire)
- Damparis Rue Roger Bride
- Damparis Rue de Champvans
- Damparis Rue de Champvans
- Damparis Soleil
- Damparis Soleil
- Damparis Sous les Vignes
- Damparis Sous les Vignes
- Damparis Vignes
- 11-nov
- 11-nov
- Aberjoux
- Aberjoux
- Ameter
- Ameter
- Azans
- Azans
- Barberousse
- Barberousse
- Bastié
- Beauregard
- Beauregard
- La Bedugue
- La Bedugue
- Berlioz
- Berlioz
- Bizard
- Bizard
- Charles Blind
- Charles Blind
- Bougauld
- Bougauld
- Boyvin
- Briand
- Bugnardes
- Bugnardes
- Cimetière 1
- Cimetière 1
- Cimetière 2
- Cimetière 2
- Cinorodons
- Cinorodons
- Collège
- Combe Truchenne 1
- Les Commards
- Les Commards
- Constant
- Constant
- La Corniche
- La Corniche
- Avenue de la Côte d'Or
- Avenue de la Côte d'Or
- Place du Coulon
- Place du Coulon
- Crechot
- Crechot
- Defois
- Defois
- Descartes
- Descartes
- Lycée Duhamel
- Lycée Duhamel
- Léon Bel
- Eisenhower
- Eisenhower
- Grandes Epenottes
- Dolexpo
- Dolexpo
- Foch
- Foch
- Dole Gare
- Grandes Carrières SNCF
- Grandes Carrières SNCF
- Général Béthouart
- Goux Place de la Cornée
- Goux Place de la Cornée
- Goux Ecole
- Goux Ecole
- Goux Lotissement
- Goux Lotissement
- Guignard
- Gujean
- Gujean
- Hézard
- Hézard
- Hopital Pasteur
- Hopital Pasteur
- Jantet Gare
- Landon Eglise
- Landon Eglise
- De Lattre de Tassigny
- De Lattre de Tassigny
- Collège Ledoux
- Lombard
- Lombard
- Longeottes
- Longeottes
- Machard
- Machard
- Marcuse
- Marcuse
- Rue Jean Mermoz
- Rue Jean Mermoz
- Montciel
- Montciel
- Mont d'Alland
- Mont d'Alland
- Montée Rouge
- Montée Rouge
- Muguet
- Muguet
- Pacottes
- Pacottes
- Paters
- Paters
- La Paule
- Mont des Pins
- Mont des Pins
- Plumont
- Plumont
- Place Novarina
- Place Novarina
- Pointelin
- Pointelin
- Poiset
- Poiset
- Cité des Polonais
- Cité des Polonais
- Pont Saint-Martin
- Pont Saint-Martin
- Rue de Chaux
- Rue de Chaux
- Résistance
- Résistance
- Mont Roland
- Rue de Séans
- Rue de Séans
- Souvenir Français
- Sombardier
- Saint-Germain-Les-Noches
- Saint-Germain-Les-Noches
- Dole Saint Mauris
- Templiers
- and 166 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
12 findings, ordered by severity.
Show every finding
- Warning656 instances
656 of 656 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning338 instances
338 of 416 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)
- Warning50 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.)
Validator rule: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning48 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Validator rule: stop_without_stop_time · 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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 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.)
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Validator rule: fast_travel_between_consecutive_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.)
Validator rule: 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.)
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)
- Info28 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.)
Validator rule: 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).
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 19% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 69 days.
- Accessible Not yet
- States wheelchair access on 19% 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 48 of 416 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Realtime reliability
The realtime feed responded on 100.0% of 1 checks, with 10s 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 a median 10s late versus the schedule, and stayed within 130s nine times in ten. They were on time (about a minute early to five late) 100.0% 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 68 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 69 / 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 42 / 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-grandole-mobilites/2026-07-23.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-23. 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.