GTFS Scorecard
← All agencies

Feed status · checked 2026-09-01

Réseau urbain Le Vib'

Based on the official feed source on file

Service mode Bus

78.5 / 100

First scorecard for this agency

Catalogued in Centre-Val de Loire, France.

Covers 333 daysAccessibility gaps

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 4 of 4 score categories from the official feed URL on file.

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 9 snapshots.
  • 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

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

Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +24 points in its category

Fix 02

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

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

Fix 03

Re-generate shape_dist_traveled on export so stop and shape distances use the same units.Likely your export tool

On some trips the stop distances run a little past the end of the route line. The stop and shape distance values don't quite line up, so any math that uses them can drift.

⏱ Usually an export-tool fix, not hand editing.worth about +8 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
Trip distance exceeds shape distance (flagged by the MobilityData validator).
Next action
Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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. Review the rule documentation for 'trip_distance_exceeds_shape_distance' 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.

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

  3. Re-generate shape_dist_traveled on export so stop and shape distances use the same units. · 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 333 days.
Published accessibility data
Accessibility information is stated for 95% 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
Live-arrival data covered 100% 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

Correctness50.2 / 100

The MobilityData validator flagged 7 kinds of issue across 440 instances (118 error, 239 warning, 83 informational).

Freshness100.0 / 100

Service data covers the next 333 days.

Rider experience83.8 / 100

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

Accessibility59.4 / 100

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

2 accessibility depth signals

  • 4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (B, D, Vierzon - Romorantin, Ligne de Marché).

    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.

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

FaresLegacy fares

Fares are applied to trips.

Realtime quality100.0 / 100

Sampled 9 times: 3 of 3 configured feeds healthy; 100.0% of scheduled trips had live predictions; 100.0% of vehicles on their route; predictions ran a median of 5s behind schedule.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

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

  • A (purple)
  • Vierzon - Romorantin (teal)
  • Ligne de Marché (orange)
  • B (teal)
  • C (pink)
  • D (orange)
  • E (green)
  • Bourges - Vierzon (orange)
Routes in Réseau urbain Le Vib''s feed
RouteTypeLine color
A Forum - Allende - SologneBuspurple
Vierzon - RomorantinBusteal
Ligne de MarchéBusorange
B Forum - Colombier - SologneBusteal
C Brisson - Croizat - DesrochesBuspink
D Hurvoy - Villeneuve - Les CrelesBusorange
E Fernand Léger - Forum - Route de FoëcyBusgreen
Bourges - VierzonBusorange
List every stop
  • Non défini
  • Gendarmerie
  • Gay-Lussac
  • Tilleuls
  • République
  • Tilleuls
  • Port Arthur
  • Autoroute
  • Port Arthur
  • Autoroute
  • Marché
  • Gendarmerie
  • Langevin
  • Langevin
  • Gay-Lussac
  • Pyat
  • Roosevelt
  • Petite Noue
  • Roosevelt
  • Petite Noue
  • Marché
  • 19 Mars 62
  • Bruyères
  • 19 Mars 62
  • Bruyères
  • Piscine
  • Piscine
  • Croizat
  • Decour
  • Albrecht
  • Le Tacot
  • Decour
  • Albrecht
  • Fernand Léger
  • Nation
  • Aujonnière
  • Salle Collier
  • Aujonnière
  • Salle Collier
  • Croizat
  • Croix d'en Bas
  • Tunnel
  • Cimetière des Forges
  • Gagarine
  • Colombier
  • Colombier
  • Hurvoy
  • Route de Foëcy
  • Brisson
  • Etienne Dolet
  • Gagarine
  • Honoré de Balzac
  • Péraudin
  • Honoré de Balzac
  • Gourdon
  • Gourdon
  • Tunnel
  • La Croix
  • Marché au Blé
  • La Croix
  • Sellier
  • Cimetière des Forges
  • Desert
  • Pyat
  • Desert
  • La Gaillardière
  • Sologne
  • Clouseaux
  • Marché au Blé
  • Desroches
  • Mouton
  • Desroches
  • Sellier
  • Clouseaux
  • Mouton
  • Croix d'en Bas
  • Allende
  • La Gaillardière
  • Allende
  • La Bidauderie
  • La Bidauderie
  • Stade
  • Stade
  • Le Tacot
  • Les Richoux
  • Vallès
  • Hôpital
  • Les Richoux
  • Médiathèque
  • Héry
  • Médiathèque
  • Héry
  • Barbès
  • Barbès
  • Péri
  • Péri
  • Vallès
  • Villeneuve
  • Paul Eluard
  • Val Fleury
  • Val Fleury
  • Villeneuve
  • Labourbe
  • Beethoven
  • Beethoven
  • Ainset
  • Val d'Yèvre
  • Berlurettes
  • Val d'Yèvre
  • Berlurettes
  • Petites Crêles
  • Petites Crêles
  • Labourbe
  • Stalingrad
  • Stalingrad
  • Ainset
  • Pica
  • Gare des Forges
  • Gare des Forges
  • Etienne Dolet
  • Tabalou
  • Tabalou
  • Pica
  • Debournou
  • Debournou
  • Sous-Préfecture
  • Gare SNCF
  • Sous-Préfecture
  • Gare SNCF Quai C
  • Nation
  • Place Marceau
  • Place Marceau
  • Le Grelet
  • Village
  • Les Crêles
  • Village
  • Champ Bellon
  • Pont du Cher
  • Le Grelet
  • Pont du Cher
  • Village Aubry
  • Les Bourbiers
  • Les Bourbiers
  • Grands Moulins
  • Village Aubry
  • Léo Mérigot
  • Mairie
  • Labras
  • Léo Mérigot
  • Tassigny
  • Le Verdin
  • Labras
  • Le Verdin
  • La Source
  • Grands Moulins
  • Petits Moulins
  • Petits Moulins
  • Prévert
  • Sémard
  • Mairie
  • Route de Brinay
  • Brossolettes
  • Sémard
  • Hôpital
  • Forum
  • Politzer
  • 14 Juillet
  • 14 Juillet
  • Prévert
  • Paul Eluard
  • La Source
  • Champ Bellon
  • Brossolettes
  • Brisson 2
  • 19 Mars 62
  • 14 Juillet
  • A. Croizat
  • Ainset
  • Albrecht
  • Allende
  • Aujonnière
  • Autoroute
  • Barbès
  • Beethoven
  • Berlurettes
  • Brisson 1
  • Brossolettes
  • Bruyères
  • Champ Bellon
  • Cimetière des Forges
  • Clouseaux
  • Colombier
  • Croix d'en Bas
  • Debournou
  • Decour
  • Desert
  • Desroches
  • Etienne Dolet
  • Fernand Léger
  • Forum
  • Gagarine
  • Gare des Forges
  • Gare SNCF
  • Gay-Lussac
  • Gendarmerie
  • Gourdon
  • Grands Moulins
  • Héry
  • Honoré de Balzac
  • Hôpital
  • Hurvoy
  • La Bidauderie
  • La Croix
  • La Gaillardière
  • La Source
  • Labourbe
  • Labras
  • Langevin
  • Le Grelet
  • Le Tacot
  • Le Verdin
  • Léo Mérigot
  • Les Bourbiers
  • Les Crêles
  • Les Richoux
  • Mairie
  • Marché
  • Marché au Blé
  • Médiathèque
  • Mouton
  • Nation
  • Paul Eluard
  • Péraudin
  • Péri
  • Petite Noue
  • Petites Crêles
  • Petits Moulins
  • Pica
  • Piscine
  • Place Marceau
  • Politzer
  • Pont du Cher
  • Port Arthur
  • Prévert
  • Pyat
  • République
  • Roosevelt
  • Route de Brinay
  • Route de Foëcy
  • Salle Collier
  • and 31 more (see the full list on the map or in the GeoJSON)

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
  • Error118 instances

    Trip distance exceeds shape distance (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules

  • Warning333 instances

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

  • Warning200 instances

    On some trips the stop distances run a little past the end of the route line.

    The stop and shape distance values don't quite line up, so any math that uses them can drift.

    Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)

    Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules

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

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

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

    Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules

  • Warning14 instances

    14 of 281 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

  • Warning3 instances

    Route short name too long (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: route_short_name_too_long · See MobilityData GTFS Validator rules

  • 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

  • Info59 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 · See MobilityData GTFS Validator rules

  • Info24 instances

    Some trip headsigns name a stop along the way, not the final destination.

    The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.

    Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)

    Finding code: trip_headsign_matches_intermediate_stop · 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 95% 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 333 days.
Accessible Not yet
States wheelchair access on 95% 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 5 checks over the last 1 day, with 12s 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 5s late versus the schedule, and stayed within 353s nine times in ten. They were on time (about a minute early to five late) 86.3% 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 333 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 118 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 50 / 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 84 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 100 / 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.

Réseau urbain Le Vib' GTFS data quality grade: C

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