← All agencies

Feed status · checked 2026-10-16

Réseau urbain agglo'Bus

Based on the official feed source on file

Service mode Bus

FDCBA

93.2 / 100

unchanged since 2026-10-15

Cataloged in Nouvelle-Aquitaine, France.

Covers 319 daysAccessibility gapsRealtime not yet published

Source feed: https://www.data.gouv.fr/api/1/datasets/r/4b6bb4e3-86de-491c-8a0a-7892a02ccb60

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 3 hours ago; last changed 45 days ago.

Measured 3 of 4 score categories from the official feed URL on file.

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 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 agglo'Bus’s published feed lists 8 bus routes, 117 scheduled trips and 69 stops. Its service dates run from 2026-08-03 through 2027-08-31. The published file has not changed since our first check on 2026-09-01.

Top things to fix

Fix 01

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

117 of 117 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 117 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 02

Delete the empty calendars or set their service days.Likely your export tool

Some service calendars have no days of the week switched on. Trips tied to these calendars never run; they are dead data that can mask real schedule problems.

This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

⏱ A few minutes in your scheduling software.worth about +4 points in its category

Fix 03

Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar.

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.

This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

⏱ A review of your calendar dates.

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

Agency: Réseau urbain agglo'Bus
Finding: scorecard_wheelchair_accessible_unknown
Feed evidence: 117 of 117 trips don't say whether the vehicle is wheelchair accessible.
Why it matters: Even with accessible stops, riders need to know the bus itself can take them.
Requested change: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Evidence: https://gtfsscorecard.org/agency/fr-pan-79483/?finding=scorecard_wheelchair_accessible_unknown#finding-handoff

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_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. Self-check a feed before you publish.
Fix 02 · Read the fix guide for service_has_no_active_day_of_the_week
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.
Fix 03 · Read the fix guide for big_gap_in_service
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 319 days.
Published accessibility data: Accessibility information is stated for 100% 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: 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.

Hi,

Our GTFS feed (Réseau urbain agglo'Bus) scored A (93.2 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 117 of 117 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

2. Delete the empty calendars or set their service days.
   What: Some service calendars have no days of the week switched on.
   Finding code: service_has_no_active_day_of_the_week
   Guide: https://gtfsscorecard.org/fix/service_has_no_active_day_of_the_week/

3. Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar.
   What: The feed has a stretch of two weeks or more with no service running.
   Finding code: big_gap_in_service
   Guide: https://gtfsscorecard.org/fix/big_gap_in_service/

Full scorecard: https://gtfsscorecard.org/agency/fr-pan-79483/

Score by category

Correctness95.2 / 100

The MobilityData validator flagged 2 kinds of issue across 10 instances (0 error, 1 warning, 9 informational).

Freshness100.0 / 100

Service data covers the next 319 days.

Rider experience85.0 / 100

100% of stops state wheelchair accessibility (62% marked accessible, 38% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.

Accessibility62.5 / 100

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

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

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.

This feed has 69 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.

L1 (yellow)
L2 (teal)
L3 (pink)
L4 (blue)
L5 (red)
L6 (brown)
L7 (purple)
L8 (yellow)

Routes in Réseau urbain agglo'Bus's feed
Route	Type	Line color
L1 Ligne 1	Bus	yellow
L2 Ligne 2	Bus	teal
L3 Ligne 3	Bus	pink
L4 Ligne 4	Bus	blue
L5 Ligne 5	Bus	red
L6 Ligne 6	Bus	brown
L7 Ligne 7	Bus	purple
L8 Ligne 8	Bus	yellow

List every stop

Allendé
Allendé
Beauregard
Bellevue
Berry
Place Bonnyaud
Lycée Bourdan
Lycée Bourdan
Brésard
Brésard
Carnot
René Cassin
Docteur Chantrelle
Charsat
Charles de Gaulle
Clinique de la Marche
Courtille
Croizat
Saint Exupéry
Lycée Favard
Fayolle
Fayolle
Gambetta
Gambetta
Ecole de la Garde
Gare SNCF
Gare SNCF
Professeur Grancher
Professeur Grancher
Guillaumin
Guillon
Hôpital
Hôpital
Hôtel de Ville
Hôtel de Ville
Eugène Jamot Braconne
Jean Moulin
Jouhet
Labetoulle
Ecole Langevin
Louis Laroche
Avenue de Laure
Limousin
Limousin
Maindigour
Maindigour
Petit Malleret
Place du Marché
Marc Bloch
Collège Marouzeau
Collège Marouzeau
Mendès France
Montplaisir
Montplaisir
Collège Nadaud
Picasso
Picasso
Poitou
Ecole Prévert
Ecole Prévert
Anna Quinquaud
Rhin Danube
Ribière
Schoelcher
Schoelcher
Sylvain Blanchet
Tabarly
Place du Tilleul
Le Verger

Over time

Overall score across the last 15 checks — unchanged since 2026-10-15.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-02	93.2	first check
2026-10-03	93.2	no change
2026-10-04	93.2	no change
2026-10-05	93.2	no change
2026-10-06	93.2	no change
2026-10-07	93.2	no change
2026-10-08	93.2	no change
2026-10-09	93.2	no change
2026-10-10	93.2	no change
2026-10-11	93.2	no change
2026-10-12	93.2	no change
2026-10-13	93.2	no change
2026-10-14	93.2	no change
2026-10-15	93.2	no change
2026-10-16	93.2	no change

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change

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.

Feed history by published file
Checked	Published file	Service dates through	Grade at the time
2026-10-02 to 2026-10-16 (15 checks)	`96328e4b2490`	2027-08-31	Current rubric: see the trend above
2026-09-01 to 2026-10-01 (27 checks)	`96328e4b2490`	2027-08-31	B, 88.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

Overall grade and score held steady since 2026-10-15.

Same feed file as 2026-10-15; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.

Everything we checked

3 findings, ordered by severity.

Show every finding

Warning117 instances
117 of 117 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)
Warning1 instance
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Finding code: service_has_no_active_day_of_the_week · Read the fix guide for service_has_no_active_day_of_the_week · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info9 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)

Conformance mark Not yet

One requirement remains for this feed to earn the conformance mark. States wheelchair access on 100% 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 319 days.
Accessible Not yet: States wheelchair access on 100% 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.

Clears the Google and Apple Maps four-week coverage bar. This feed has 319 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 95 / 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 85 / 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.

Part of the France portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Nouvelle-Aquitaine

Other scorecards in Nouvelle-Aquitaine, 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.

Badge HTML

<a href="https://gtfsscorecard.org/agency/fr-pan-79483/"><img src="https://gtfsscorecard.org/agency/fr-pan-79483/badge.svg" width="320" height="58" alt="Réseau urbain agglo&#x27;Bus: current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![Réseau urbain agglo'Bus: current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/fr-pan-79483/badge.svg)](https://gtfsscorecard.org/agency/fr-pan-79483/)

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

GTFS Scorecard. (2026). Réseau urbain agglo'Bus GTFS feed-quality record, dated 2026-10-16 (grade A (93.2/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 96328e4b2490…). https://gtfsscorecard.org/data/artifacts/fr-pan-79483/2026-10-16.json

@misc{gtfsscorecard-fr-pan-79483-2026-10-16,
  title        = {Réseau urbain agglo'Bus GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/fr-pan-79483/2026-10-16.json}},
  note         = {Checked 2026-10-16; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade A (93.2/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.