GTFS Scorecard
← All agencies

Feed status · checked 2026-07-23

Réseau urbain TIVA

Based on the feed this agency publishes

Service mode Bus

89.6 / 100

First scorecard for this agency

Catalogued in Normandie, France.

Covers 161 daysRealtime 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

Populate trip_headsign to match what the bus displays.Likely your export tool

17 of 17 trips have no headsign. Riders at the stop can't tell which direction a bus is going.

⏱ Usually a bulk edit in your scheduling software.worth about +15 points in its category

Fix 02

Review the flagged fields and fill in the ones your riders would use.

Some files leave out fields that GTFS asks for but does not require. Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

⏱ A field at a time; not urgent.worth about +4 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 +4 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. Populate trip_headsign to match what the bus displays. · 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. Review the flagged fields and fill in the ones your riders would use. · 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 100% of stops and 100% 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
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

Correctness87.0 / 100

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

Freshness100.0 / 100

Service data covers the next 161 days.

Rider experience85.0 / 100

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

Accessibility100 / 100

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

1 accessibility depth signal

  • 1 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Mermoz / Maupas").

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

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 qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

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 TIVA's feed
RouteTypeLine color
Tiva_urbain VIRE - "Les Mancellières - Parc CommercialBusgreen (no shape in feed)

This feed has 31 stops.

List every stop
  • Les Mancellières
  • Rue Guy Degrenne (France Travail)
  • Gare SNCF
  • Piscine (Aquavire)
  • Les Acres
  • Lycée Marie Curie (Clinique)
  • Martilly
  • A. Malraux
  • G. Pompidou
  • Abbé Vallée
  • M. Foubert
  • Atlacomulco
  • Neuville Bourg
  • Rue de la Planche (Jean Moulin)
  • Rue de Bretagne
  • Zone du Neuvillé
  • Centre Commercial Le Maupas
  • Bichwiller
  • La Douitée
  • Parc Commercial
  • Pont Féron
  • Musée
  • Route de Condé
  • La Monderie
  • Sainte Anne
  • Mermoz / Maupas
  • 11 novembre
  • Hôpital
  • La Poste
  • Champ de Foire
  • A. Halboult

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

6 findings, ordered by severity.

Show every finding
  • Warning17 instances

    17 of 17 trips have no headsign.

    Riders at the stop can't tell which direction a bus is going.

    Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)

    Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices

  • Warning5 instances

    Some files leave out fields that GTFS asks for but does not require.

    Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

    Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)

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

  • Warning1 instance

    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

  • Warning1 instance

    Some stops exist in the feed but no trip ever stops at them.

    Riders may walk to a stop where no bus is scheduled to arrive.

    Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

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

  • Info1 instance

    Service extends far in the future (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: service_extends_far_in_the_future · See MobilityData GTFS Validator rules

  • Info1 instance

    Some service dates fall outside the date window set in feed_info.txt.

    feed_info.txt should span every day your service runs, so apps know when the data applies.

    Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)

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

Conformance mark Awarded

This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.

GTFS conformance mark for Réseau urbain TIVA

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 161 days.
Accessible Met
States wheelchair access on 100% of stops and 100% of trips.

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.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

  • 1 of 31 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Clears the Google and Apple Maps four-week coverage bar. This feed has 1134 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 87 / 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 85 / 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 TIVA 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-tiva/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.