Feed status · checked 2026-10-16
Réseau urbain Glazgo
Based on the official feed source on file
Service mode Bus
down 4.7 since 2026-10-15
Cataloged in Bretagne, France.
Source feed: https://www.data.gouv.fr/api/1/datasets/r/4dc52cb9-909e-40dd-80e5-a90073bc80fc
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.4, validator 8.0.1.
Checked for changes 37 minutes ago; last changed 17 days 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.
About this feed
Réseau urbain Glazgo’s published feed lists 3 bus routes, 296 scheduled trips and 160 stops. Its service dates run from 2026-08-31 through 2027-07-02. It publishes realtime trip updates, vehicle positions and service alerts; when we checked, all of them answered. The published file last changed on 2026-09-29.
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
157 of 160 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.
Fixing this covers 157 of 160 stops, about 98% of them.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +24 points in its category
Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out.
2 of 3 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.
This was measured over a realtime sampling window, so it has no feed-wide share.
⏱ A vendor data-mapping question.worth about +23 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
296 of 296 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 296 trips in the feed.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Riders and need behind these fixes
- Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
- The served-area need overlays cover the United States and Canada, so none of them applies to this feed.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested change.
- 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.
Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown
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.
Fix 02 · Read the fix guide for scorecard_rt_trip_coverage
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.
Fix 03 · Read the fix guide for scorecard_wheelchair_accessible_unknown
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 259 days.
- Published accessibility data
- Accessibility information is stated for 1.9% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- Live-arrival data covered 33.3% 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 5 kinds of issue across 1377 instances (0 error, 1331 warning, 46 informational).
Service data covers the next 259 days.
2% of stops state wheelchair accessibility (2% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
2% of stops state accessibility (2% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
3 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Bibliothèque/Mairie", "Bibliothèque/Mairie", "Bibliothèque/Mairie").
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.
Fares are applied to trips.
Sampled 9 times: 3 of 3 configured feeds healthy; 33.3% of scheduled trips had live predictions; 100.0% of vehicles on their route; predictions ran a median of 88s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 160 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.
- A (white)
- B (white)
- C (white)
| Route | Type | Line color |
|---|---|---|
| A Auray Alre'O - Auray Gare | Bus | white |
| B Brec’h St Gildas - Pluneret Gare Ste Anne | Bus | white |
| C Auray Gare - Crac’h Henri Le Doré | Bus | white |
List every stop
- La Forêt
- La Forêt
- Belgique
- Duquesne
- Danemark
- Alre'O
- Kerbois
- Mozart
- Gumenen
- Villeneuve
- MAL
- Kerléano
- Bel Air
- Lann Roz
- Le Verger
- Rostevel
- Royère
- Père Eternel
- Keriolet
- Château
- Boceno
- Kerdrain
- Belgique
- Duquesne
- Kerbois
- Mozart
- Villeneuve
- MAL
- Kerléano
- Bel Air
- Lann Roz
- Le Verger
- Rostevel
- Keriolet
- Château
- Boceno
- Kerdrain
- Bibliothèque/Mairie
- Denis Papin
- Foch
- Gare Sainte-Anne
- Gros Sel
- Hôtel de Ville
- Kerfontaine
- Le Ballon
- Le Beg Du
- Montfort
- Notre Dame
- Terre Rouge
- Toulchignanet
- Le Creslin
- Penhoët
- Duguesclin (lycée)
- Ampère
- Stade
- Ampère
- Le Beg Du
- Bibliothèque/Mairie
- Château
- Denis Papin
- Duguesclin (lycée)
- Gros Sel
- Kerfontaine
- Le Ballon
- Le Creslin
- Montfort
- Penhoët
- Pont-Sablen
- Stade
- Terre Rouge
- Toulchignanet
- Barré
- Les Augustines
- Bretagne
- Europe
- Moustoir
- Parc Utting
- Toul Garros
- Keropert
- Général de Gaulle
- Bois Colette
- Bois Colette
- Général de Gaulle
- Gumenen
- Keropert
- Henri Le Doré
- Parc Utting
- Gare Sainte-Anne
- Saint-Gildas
- Le Ballon
- Le Ballon
- Wilson
- Wilson
- Ty Coat
- Ty Coat
- Toulchignanet
- Europe
- Belgique
- Bretagne
- Duquesne
- Moustoir
- Le Beg Du
- Toul Garros
- Gros Sel
- Danemark
- Kerbois
- Alre'O
- Keropert
- Montfort
- Mozart
- Villeneuve
- Gumenen
- MAL
- Parc Utting
- Kerléano
- Lann Roz
- Le Ballon
- Le Verger
- Rostevel
- Foch
- Royère
- Keriolet
- Ty Coat
- Notre Dame
- Château
- Hôtel de Ville
- Père Eternel
- Pont-Sablen
- Wilson
- Terre Rouge
- Kerfontaine
- Gare Sainte-Anne
- Denis Papin
- Bibliothèque/Mairie
- Kerdrain
- Saint-Gildas
- Le Creslin
- Penhoët
- Duguesclin (lycée)
- Ampère
- Stade
- Barré
- Les Augustines
- Général de Gaulle
- Henri Le Doré
- La Forêt
- Bel Air
- Boceno
- Bois Colette
- Kerdrain
- Gare SNCF
- Le Ballon - JF Kennedy
- Le Ballon - JF Kennedy
- Gare SNCF
- Le Ballon - JF Kennedy
- Porte Océane
- Porte Océane
- Le Loch
- Porte Océane
- Le Loch
Over time
Overall score across the last 15 checks — down 4.7 since 2026-10-15.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-02 | 82.0 | first check |
| 2026-10-03 | 82.0 | no change |
| 2026-10-04 | 82.0 | no change |
| 2026-10-05 | 82.0 | no change |
| 2026-10-06 | 82.0 | no change |
| 2026-10-07 | 82.0 | no change |
| 2026-10-08 | 82.0 | no change |
| 2026-10-09 | 82.0 | no change |
| 2026-10-10 | 82.0 | no change |
| 2026-10-11 | 82.0 | no change |
| 2026-10-12 | 82.0 | no change |
| 2026-10-13 | 82.0 | no change |
| 2026-10-14 | 82.0 | no change |
| 2026-10-15 | 82.0 | no change |
| 2026-10-16 | 77.3 | down 4.7 |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality down 23.3
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-10-02 to 2026-10-16 (15 checks) | 8622e20cc386 | 2027-07-02 | Current rubric: see the trend above |
| 2026-09-29 to 2026-10-01 (3 checks) | 8622e20cc386 | 2027-07-02 | B, 82 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-09-01 to 2026-09-28 (24 checks) | e42bef2cfa01 | 2027-07-02 | D, 61.8 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
What changed in this feed
Grade dropped from B to C since 2026-10-15.
Same feed file as 2026-10-15; the published zip did not change.
New since 2026-10-15 (1 finding)
- Warning2 instances
2 of 3 trips scheduled during the sampling window had no live predictions.
Finding code: scorecard_rt_trip_coverage · Read the fix guide for scorecard_rt_trip_coverage · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
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-10-02 this feed started at grade B. On 2026-10-16 the grade moved from B to C. As of 2026-10-16 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-10-16 Grade went B to C, realtime fell 23 points.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning1109 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)
- Warning296 instances
296 of 296 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning204 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 for trip_distance_exceeds_shape_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning157 instances
157 of 160 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning18 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 for stop_too_far_from_shape_using_user_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
2 of 3 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 for scorecard_rt_trip_coverage · See GTFS-Realtime reference (opens the GTFS-Realtime reference 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 for scorecard_station_no_pathways · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info45 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 for big_gap_in_service · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Feed valid beyond total service window (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'feed_valid_beyond_total_service_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: feed_valid_beyond_total_service_window · 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 2% 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 259 days.
- Accessible Not yet
- States wheelchair access on 2% 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.
Realtime reliability
The realtime feed responded on 100.0% of 200 checks in the 25 days to 2026-10-16, with 8s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.
Live predictions vs schedule
Arrival predictions ran a median 88s late versus the schedule, and stayed within 320s nine times in ten. They were on time (about a minute early to five late) 79.0% of the time. 100.0% of reported vehicle positions sat on or near the published route shape.
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 259 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 77 / 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 60 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 77 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Part of the France portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Bretagne
Other scorecards in Bretagne, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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-83300/2026-10-16.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-10-16. 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.