GTFS Scorecard
← All agencies

Feed status · checked 2026-07-23

Réseau urbain Riv'Connect

Based on the feed this agency publishes

Service mode Bus

80.4 / 100

First scorecard for this agency

Catalogued in Grand-Est, France.

Covers 161 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.2, validator 8.0.1.

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

Fix 01

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

110 of 110 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 02

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

Fix 03

Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool

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.

⏱ Often a bulk fix in your scheduling software.worth about +8 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. 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.

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

  3. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · 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 161 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 100% 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
One or more realtime feeds were reachable; live-arrival coverage is not known.

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

Correctness88.0 / 100

The MobilityData validator flagged 2 kinds of issue across 170 instances (0 error, 170 warning, 0 informational).

Freshness100.0 / 100

Service data covers the next 161 days.

Rider experience38.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.

Accessibility37.5 / 100

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

2 accessibility depth signals

  • 2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 2).

    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.

Realtime quality100.0 / 100

Sampled 3 times outside service hours: 1 of 1 configured feed healthy; predictions ran a median of 5s behind schedule.

Routes and stops

This feed has no route shapes, so the map shows its stops only.

Skip to route and stop data

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

Routes in Réseau urbain Riv'Connect's feed
RouteTypeLine color
1 Ligne 1 Hagondange - EurotransitBusteal (no shape in feed)
2 Ligne 2 Maizieres Gare - EnneryBusyellow (no shape in feed)
3 Ligne 3 Maizieres - TalangeBusteal (no shape in feed)
4 Ligne 4 Maizieres - EcoparcBusteal (no shape in feed)

This feed has 110 stops.

List every stop
  • HAUCONCOURT - CENTRE COMMERCIAL
  • MAIZIERES-LES-METZ - COLONIES
  • ZI DU MALAMBAS - CANAL
  • ZI DU MALAMBAS - NORD
  • ZI DU MALAMBAS - SUD
  • ECOPARC - 1
  • EUROTRANSIT - ANDRE AMPERE
  • HAUCONCOURT - Centre
  • MAIZIERES-LES-METZ - VAL MAIDERA
  • ECOPARC - 2
  • ECOPARC - 3
  • NORROY-LE-VENEUR - EUROMOSELLE SUD
  • TALANGE - MARQUES AVENUE
  • LES JONQUIERES 3
  • LES JONQUIERES 4
  • AY - VILLAGE
  • STELLANTIS
  • ENNERY - BELLE CROIX
  • ENNERY - CARREFOUR MARKET
  • EUROTRANSIT - ANDRE MAGINOT
  • EUROTRANSIT - GEORGES CLAUDE
  • EUROTRANSIT - MARCEL DASSAULT
  • LES JONQUIERES 1
  • LES JONQUIERES 2
  • SEMECOURT - LA CROIX BLAISE
  • EUROTRANSIT - ANDRE MAGINOT
  • EUROTRANSIT - GUSTAVE EIFFEL
  • HAGONDANGE - GARE ARAGON
  • HAUCONCOURT - GRANDE RAYEE 1
  • HAUCONCOURT - GRANDE RAYEE 2
  • TALANGE - PRE LE LOUP 1
  • TALANGE - PRE LE LOUP 2
  • ARCELORMITTAL
  • MAIZIERES-LES-METZ - GARE OUEST
  • Maizieres les METZ Clinique Sud
  • ECOPARC - 4
  • NORROY-LE-VENEUR - GRAND PRE
  • ARCELORMITTAL
  • SEMECOURT - CENTRE COMMERCIAL
  • TALANGE-LYCEE EIFFEL
  • EUROTRANSIT - DENIS PAPIN
  • FEVES - Croix Blaise
  • HAGONDANGE - Parc Municipal
  • ECOPARC - BELLEVUE
  • SEMECOURT - Hypermarche
  • HAUCONCOURT - EST
  • Gare de Maizières-lès-Metz
  • AY - VILLAGE
  • AY - VILLAGE
  • ENNERY - CARREFOUR MARKET
  • ENNERY - BELLE CROIX
  • ENNERY - BELLE CROIX
  • LES JONQUIERES 1
  • LES JONQUIERES 2
  • LES JONQUIERES 3
  • LES JONQUIERES 4
  • EUROTRANSIT - ANDRE AMPERE
  • EUROTRANSIT - ANDRE AMPERE
  • EUROTRANSIT - ANDRE MAGINOT
  • EUROTRANSIT - ANDRE MAGINOT
  • EUROTRANSIT - DENIS PAPIN
  • EUROTRANSIT - GEORGES CLAUDE
  • EUROTRANSIT - GEORGES CLAUDE
  • EUROTRANSIT - GUSTAVE EIFFEL
  • EUROTRANSIT - GUSTAVE EIFFEL
  • EUROTRANSIT - MARCEL DASSAULT
  • EUROTRANSIT - MARCEL DASSAULT
  • HAGONDANGE - GARE ARAGON
  • HAGONDANGE - PARC MUNICIPAL
  • HAGONDANGE - PARC MUNICIPAL
  • ZI DU MALAMBAS - CANAL
  • HAUCONCOURT - CENTRE COMMERCIAL
  • HAUCONCOURT - CENTRE COMMERCIAL
  • HAUCONCOURT - CENTRE
  • HAUCONCOURT - CENTRE
  • HAUCONCOURT - EST
  • HAUCONCOURT - EST
  • HAUCONCOURT - GRANDE RAYEE 1
  • HAUCONCOURT - GRANDE RAYEE 2
  • TALANGE - MARQUES AVENUE
  • ZI DU MALAMBAS - NORD
  • TALANGE - PRE LE LOUP 1
  • TALANGE - PRE LE LOUP 2
  • ZI DU MALAMBAS - SUD
  • ARCELORMITTAL
  • ARCELORMITTAL
  • Maizieres les METZ Clinique Sud
  • MAIZIERES-LES-METZ - COLONIES
  • MAIZIERES-LES-METZ - COLONIES
  • MAIZIERES-LES-METZ - GARE PARVIS
  • MAIZIERES-LES-METZ - GARE OUEST
  • MAIZIERES-LES-METZ - VAL MAIDERA
  • MAIZIERES-LES-METZ - VAL MAIDERA
  • ECOPARC - 1
  • ECOPARC - 2
  • ECOPARC - 3
  • ECOPARC - 4
  • ECOPARC - BELLEVUE
  • ECOPARC - BELLEVUE
  • NORROY-LE-VENEUR - EUROMOSELLE SUD
  • NORROY-LE-VENEUR - EUROMOSELLE SUD
  • NORROY-LE-VENEUR - GRAND PRE
  • NORROY-LE-VENEUR - GRAND PRE
  • SEMECOURT - LA CROIX BLAISE
  • SEMECOURT - LA CROIX BLAISE
  • SEMECOURT - CENTRE COMMERCIAL
  • SEMECOURT - CENTRE COMMERCIAL 2
  • TALANGE-LYCEE EIFFEL
  • TALANGE-LYCEE EIFFEL
  • STELLANTIS

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

7 findings, ordered by severity.

Show every finding
  • Warning169 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

  • Warning110 instances

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

  • 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

  • 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

  • Info103 instances

    About 103 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

  • 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. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 161 days.
Accessible Not yet
States wheelchair access on 0% of stops and 100% 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 1 checks, with 44s 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 235s nine times in ten. They were on time (about a minute early to five late) 80.0% of the time.

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 160 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 88 / 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 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 Riv'Connect GTFS data quality grade: B

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-riv-connect/2026-07-23.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-23. 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.