GTFS Scorecard
← All agencies

Feed status · checked 2026-09-01

Réseau urbain TUB (Bergerac)

Based on the official feed source on file

Service mode Bus

62.5 / 100

First scorecard for this agency

Catalogued in Nouvelle-Aquitaine, France.

Covers 121 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.3, validator 8.0.1.

Checked for changes 1 hours ago; last changed 1 hours 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.

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

Fix 02

Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool

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.

⏱ Two fields, set once in export settings.worth about +15 points in its category

Fix 03

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.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

⏱ A small file for most flat-fare systems.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
Some trips have stop times whose distances along the route go backwards.
Next action
Re-generate shape distances in your export; flag to your vendor if it persists.
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. 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. Add feed_info.txt with feed_start_date and feed_end_date to your export. · 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. 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. · 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 121 days.
Published accessibility data
Accessibility information is stated for 97.8% of stops and 9.2% 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

Correctness59.0 / 100

The MobilityData validator flagged 6 kinds of issue across 271 instances (48 error, 158 warning, 65 informational).

Freshness85.0 / 100

Service data covers the next 121 days.

Rider experience49.3 / 100

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

Accessibility64.6 / 100

98% of stops state accessibility (0% 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 (L2).

    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 ("AV A.BRIAND", "AV A.BRIAND", "AV A.BRIAND (Loupias)", 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.

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

  • L3 (yellow)
  • L1 (white)
  • L2 (red)
  • NAV (orange)
Routes in Réseau urbain TUB (Bergerac)'s feed
RouteTypeLine color
L3 LIGNE 3Busyellow
L1 POLE MULTIMODAL<>CENTRE VILLE<> Z.A LA CAVAILLEBuswhite
L2 POLE MULTIMODAL<>CENTRE VILLE ><3 VALLEESBusred
NAV NAVETTE COEUR DE VILLEBusorange
List every stop
  • RUE DU PARC
  • PRIGONRIEUX EGLISE A
  • GARE SNCF
  • PLACE DE LA MAIRIE
  • PRIGONRIEUX EGLISE R
  • TIBERIADE
  • ESPACE FRANCOIS MITTERAND D 933 3
  • MAISON DE SANTE BERGERAC EST
  • M.BARRAT
  • SAID ESCOLLA
  • SAID ESCOLLA
  • PAUL PAINLEVE
  • LA CAVAILLE
  • POLE EMPLOI
  • CHATEAUBRIAND A
  • RTE DE BORDEAUX R
  • CHATEAUBRIAND R
  • RTE DE BORDEAUX A
  • MAIRIE
  • LA BEYLIVE LOTISSEMENT 1
  • LA BEYLIVE LOTISSEMENT 2
  • ESPACE FRANCOIS MITTERAND 1
  • ESPACE FRANCOIS MITTERAND 2
  • REPUBLIQUE
  • CROZES A
  • JULES FERRY
  • JULES FERRY
  • CROZES R
  • LA MADELEINE G.CLEMENCEAU
  • PLACE DE LATTRE DE TASSIGNY
  • LES SARDINES
  • LA MADELEINE BERGREEN
  • QUAI SALVETTE
  • LES MAURIGOUX
  • LES MAURIGOUX
  • JEAN CAPELLE
  • JEAN CAPELLE
  • RTE DU COMBAL
  • RTE DU COMBAL
  • POLE MULTIMODAL SNCF
  • POLE EMPLOI
  • VALLADE SUD
  • LE TOUNET
  • GENERAL DE GAULLE R
  • LE TOUNET
  • GENERAL DE GAULLE A
  • H.DUC
  • 3 VALLEES
  • BD CLAVEILLE 2
  • BD CLAVEILLE1
  • JARDIN PERDOUX
  • HOPITAL 1
  • HOPITAL 2
  • GRANDS DUCS
  • GRANDS DUCS 2
  • LES CARMES
  • RENE DESMAISON
  • ALBA
  • ANDRE MAUROIS
  • BELLEGARDE
  • ANATOLE FRANCE D
  • FOIRAIL 1
  • FOIRAIL 2
  • PLACE DE L'EUROPE
  • GUILBAUD
  • AV A.BRIAND (pharmacie)
  • JEAN MOULIN
  • Anatole France A
  • AV A.BRIAND (Loupias)
  • BD BEAUSOLEIL
  • ESPACE J LAGABRIELLE
  • MARCHE (place de Lattre)
  • LR BERGERAC-Jardin Perdoux (2)
  • LR BERGERAC-Place du Foirail (2)
  • LR BERGERAC-Lyc. Prof. Capelle (2)
  • SAID ESCOLLA
  • PAUL PAINLEVE
  • LA CAVAILLE
  • POLE EMPLOI
  • CHATEAUBRIAND A
  • RTE DE BORDEAUX R
  • CHATEAUBRIAND R
  • RTE DE BORDEAUX A
  • MAIRIE
  • LA BEYLIVE LOTISSEMENT 1
  • LA BEYLIVE LOTISSEMENT 2
  • ESPACE FRANCOIS MITTERAND 1
  • ESPACE FRANCOIS MITTERAND 2
  • REPUBLIQUE
  • CROZES A
  • JULES FERRY
  • CROZES R
  • LA MADELEINE G.CLEMENCEAU
  • PLACE DE LATTRE DE TASSIGNY
  • LES SARDINES
  • LA MADELEINE BERGREEN
  • QUAI SALVETTE
  • LES MAURIGOUX
  • RTE DU COMBAL
  • POLE MULTIMODAL SNCF
  • POLE EMPLOI
  • VALLADE SUD
  • GENERAL DE GAULLE R
  • LE TOUNET
  • GENERAL DE GAULLE A
  • 3 VALLEES
  • BD CLAVEILLE 2
  • BD CLAVEILLE1
  • HOPITAL 1
  • HOPITAL 2
  • GRANDS DUCS
  • GRANDS DUCS 2
  • LES CARMES
  • RENE DESMAISON
  • ALBA
  • ANDRE MAUROIS
  • BELLEGARDE
  • ANATOLE FRANCE D
  • PLACE DE L'EUROPE
  • GUILBAUD
  • AV A.BRIAND
  • JEAN MOULIN
  • Anatole France A
  • AV A.BRIAND
  • BD BEAUSOLEIL
  • ESPACE J LAGABRIELLE
  • MARCHE
  • LR BERGERAC-Lyc. Métiers H. Duc (2)
  • RUE DU PARC
  • PRIGONRIEUX EGLISE A
  • GARE SNCF
  • PLACE DE LA MAIRIE
  • PRIGONRIEUX EGLISE R
  • TIBERIADE
  • ESPACE FRANCOIS MITTERAND D 933 3
  • MAISON DE SANTE BERGERAC EST
  • M.BARRAT

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

13 findings, ordered by severity.

Show every finding
  • Error48 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.)

    Finding code: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules

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

  • Warning59 instances

    59 of 65 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

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

    Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules

  • Warning3 instances

    3 of 137 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

  • 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

  • Warning1 instance

    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

  • 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

  • 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

  • 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

  • Info128 instances

    About 128 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.)

    Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices

  • Info65 instances

    Trip with shape dist traveled but no shape distances (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'trip_with_shape_dist_traveled_but_no_shape_distances' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: trip_with_shape_dist_traveled_but_no_shape_distances · See MobilityData GTFS Validator rules

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.

    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

Conformance mark Not yet

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

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 121 days.
Accessible Not yet
States wheelchair access on 98% of stops and 9% 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 121 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 48 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 59 / 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 49 / 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 TUB (Bergerac) GTFS data quality grade: D

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