GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Ritmo (Haguenau)

Based on the feed this agency publishes

Service mode Bus

50.8 / 100

First scorecard for this agency

Catalogued in Grand-Est, France.

Covers 43 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

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

Invalid url (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +12 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

462 of 533 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 +22 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

1247 of 1247 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. Review the rule documentation for 'invalid_url' 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_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 43 days.
Published accessibility data
Accessibility information is stated for 13.3% 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.2 / 100

The MobilityData validator flagged 8 kinds of issue across 2672 instances (1 error, 2652 warning, 19 informational).

Freshness71.7 / 100

Service data covers the next 43 days.

Rider experience33.3 / 100

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

Accessibility8.3 / 100

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

3 accessibility depth signals

  • 5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (05, 13, 11, 02, 04).

    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.

  • 13 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Les Pins / Caire", "Les Pins / Caire", "Gare de Haguenau / Moulin Neuf", 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.

Skip to route and stop data

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

  • 05 (green)
  • 13 (green)
  • 01 (red)
  • 11 (blue)
  • 03 (yellow)
  • 12 (pink)
  • 02 (teal)
  • 10 (orange)
  • 04 (purple)
Routes in Ritmo (Haguenau)'s feed
RouteTypeLine color
05 Zone Com. Sud <> Gare de Mom.Busgreen
13 Gare Hag. / M.N. <> Gare Mommen.Busgreen
01 Sch. Rosenberg <> B. HanhoffenBusred
11 Gare Hag. <> Pfaffenhoff. MairieBusblue
03 Chemin du Parcage <> HôpitalBusyellow
12 Gare Bru. <> Pfaffenhoff. MairieBuspink
02 Les Pins/Caire <> C. EquestreBusteal
10 Gare Hag. / M.N. <> Gare BrumathBusorange
04 Gare Hag. <> Gare BischwillerBuspurple

This feed has 533 stops.

List every stop
  • Rue des Souris
  • Complexe de loisirs
  • College Kléber
  • Rue du chevreuil
  • Huttendorf Route de Brumath
  • Monument aux morts
  • Mairie
  • Chemin des Friches
  • Wintershouse Mairie
  • ZA Industrie
  • Berstheim Eglise
  • Thurot
  • Wittersheim Centre
  • Gebolsheim Centre
  • Londres
  • Orge
  • Palais de Justice
  • Rosenfeld
  • Dauendorf Espace Concordia
  • Bruxelles
  • Oslo
  • Allée Bumb
  • Saint Exupery
  • PFAFFENHOFEN - Gare
  • RINGELDORF - Centre
  • Cimetieres
  • Bischwiller Hanhoffen
  • Lycée Goulden
  • Bischwiller Mairie
  • Brumath Collège
  • Zone Commerciale Nord
  • Bugatti
  • Charmille
  • Eliane Traband
  • Rue des Roses
  • Roses
  • Foch
  • Commerce
  • Oberhoffen Mairie
  • Ohlungen Eglise
  • La Walck Monument Aux Morts
  • Z.I. Schweighouse
  • Haguenau - Moulin Neuf Gare
  • BERNOLSHEIM Centre
  • Ohlungen Rue du Sapin
  • Weinumshof
  • Taubenhof Kestlerhof
  • La Walck Ecoles
  • De Gaulle
  • Batzendorf Centre
  • Batzendorf Pharmacie
  • Centre Hospitalier Bischwiller
  • Bellevue / Chateau
  • Bellevue/Romains
  • Gare de Stephansfeld
  • Ours Blanc
  • Pont de la Zorn
  • Rue du Général Duport
  • Rue du Général Rampont
  • Scierie
  • Waldgraben
  • Zone Commerciale Sud
  • Ancienne Douane
  • Anita Conti
  • Château Fiat
  • Cité Scolaire
  • Harthouse
  • Hôpital
  • Berstheim giratoire
  • Crémaillere
  • Rue de Marienthal
  • De Gaulle
  • Mommenheim Alpes
  • Rue de la Foret
  • Tulipes
  • Crocus
  • Ohlungen Sandbuehl
  • La Walck Rue de Bitschhoffen
  • Uberach Centre
  • Uberach Cité
  • Roseliere
  • Schweitzer
  • Rue Principale
  • Wintershouse Eglise
  • Chemin du Parcage
  • Heimelsberg
  • Saint-Materne
  • Rond Point de Landau
  • Quartier Frere
  • Lezay Marnésia
  • Foulon
  • Leriche
  • Voituriers
  • Rue des Cigales
  • Missions Africaines
  • Mathis
  • Place Schuman
  • Marché aux Grains
  • Garance
  • Hannong
  • Allée des Cerisiers
  • Platanes
  • Centre de Dédouanement
  • Truttmann
  • Boulevard Pasteur
  • Rue des Moines
  • Centre de Secours Principal
  • Acacias
  • Clos des Prés
  • Schaeffler
  • Zone Commerciale Schweighouse
  • Papeterie
  • Mairie de Schweighouse
  • Villa
  • Aérodrome
  • Barberousse
  • Bellevue
  • Burlenfeld
  • Centre Equestre
  • Ecole Bildstoeckel
  • Ferme Oberlin
  • Halle aux Houblons
  • Lerchenberg
  • Les Pins / Caire
  • Pont de Strasbourg
  • Route de Weitbruch
  • Rue des Fourmis
  • Saint Joseph
  • Sandlach
  • Taubenhof Caserne
  • Taubenhof Centre Commercial
  • Breitung
  • Cité Franck
  • Ecoles
  • Maréchal Leclerc
  • Socrate
  • PFAFFENHOFEN - Mairie
  • Hôtel de Ville
  • Eglise
  • Liberté
  • Lycée André Maurois
  • Sonnenhof
  • Cigognes/Schuman
  • Dauendorf Mairie
  • Grassendorf RD 419
  • Branly
  • Ferme Roehri
  • Fougeres
  • Pélerins
  • Porte de Wissembourg
  • Route de Winterhouse
  • Veramont
  • Rue de Bischwiller
  • Niedermodern Cité Leopold
  • Les Trois Tilleuls
  • Quartier Estienne
  • Caserne des Pompiers
  • Gare de Schweighouse
  • Rochette
  • Wittersheim Stade
  • Médiatheque
  • Kapsmatt
  • Schweighouse Rosenberg
  • De Gaulle
  • Sabliere
  • Rue des Vélos
  • Centre Culturel
  • Hochstett rue de Pfaffenhoffen
  • Mairie
  • Couronne
  • Gare de Bischwiller
  • Champs
  • Statuette
  • Route de Woerth
  • Eisenbruch
  • Montserrat
  • Vestra
  • Eglise
  • Brumath
  • Gare de Haguenau
  • Gare de Marienthal
  • Marienthal - Basilique
  • Gare de Mommenheim
  • Niedermodern Pont de la Moder
  • Eglise Protestante
  • Wittersheim Stade
  • Dauendorf Mairie
  • Route de Winterhouse
  • Porte de Wissembourg
  • Liberté
  • Eglise
  • Acacias
  • Rue de Bischwiller
  • Bellevue/Romains
  • College Kléber
  • Sonnenhof
  • Cité Franck
  • Eglise
  • Barberousse
  • Weinumshof
  • Weinumshof
  • Anita Conti
  • Ferme Roehri
  • Centre Hospitalier Bischwiller
  • Berstheim giratoire
  • Pélerins
  • Rochette
  • Niedermodern Cité Leopold
  • Wittersheim Centre
  • Hôpital
  • Taubenhof Centre Commercial
  • Liberté
  • Rochette
  • Pont de la Zorn
  • Fougeres
  • Grassendorf RD 419
  • Hochstett rue de Pfaffenhoffen
  • Caserne des Pompiers
  • Commerce
  • Aérodrome
  • Gare de Marienthal
  • Quartier Estienne
  • Les Trois Tilleuls
  • Grassendorf RD 419
  • Quartier Frere
  • Wittersheim Stade
  • Allée Bumb
  • Cigognes/Schuman
  • Lycée André Maurois
  • Gare de Schweighouse
  • Gare de Marienthal
  • Kriegsheim Centre
  • Dauendorf Mairie
  • Boulevard Pasteur
  • Veramont
  • Lycée André Maurois
  • Clos des Prés
  • Rue des Cigales
  • Route de Winterhouse
  • Sabliere
  • Eisenbruch
  • Médiatheque
  • Chemin des Friches
  • Hochstett rue de Pfaffenhoffen
  • Route de Weitbruch
  • Voituriers
  • Centre Equestre
  • Rue des Moines
  • Montserrat
  • Allée des Cerisiers
  • and 283 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

14 findings, ordered by severity.

Show every finding
  • Error1 instance

    Invalid url (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: invalid_url · See MobilityData GTFS Validator rules

  • Warning1247 instances

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

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

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

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

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

  • Warning462 instances

    462 of 533 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

  • Warning5 instances

    Some service calendars in the feed have already ended.

    Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

    Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)

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

  • Warning2 instances

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

    Validator rule: route_color_contrast · 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

  • Warning1 instance

    agency.txt has no working website URL.

    Trip planners link riders to this URL for schedules and fares.

    Fix: Set agency_url to your agency's website, starting with https://. (One field.)

    Validator rule: scorecard_bad_agency_url

  • 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

  • Info19 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 13% 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 43 days.
Accessible Not yet
States wheelchair access on 13% 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 43 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 1 validator error, 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 51 / 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 72 / 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 33 / 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.

Ritmo (Haguenau) 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/ritmo-haguenau/2026-07-19.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-19. 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.