GTFS Scorecard
← All agencies

Feed status · checked 2026-07-24

Réseau urbain Duobus

Based on the feed this agency publishes

Service mode Bus

59.2 / 100

First scorecard for this agency

Catalogued in Auvergne-Rhône-Alpes, France.

Covers 525 daysAccessibility gapsRealtime not yet published

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

Fix 01

Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool

Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.

⏱ Usually an export-tool fix, not hand editing.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

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

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

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. Re-generate shape distances in your export; flag to your vendor if it persists.

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

Correctness51.5 / 100

The MobilityData validator flagged 6 kinds of issue across 418 instances (172 error, 244 warning, 2 informational).

Freshness100.0 / 100

Service data covers the next 525 days.

Rider experience37.5 / 100

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.

Accessibility0 / 100

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

1 accessibility depth signal

  • 5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (L2, L3, L3A, L3B, L4).

    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.

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.

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.

Skip to route and stop data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • L1 (red)
  • L2B (purple)
  • L2 (orange)
  • L3A (green)
  • L3B (green)
  • L3 (green)
  • L4 (teal)
  • ZIO (purple)
Routes in Réseau urbain Duobus's feed
RouteTypeLine color
L1 Ligne 1 Arbent <> Gare SNCF <> Bellignat <> MartignatBusred
L2B Ligne 2 B Gare SNCF <> Veyziat <> GéovreissetBuspurple
L2 Ligne 2 Gare SNCF <> OrmeBusorange
L3A Gare SNCF <> Point B <> ArbentBusgreen
L3B Gare SNCF <> Point B <> DortanBusgreen
L3 Ligne 3 Gare SNCF <> Point BBusgreen
L4 Ligne 4 Gare SNCF <> GeillesBusteal
ZIO Ligne ZIO Gare SNCF <> Zone Industrielle OuestBuspurple

This feed has 145 stops.

List every stop
  • 1er Mai Est
  • 1er Mai Est
  • 1er Mai Ouest
  • 1er Mai Ouest
  • Cimetière
  • Mairie
  • Scieries
  • Epinettes
  • Epinettes
  • Espace Loisirs
  • Espace Loisirs
  • Ferme Richard
  • Ferme Richard
  • Fullus
  • Fullus
  • Marchon
  • Marchon
  • Planet
  • Planet
  • Point B
  • pôle santé
  • Ravel
  • Ravel
  • Rostand
  • Rostand
  • ZINord
  • ZINord
  • Arbez Carme
  • Arbez Carme
  • Arcades
  • Arcades
  • Bellignat
  • Mairie
  • Guynemer
  • Lange
  • Lange
  • Les Prés
  • Les Prés
  • Les Merciers
  • Les Merciers
  • Montains
  • Simone veil
  • Simone veil
  • ZISud
  • ZISud
  • Cité
  • HLM
  • HLM
  • Mairie
  • Mairie
  • Cimetière Géovreisset
  • Lavoir
  • Mairie Géovreisset
  • le parc
  • Eglise
  • Eglise
  • Mairie
  • Mairie
  • PI du Marais
  • PI du Marais
  • Lavoir
  • Lavoir
  • Mairie
  • 4 Ponts
  • 4 Ponts
  • 5 Passages
  • Route Arfontaine
  • Route Arfontaine
  • Braconnais
  • Brillat Savarin
  • Burgondes
  • Burgondes
  • Chambourg
  • Chambourg
  • Chevret
  • Chevret
  • Cité Administrative
  • Clémenceau
  • Alice Millat
  • Alice Millat
  • De Lattre
  • De Lattre
  • Déportés
  • Diderot
  • Diderot
  • Dupont
  • Edf
  • Eglisette
  • Eglisette
  • Ferrié
  • Gagarine
  • Gare SNCF
  • Gare SNCF
  • Geilles carrefour d'Apremont
  • Geilles centre
  • Geilles centre
  • Geilles école
  • Geilles école
  • Geilles
  • Rosa Bonheur
  • Grand Moulin
  • Grand Moulin
  • Hôtel de Ville
  • Hôpital
  • Jeanne d'Arc
  • Jeanne d'Arc
  • Jean Moulin
  • Kennedy
  • La Croix
  • La Croix
  • La Forge
  • La Forge
  • Michelet
  • Michelet
  • Narvick
  • Narvick
  • Notre Dame
  • Notre Dame
  • Nicod
  • Nicod
  • Orme
  • Irène Claire
  • Irène Claire
  • ienne
  • Pascal
  • Parc Industriel Ouest
  • Rochaix
  • Rochaix
  • Irène clair
  • Irène clair
  • Rousseau
  • Rousseau
  • Romans Petit
  • Schuman
  • Square Meneault
  • Saint Exupéry
  • Sully
  • Sully
  • Foyer Verchère
  • Vey
  • Vey
  • Victor Hugo
  • ZIOuest
  • ZIOuest
  • Zi Veyziat

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

10 findings, ordered by severity.

Show every finding
  • Error172 instances

    Some trips have stop times whose distances along the route go backwards.

    Apps can show buses jumping backwards or mis-order stops.

    Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)

    Validator rule: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules

  • Warning225 instances

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

  • Warning180 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.)

    Validator rule: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning145 instances

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

  • Warning59 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.)

    Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules

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

  • Warning1 instance

    feed_info.txt lists no contact email and no contact URL.

    Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

    Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)

    Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

  • 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

  • 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

Conformance mark Not yet

This feed is close to the conformance mark. 1 validator error to resolve. States wheelchair access on 0% 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 525 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.

Clears the Google and Apple Maps four-week coverage bar. This feed has 525 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 172 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 52 / 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 38 / 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.

Réseau urbain Duobus GTFS data quality grade: F

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