GTFS Scorecard
← All agencies

Feed status · checked 2026-09-01

Réseau urbain Glazgo

Based on the official feed source on file

Service mode Bus

70.1 / 100

First scorecard for this agency

Catalogued in Bretagne, France.

Covers 304 daysAccessibility gaps

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 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

Fix 01

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 +24 points in its category

Fix 02

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

437 of 445 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

Fix 03

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

806 of 806 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

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
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.

  1. 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. Self-check a feed before you publish.

  2. 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.

  3. 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.

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 304 days.
Published accessibility data
Accessibility information is stated for 1.8% 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 100% 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

Correctness42.8 / 100

The MobilityData validator flagged 8 kinds of issue across 3557 instances (65 error, 3453 warning, 39 informational).

Freshness100.0 / 100

Service data covers the next 304 days.

Rider experience60.4 / 100

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.

Accessibility1.1 / 100

2% of stops state accessibility (2% marked accessible). Reflects what the feed states, not verified physical usability.

3 accessibility depth signals

  • 1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (E6).

    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.

  • 7 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Place St Michel", "Place St Michel", "Bibliothèque/Mairie", and more).

    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.

FaresLegacy fares

Fares are applied to trips.

Realtime quality100.0 / 100

Sampled 9 times: 3 of 3 configured feeds healthy; 100.0% of scheduled trips had live predictions; 100.0% of vehicles on their route; predictions ran a median of 128s behind schedule.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 445 stops.

Skip to route and stop data

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)
  • E1 (gray)
  • E2 (teal)
  • E3 (white)
  • E4 (teal)
  • E5 (pink)
  • E6 (blue)
  • E7 (white)
  • E8 (white)
  • E9 (orange)
  • E10 (red)
  • C (white)
Routes in Réseau urbain Glazgo's feed
RouteTypeLine color
A Auray Alre'O - Auray GareBuswhite
B Brec’h St Gildas - Pluneret Gare Ste AnneBuswhite
E1 Erdeven - PlouharnelBusgray
E2 Saint-Pierre-Quiberon - QuiberonBusteal
E3 Quiberon EstBuswhite
E4 Quiberon OuestBusteal
E5 Carnac - CarnacBuspink
E6 CarnozBusblue
E7 Carnac - La Trinité-sur-MerBuswhite
E8 La Trinité-sur-Mer - La Trinité-sur-MerBuswhite
E9 Crach - Saint-PhilibertBusorange
E10 Crach - LocmariaquerBusred
C Auray Gare - Crac’h Henri Le DoréBuswhite
List every stop
  • La Forêt
  • Place St Michel
  • La Forêt
  • Place De Gaulle Marché
  • 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
  • Anatole France
  • Place De Gaulle
  • Armorique / Quatre Vents
  • Kerchican
  • Kerchican
  • Base Nautique
  • Boulevard du Conguel
  • Campings
  • Complexe sportif
  • Complexe sportif
  • Bourg
  • Gare SNCF
  • Bourg
  • Briellec
  • Kerhillio
  • Kerhillio
  • Camping de Kerné
  • Saint Antoine
  • Camping du Conguel
  • Camping du Rohu
  • Camping du Rohu
  • Camping Keravel
  • Camping Keravel
  • Camping La Croix Villieu
  • Camping La Croix Villieu
  • Camping Les Ormeaux
  • Camping Les Ormeaux
  • Camping L'Idéal
  • Camping L'Idéal
  • Le Relais de l'Océan
  • Château Turpault
  • Cinéma
  • Centre Ville (rue Général de Gaulle)
  • Centre Ville (Place de la Marne)
  • Duchesse Anne
  • Eglise
  • Métairie
  • Igesa
  • Kasino
  • Kergallo
  • Kermario
  • Kermarquer
  • Kermarquer
  • Kermorvan
  • Kerniscob
  • Kervillen
  • Kervilor
  • Rond Point Kervozès
  • Korrigans
  • La Mare aux Canards
  • Manémeur
  • Notre Dame de Lotivy
  • Notre Dame de Lotivy
  • Ménec
  • Moustoir
  • Parking Charles de Gaulle
  • Camping Plijadur
  • Camping Plijadur
  • Parking des Alignements
  • Place Hoche
  • Plage de Kerbougnec
  • Plage de Kerbougnec
  • Le Fozo
  • Le Fozo
  • Plage du Vahidy
  • Plage du Vahidy
  • Port en Dro
  • Port Haliguen
  • Port Maria
  • Portivy
  • Portivy
  • Poul Douar
  • Poul Douar
  • Quai des Saveurs
  • Roch-Priol
  • Le Nignol
  • Centre Commercial
  • Arvor
  • Arvor
  • Thalasso
  • Varquez
  • Le Vivier
  • Rue du Parco
  • Rue du Parco
  • Bourg (cimetière)
  • Bourg - Office de Tourisme
  • Camping de La Falaise
  • Camping La Ferme Fleurie
  • Camping Kerarno
  • Camping de Kerpenhir
  • Camping de La Tour
  • Camping Lann Brick
  • Le Guilvin
  • Camping Les Palmiers
  • Les Presses
  • Site des Mégalithes
  • Plage de Men Er Beleg
  • Les Pierres Plates
  • Plage de Kernevest
  • Pointe de Kerpenhir
  • Gare Sainte-Anne
  • Saint-Gildas
  • Le Ballon
  • Le Ballon
  • Wilson
  • Wilson
  • Roer
  • Roer
  • Site des Mégalithes
  • Bourg - Office de Tourisme
  • Camping Lann Brick
  • Camping Les Palmiers
  • Parking Corniche
  • Parking Corniche
  • Plage de Kernevest
  • Plage de Men Er Beleg
  • Camping Kerarno
  • Bourg (cimetière)
  • Camping La Ferme Fleurie
  • Discothèque Les Chandelles
  • Ty Coat
  • Ty Coat
  • Anatole France
  • Armorique / Quatre Vents
  • Kerchican
  • Base Nautique
  • Boulevard du Conguel
  • Campings
  • Complexe sportif
  • Bourg
  • Briellec
  • Kerhillio
  • Camping de Kerné
  • Saint Antoine
  • Camping du Conguel
  • Camping du Rohu
  • Camping Keravel
  • Camping La Croix Villieu
  • Camping Les Ormeaux
  • Camping L'Idéal
  • Le Relais de l'Océan
  • Roer
  • Château Turpault
  • Cinéma
  • Centre Ville (rue Général de Gaulle)
  • Duchesse Anne
  • Eglise
  • Gare SNCF
  • Métairie
  • Igesa
  • Discothèque Les Chandelles
  • Kasino
  • Kergallo
  • Kermario
  • Kermarquer
  • Kermorvan
  • Kerniscob
  • Kervillen
  • Kervilor
  • Rond Point Kervozès
  • Korrigans
  • and 195 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

11 findings, ordered by severity.

Show every finding
  • Error65 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

  • Warning2836 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

  • Warning806 instances

    806 of 806 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

  • Warning562 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

  • Warning437 instances

    437 of 445 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

  • Warning41 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

  • Warning13 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

  • Warning1 instance

    Many of the feed's trips don't run at all in the next 7 days.

    It usually means old service periods are still in the export, making the feed bigger and harder to check.

    Fix: Trim past service periods the next time you export. (One setting in most export tools.)

    Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

  • Info38 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

  • 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

Conformance mark Not yet

Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 2% of stops and 0% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 304 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.

Live predictions vs schedule

Arrival predictions ran a median 128s late versus the schedule, and stayed within 390s nine times in ten. They were on time (about a minute early to five late) 75.8% 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 304 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 65 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 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 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.

Réseau urbain Glazgo GTFS data quality grade: C

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-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.