Feed status · checked 2026-07-24
Réseau urbain Agglobus — GTFS L7 ET L10
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Guyane (française), 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.
Measured 3 of 4 score categories from the agency's own feed.
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 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
Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Stop time with arrival before previous departure time (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
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
191 of 191 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
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.
Review the rule documentation for 'duplicate_key' 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.
Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' 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.
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.
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 160 days.
- Published accessibility data
- Accessibility information is stated for 0% 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
- 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.
Score by category
The MobilityData validator flagged 11 kinds of issue across 2230 instances (3 error, 2154 warning, 73 informational).
Service data covers the next 160 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Ligne 7, Ligne 10).
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 ("ECOLE ST MICHEL", "ECOLE ST MICHEL", "ECOLE ST MICHEL", 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.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- Ligne 7 (brown)
- Ligne 10 (pink)
| Route | Type | Line color |
|---|---|---|
| Ligne 7 Aéroport F. Eboué / Gare Routière | Bus | brown |
| Ligne 10 Matoury / Lycée L.G. Damas | Bus | pink |
This feed has 191 stops.
List every stop
- Ecole Barbadine
- Ecole Barbadine
- Family Plaza
- Family Plaza
- Ecole Saint Michel
- Ecole Saint Michel
- Stade Municipal
- Stade Municipal
- Balata
- Balata
- Balata
- Kalina
- Kalina
- Kalina
- Jasmen Kayenn
- Jasmen Kayenn
- Jasmen Kayenn
- Terca
- Terca
- Terca
- Caf de Guyane
- Caf de Guyane
- Caf de Guyane
- Cayenne - Gare Routière
- Cayenne - Gare Routière
- Cayenne - Gare Routière
- Barbadine 2
- Barbadine 2
- Barbadine 2
- Collège Canopée
- Collège Canopée
- Collège La Canopée
- Collège Saint Pierre
- Collège Saint Pierre
- Collège Saint Pierre
- Eglise de Matoury
- Eglise de Matoury
- Eglise de Matoury
- Rue de la Canneraie
- Rue de la Canneraie
- Rue de la Canneraie
- La Rhumerie
- La Rhumerie
- La Rhumerie
- Centre Commercial Makoupy
- Centre Commercial Makoupy
- CC Makoupy
- Wang
- Wang
- Wang
- Mairie de Matoury
- Mairie de Matoury
- Mairie de Matoury
- PROGT
- PROGT
- Ranch
- Ranch
- Ranch
- Moucayas
- Moucayas
- Moucayas
- Ronds-Points Cogneau
- Ronds-Points Cogneau
- Ronds-Points Cogneau Sud
- Rue des Cotonniers
- Rue des Cotonniers
- Rue des Cotonniers
- Korosol
- Korosol
- Korosol
- Vénéré
- Vénéré
- Vénéré
- Barbadine 1
- Family Plaza
- Saint Michel
- Aéroport Félix Éboué
- Aéroport Félix Éboué
- CC Beauregard
- CC Beauregard
- RN2 - Califourchon
- RN2 - Califourchon
- CONCORDE LABRANCHE
- CONCORDE LABRANCHE
- CONCORDE LABRANCHE
- CONCORDE LABRANCHE
- CENTRE DE TRI EKOTRI
- CENTRE DE TRI EKOTRI
- CENTRE DE TRI EKOTRI
- CENTRE DE TRI EKOTRI
- LOT. FUSHIA
- LOT. FUSHIA
- LOT. FUSHIA
- LOT. FUSHIA
- RN2 - La Désirée
- RN2 - La Désirée
- CITE CONCORDE
- CITE CONCORDE
- CITE CONCORDE
- CITE CONCORDE
- CONCORDE GR SCOL
- CONCORDE GR SCOL
- CONCORDE GR SCOL
- CONCORDE GR SCOL
- LYCEE LEON GONTRAN DAMAS
- LYCEE LEON GONTRAN DAMAS
- CONCORDE
- CONCORDE
- CONCORDE
- CONCORDE
- CHEMIN MORTIUM 1
- CHEMIN MORTIUM 1
- CHEMIN MORTIUM 1
- CHEMIN MORTIUM 1
- CHEMIN MORTIUM 2
- CHEMIN MORTIUM 2
- CHEMIN MORTIUM 2
- CHEMIN MORTIUM 2
- CHEMIN MORTIUM 3
- CHEMIN MORTIUM 3
- CHEMIN MORTIUM 3
- CHEMIN MORTIUM 3
- CENTRE PENITENTIAIRE1
- CENTRE PENITENTIAIRE1
- CENTRE PENITENTIAIRE2
- CENTRE PENITENTIAIRE2
- CENTRE PENITENTIAIRE3
- CENTRE PENITENTIAIRE3
- LE RANCH MATOURIENNE
- LE RANCH MATOURIENNE
- LE RANCH MATOURIENNE
- LE RANCH MATOURIENNE
- LA RHUMERIE
- LA RHUMERIE
- LA RHUMERIE
- LA RHUMERIE
- SERVAIR
- SERVAIR
- SERVAIR
- SERVAIR
- SERVAIR
- SERVAIR
- STADE MUNICIPAL DE MATOURY
- STADE MUNICIPAL DE MATOURY
- STADE MUNICIPAL DE MATOURY
- STADE MUNICIPAL DE MATOURY
- STADE EDMARD LAMA
- STADE EDMARD LAMA
- STADE EDMARD LAMA
- STADE EDMARD LAMA
- ECOLE ST MICHEL
- ECOLE ST MICHEL
- ECOLE ST MICHEL
- ECOLE ST MICHEL
- Stade de Matoury
- Ronds-Points Cogneau Nord
- Aéroport F. EBOUE
- CC Beauregard
- RN2 - Califourchon
- Concorde Labranche
- Concorde Labranche
- Lot. Fushia
- Lot. Fushia
- RN2 - La Désirée
- Concorde Saint-Exupéry
- Concorde Saint-Exupéry
- Concorde ZAC
- Concorde ZAC
- Lycée Léon Gontran DAMAS
- Concorde Malidor
- Concorde Malidor
- Chemin Mortium 1
- Chemin Mortium 1
- Chemin Mortium 2
- Chemin Mortium 2
- Chemin Mortium 3
- Chemin Mortium 3
- Caserne de Remire-Montjoly
- Centre pénitentiaire
- Le Ranch
- Le Ranch
- La Rhumerie
- La Rhumerie
- Servair
- Servair
- Stade de Matoury
- Stade de Matoury
- Stade Edmard LAMA
- Stade Edmard LAMA
- Saint Michel
- Saint Michel
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
18 findings, ordered by severity.
Show every finding
- Error2 instances
Duplicate key (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: duplicate_key · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Stop time with arrival before previous departure time (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: stop_time_with_arrival_before_previous_departure_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1800 instances
Some internal IDs use characters outside the basic text set.
These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)
Validator rule: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning249 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)
- Warning191 instances
191 of 191 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)
- Warning189 instances
189 of 189 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)
- Warning100 instances
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Validator rule: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 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)
- 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
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.)
Validator rule: stops_match_shape_out_of_order · 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)
- 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.)
Validator rule: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info72 instances
About 72 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Validator rule: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info70 instances
Unused station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unused_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: unused_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 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
Unsorted stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: unsorted_stop_times · 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. 2 validator errors to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Met
- Service data covers the next 160 days.
- Accessible Not yet
- States wheelchair access on 0% 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.
- 3 of 61 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 160 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 3 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 38 / 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 32 / 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.
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-pan-83304/2026-07-24.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-24. 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.