Feed status · checked 2026-08-01
Réseau urbain L'Agglo en Bus
Based on the feed this agency publishes
Service mode Bus
up 1.1 since 2026-07-31 · D → D
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 79 minutes ago; last changed 9 days 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
343 of 346 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
Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.
6 of 13 trips scheduled during the sampling window had no live predictions. Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
⏱ A vendor data-mapping question.worth about +16 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
577 of 577 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
- 343 of 346 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
- 6 of 13 trips scheduled during the sampling window had no live predictions.
- Next action
- Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.
- 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
- 577 of 577 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- 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.
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.
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.
Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. · 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.
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. 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 152 days.
- Published accessibility data
- Accessibility information is stated for 0.9% 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
- Live-arrival data covered 53.8% 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 90 instances (0 error, 90 warning, 0 informational).
Service data covers the next 152 days.
1% of stops state wheelchair accessibility (1% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
1% of stops state accessibility (1% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
8 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 20, 3, 4, 6, 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.
2 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Parc St Joseph", "E.P.H.A.D St.Mens").
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 6 times: 2 of 2 configured feeds healthy; 53.8% of scheduled trips had live predictions; 100.0% of vehicles on their route; predictions ran a median of 104s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 346 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.
- 1 (red)
- 2 (purple)
- 20 (pink)
- 21 (red)
- 22 (red)
- 23 (red)
- 3 (green)
- 4 (orange)
- 5 (teal)
- 6 (yellow)
- 7 (teal)
- 8 (white)
- 9 (brown)
| Route | Type | Line color |
|---|---|---|
| 1 LIGNE 1 Serviolan - Bonneval (La Source) | Bus | red |
| 2 LIGNE 2 Molines - (Le Rigodon) Les Gontiers | Bus | purple |
| 20 LIGNE 20 NRE Saint-Louis - Balmens | Bus | pink |
| 21 LIGNE 21 CENTRO A : LA NAVETTE DU COEUR DE VILLE | Bus | red |
| 22 LIGNE 22 CENTRO B : PIDDINGTON>GOURLANCHES>KAPADOS | Bus | red |
| 23 LIGNE 23 CENTRO C : CHATELARD>BEAUCHATEAU>FAUVINS | Bus | red |
| 3 LIGNE 3 Les Prés - Romette | Bus | green |
| 4 LIGNE 4 Tokoro - Saint-Jean | Bus | orange |
| 5 LIGNE 5 Pôle Universitaire - Les Emeyères | Bus | teal |
| 6 LIGNE 6 (Châteauvieux) Les Abadous - Tournefave | Bus | yellow |
| 7 LIGNE 7 Faure du Serre - Parassac | Bus | teal |
| 8 LIGNE 8 Les Grandes Terres - La Justice | Bus | white |
| 9 LIGNE 9 Centre Ville - Romette | Bus | brown |
| HLP HAUT LE PIED | Bus | white (no shape in feed) |
List every stop
- Académie
- Arpège
- Florian
- Foyer de Fontreyne
- Foyer de Fontreyne
- Quai 8 de la gare S.N.C.F
- Quai 7 de la gare S.N.C.F
- Quai 2 de la gare S.N.C.F
- Graffinel
- Muret
- Guillaume Farel
- Guillaume Farel
- Guisane
- Hameau de Puymaure
- Hameau de Puymaure
- Hauteville
- Hauteville
- Hôpital
- Hôpital de l'Adret
- Impasse Sixtine
- Avenue d'Embrun
- Jean Jaurès
- Jean Jaures
- Jean Macé
- Jean Macé
- Kapados
- La Chenaie
- La Chenaie
- La Commanderie
- La Commanderie
- Balmens
- La Descente
- La Descente
- La Durance
- La Glacière
- La Justice
- La Justice
- La Luye
- La Luye
- La Poste
- Bas Collet
- La Providence
- La Romettine
- La Romettine
- La Source
- La Source
- La Tourronde
- La Tourronde
- La Valériane
- Bas Collet
- Lachaup
- Ladoucette
- Lareton
- Lareton
- Le Bois de St-Jean
- Le Bois de St-Jean
- Le Buzon
- Le Buzon
- Le Chaffal
- Boulevard d'Orient
- Le Château d'eau
- Le Clos de Charance
- Le Clos de Charance
- Le Collet
- Le Collet
- Le lac
- Boulevard d'Orient
- Le Montana
- Le Panoramic
- Le Pavillon
- Le Pavillon
- Le Puymaure
- Le Rigodon
- Le Rigodon
- Le Rio
- Le Rio
- Beauchâteau
- Le Riotord
- Le Riotord
- Le Saint Joseph
- Le Saint Pascal
- Le Torrent de la Selle
- Le Torrent de la Selle
- Le Turrelet
- Le Turrelet
- Le Vieux Chemin
- Le Vieux Chemin
- Le Villard
- Le Villard
- Les Abadous
- Les Bruyères
- Les Buissonnets
- Les Buissonnets
- Les Castors
- Les Cèdres
- Les Cèdres
- Les Cheminots
- Académie
- Les Cheminots
- Les Chênes
- Les Chênes
- Les Ecrins
- Les Ecrins
- Les Eymeyères
- Les Eymeyères
- Les Fangerots
- Les Fangerots
- Bel Air
- Les Farelles
- Les Farelles
- Les Fauvins
- Les Fauvins
- Les Genêts
- Les Genêts
- Les Gontiers
- Les Gourlanches
- Les Gourlanches
- Les Grandes Terres
- Bel Air
- Les Lacets
- Les Lacets
- Les Lauriers
- Les Lauriers
- Les Lilas
- Les Lilas
- Les Marronniers
- Les Métiers
- Bel Aure
- Les Métiers
- Les Noisetiers
- Les Noisetiers
- Les Pins
- Les Pinsons
- Les Pinsons
- Les Poncets
- Les Poncets
- Les Prés
- Les 4 Vents
- Bel Aure
- Les 4 Vents
- Les Silos
- Les Silos
- Les Terrasses
- Les Thermes
- Les Thermes
- Les Tilleuls
- Les Tilleuls
- Les Tourterelles
- Les Vergers
- Bellevue
- Les Vergers
- Les Vigneaux
- Les Vigneaux
- Lesdiguières
- Lesdiguières
- Lotissement Beauchâteau
- Lotissement les Gourlanches
- Lycée Agricole
- Bellevue
- Mairie de Romette
- Mairie de Romette
- Maison de la santé au travail
- Maison de la santé au travail
- Malcombe
- Malcombe
- Médiathèque-Théâtre
- Mermoz
- Mermoz
- Micropolis
- Micropolis
- Molines
- Montclair
- Montclair
- Moulin du Pré
- Moulin du Pré
- Nestlé
- Nestlé
- Parassac
- Parc du château
- Parc St Joseph
- Patac
- Patac
- Pervenches
- Bonne
- Pervenches
- Petit séminaire
- Petit séminaire
- Piddington
- Pignerol
- Pignerol
- Place de Kapados
- Pôle Universitaire
- Albert Borel
- Bonne
- Pôle Universitaire
- Pôle Universitaire
- Pompidou
- Pont Blanc
- Pont Blanc
- Pont Sarrazin
- Pont Sarrazin
- Porte Colombe
- Bonneval
- Residence Val du Plan
- Rochasson
- Rochasson
- Roland Garros
- Romette Pré mongil
- Rousine
- Rousine
- Route de Colombis
- Route des Prés
- Route des Prés
- Route du Col de Manse
- Route du Col de Manse
- Sabbat
- Sabbat
- Rue Carnot
- Bosquet
- Saint Jean
- Saint Jean
- Saint Louis
- Ste Marguerite
- Ste Marguerite
- Ste Marthe
- Ste Marthe
- Serre du Plan
- Services Techniques
- Bosquet
- Services Techniques
- Serviolan
- Sévigné
- Sévigné
- Soleil Levant
- Soleil Levant
- Stade
- Stade
- Stade Nautique
- Camargue
- Stade nautique
- Tavanet
- Tavanet
- Tokoro
- Tokoro
- Tokoro
- Tournefave
- Treschâtel
- Camargue
- Val du Plan
- Val du Plan
- and 96 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — up 1.1 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 68.0 | first check |
| 2026-07-30 | 68.0 | no change |
| 2026-07-31 | 67.9 | down 0.1 |
| 2026-08-01 | 69.0 | up 1.1 |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality up 5.7
What changed in this feed
Overall score rose 1.1 points since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
New since 2026-07-31 (1 finding)
- Warning256 instances
Some live predictions disagree with the schedule by more than 30 minutes.
Finding code: scorecard_rt_predictions_implausible
Changed counts
- up 6 of 13 trips scheduled during the sampling window had no live predictions. (5 → 6) (scorecard_rt_trip_coverage)
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
14 findings, ordered by severity.
Show every finding
- Warning577 instances
577 of 577 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)
- Warning343 instances
343 of 346 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)
- Warning256 instances
Some live predictions disagree with the schedule by more than 30 minutes.
Differences that large usually mean predictions are keyed to the wrong trips, not that buses are that late.
Fix: Spot-check the flagged predictions against what buses actually did; raise trip-matching with your AVL vendor. (A vendor data-mapping question.)
Finding code: scorecard_rt_predictions_implausible
- Warning77 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)
- Warning13 instances
13 of 577 trips lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning7 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
6 of 13 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)
Finding code: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning3 instances
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · 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 connecting entrances, platforms, and any elevators, with a level for each. (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)
- 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.)
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
This feed is close to the conformance mark. States wheelchair access on 1% 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 152 days.
- Accessible Not yet
- States wheelchair access on 1% 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 60 checks over the last 9 days, with 7s 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 104s late versus the schedule, and stayed within 2619s nine times in ten. They were on time (about a minute early to five late) 60.2% 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 152 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 74 / 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 37 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 84 / 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-agglo-en-bus/2026-08-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-08-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.