GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

TRACE (Colmar)

Based on the feed this agency publishes

Service mode Bus

45.5 / 100

First scorecard for this agency

Catalogued in Grand-Est, France.

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

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

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

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

Correctness36.0 / 100

The MobilityData validator flagged 9 kinds of issue across 2715 instances (108 error, 2607 warning, 0 informational).

Freshness70.0 / 100

Service data covers the next 42 days.

Rider experience39.2 / 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.

3 accessibility depth signals

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

    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.

  • 17 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("ST JOSEPH GARE", "ST JOSEPH GARE", "QUAI DR PFLEGER", 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.

  • L CV (brown)
  • G (teal)
  • B (teal)
  • A (red)
  • C (yellow)
  • D (green)
  • E (pink)
  • F (orange)
Routes in TRACE (Colmar)'s feed
RouteTypeLine color
L CV NCV Bleylé (gare) – Centre-VilleBusbrown
G Colmar – WalbachBusteal
B Wintzenheim – HoussenBusteal
A Sundhoffen – Ingersheim / TurckheimBusred
C Turckheim – Ste-Croix-en-PlaineBusyellow
D Europe – ZI Nord / AéroportBusgreen
E Colmar Brant – FortschwihrBuspink
F Mittelharth – Erlen RicohBusorange

This feed has 498 stops.

List every stop
  • HORBOURG-WIHR - Vignoble
  • VIEUX MUHLBACH
  • PL GAL DE GAULLE
  • Rue de la Mairie
  • LOGELBACH CTRE CIAL
  • HERZOG
  • CATHEDRALE
  • KOIFHUS
  • RUE DES CLES
  • SCHLUMBERGER
  • TRIBUNAL
  • Gare de Logelbach
  • COLMAR - Orangerie
  • SCHEURER KESTNER
  • BLAISE PASCAL
  • BISCHWIHR - Ried
  • ASSOMPTION
  • CAMILLE SEE
  • Campus Universitaire
  • COLMAR - Gare Ouest
  • COLMAR - Lauenstein
  • Légion étrangère
  • COLMAR - Ravel
  • COLMAR - Vauban
  • Gare de Colmar
  • Rue de Turckheim
  • Forêt Noire
  • LA COLOMBE
  • ANCIENNE GARE
  • FORTSCHWIHR MAIRIE
  • FLORIMONT
  • Halte de Wettolsheim
  • THEATRE
  • COSAQUES
  • BONNES GENS
  • COLMAR - manufacture trace
  • FRIBOURG
  • SAINTE-CROIX-EN-PLAINE - Mairie
  • RUDENWADEL
  • COLMAR - Poudriere
  • WALBACH MAIRIE
  • COLMAR - Théâtre
  • HORBOURG-WIHR - Pommiers
  • GILLET
  • ANDOLSHEIM - Centre Retour
  • PRIMEVERES
  • pl REPUBLIQUE
  • 1ERE ARMEE FRANCAISE
  • KATZENTHAL
  • LIEBHERR
  • MALRAUX
  • INGERSHEIM - Manoir - Cité scolaire
  • MUGUETS
  • HOUSSEN CTRE
  • HOPITAL PASTEUR
  • CTRE
  • CITE TURENNE
  • CTRE
  • HOUSSEN - ZAC du Mariafeld
  • BIOPOLE
  • ANDOLSHEIM - Centre
  • WIHR MAIRIE
  • COLMAR - Erckmann Chatrian
  • COLMAR - Préfecture
  • CHAMP DE MARS
  • ALLEE DES PEUPLIERS
  • CAMPING DE L'ILL
  • ESSOR DE L'ILL
  • THOMAS
  • COLMAR - Octroi
  • BILLING
  • DIACONAT
  • COLMAR - Ladhof
  • CLEMENCEAU
  • CHATEAU D'EAU
  • CROIX BLANCHE
  • GRILLENBREIT
  • LEBERT
  • HOHNACK
  • FBG DES VOSGES
  • BONER
  • COUR D'APPEL
  • LA CLAIRIERE
  • CITE ADMINISTRATIVE
  • PARIS
  • PL DES FETES
  • AUNES
  • POINCARE
  • QUAI DR PFLEGER
  • QUATRE VENTS
  • REY
  • INGERSHEIM - Saint Michel trace
  • STADE NAUT/PATINOIRE
  • STE ODILE
  • AUBERGE DE JEUNESSE
  • TROIS CHATEAUX
  • AMSTERDAM
  • BENES
  • CAMILLE SEE GYMNASE
  • CLOS ST-JACQUES
  • CEA
  • CTRE D'EXAMEN DU PERMIS
  • CUIRASSIERS
  • CURIE
  • HOP SCHWEITZER
  • KIENER
  • LAVOISIER
  • LUXEMBOURG
  • MAISON AGRICULTURE
  • Marché couvert
  • MITTELHARTH
  • MUSCAT
  • OBERHARTH
  • PLACE ST JOSEPH
  • PLATANE
  • COLMAR - Prunier trace
  • ROUFFACH
  • SOIE
  • STOEBER
  • TIMKEN
  • TOKAY
  • TREILLE
  • HORBOURG-WIHR - Place du 1er février
  • SUNDHOFFEN GARE
  • CTRE HIPPIQUE
  • LES ERLEN
  • ERLEN RICOH
  • WINTZENHEIM MAIRIE
  • ST GILLES
  • GRAD
  • ROMAINE
  • BLERIOT
  • SCHLUCHT
  • INGERSHEIM NORD
  • BASE NAUTIQUE
  • SCHICKELE
  • SOULTZ
  • HORBOURG-WIHR - Romains
  • ATHENES
  • COLMAR - Pfeffel
  • COLMAR - Stauffen
  • BERLIN
  • BERNE
  • COMPONENTS
  • EUROPE
  • COLMAR - Forge
  • HAUSSMANN
  • LUCCA
  • COLMAR - Parc Expositions
  • COLMAR - Rapp trace
  • ROME
  • SIX MONTAGNES NOIRES
  • STATUE DE LA LIBERTE
  • VIENNE
  • COL DE FORTSCHWIHR
  • HOUSSEN CTRE CIAL
  • CALVAIRE
  • TUILERIES
  • COLMAR - Camille See Gymnase
  • ST VINCENT DE PAUL
  • BRANT
  • COLMAR - Pont Rouge
  • AEROPORT
  • ATELIERS MUNICIPAUX
  • MINING
  • PORTE DE BALE
  • WECKMUND
  • ALPES
  • REMPART
  • UNTERLINDEN
  • EUROPE
  • BERLIN
  • AMSTERDAM
  • STADE NAUT/PATINOIRE
  • STADE NAUT/PATINOIRE
  • PARIS
  • PARIS
  • HOPITAL PASTEUR
  • HOPITAL PASTEUR
  • BENES
  • BENES
  • GARE OUEST
  • GARE OUEST
  • GARE
  • PREFECTURE
  • CHAMP DE MARS
  • CHAMP DE MARS
  • RAPP
  • RAPP
  • BONNES GENS
  • BONNES GENS
  • UNIVERSITE
  • UNIVERSITE
  • ORANGERIE
  • ORANGERIE
  • CAMPING DE L'ILL
  • CAMPING DE L'ILL
  • ROMAINS
  • ROMAINS
  • VIGNOBLE
  • VIGNOBLE
  • WIHR MAIRIE
  • WIHR MAIRIE
  • MANUFACTURE
  • MANUFACTURE
  • TROIS CHATEAUX
  • TROIS CHATEAUX
  • BILLING
  • BILLING
  • PLATANE
  • PLATANE
  • SOIE
  • SOIE
  • PRUNIER
  • PRUNIER
  • LADHOF
  • LADHOF
  • KIENER
  • KIENER
  • LAVOISIER
  • LAVOISIER
  • STATUE DE LA LIBERTE
  • STATUE DE LA LIBERTE
  • PFEFFEL
  • LES ERLEN
  • PFEFFEL
  • PONT ROUGE
  • PONT ROUGE
  • OBERHARTH
  • OBERHARTH
  • STAUFFEN
  • STAUFFEN
  • POUDRIERE
  • POUDRIERE
  • KATZENTHAL
  • KATZENTHAL
  • HIRN
  • LOGELBACH GARE
  • LOGELBACH GARE
  • HERZOG
  • HERZOG
  • LOGELBACH CTRE CIAL
  • COUR D'APPEL
  • COUR D'APPEL
  • CHATEAU D'EAU
  • CHATEAU D'EAU
  • ASSOMPTION
  • ASSOMPTION
  • AUNES
  • AUNES
  • and 248 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
  • Error108 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

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

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

  • Warning498 instances

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

  • Warning4 instances

    Some stops sit far from the route line they belong to.

    Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.

    Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)

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

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

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

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

  • Warning1 instance

    Some values have extra spaces at the start or end.

    A stray space can break a match, so a stop or route may fail to link across files.

    Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)

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

    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

  • Info442 instances

    About 442 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. 1 validator error to resolve. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 42 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.

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

TRACE (Colmar) 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/trace-colmar/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.