← All agencies

Feed status · checked 2026-09-01

Réseau urbain LiA

Based on the official feed source on file

Service mode Tram + Bus

80.0 / 100

First scorecard for this agency

Catalogued in Normandie, France.

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

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

5634 of 5634 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 02

Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool

feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

⏱ Two fields, set once in export settings.worth about +15 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

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
5634 of 5634 trips don't say whether the vehicle is wheelchair accessible.
Next action
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
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. 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.

  2. Add feed_info.txt with feed_start_date and feed_end_date to your export. · 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 60 days.
Published accessibility data
Accessibility information is stated for 100% 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
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

Correctness79.2 / 100

The MobilityData validator flagged 4 kinds of issue across 3802 instances (0 error, 3790 warning, 12 informational).

Freshness85.0 / 100

Service data covers the next 60 days.

Rider experience60.9 / 100

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

Accessibility62.5 / 100

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

1 accessibility depth signal

  • 45 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("St Dignefort", "St Nicolas", "St Exupéry", and more).

    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.

Realtime quality100.0 / 100

Sampled 9 times: 3 of 3 configured feeds healthy; 100.0% of scheduled trips had live predictions; vehicle position plausibility was not measurable; predictions ran a median of 0s behind schedule.

Routes and stops

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

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

Routes in Réseau urbain LiA's feed
RouteTypeLine color
09 Gares - Mt LecomteBusgreen (no shape in feed)
10 Grand Hameau - Parc EstuaireBusgreen (no shape in feed)
11 Gares - Cours Ste-CroixBusgreen (no shape in feed)
11E Gares - Cours Ste-CroixBusgreen (no shape in feed)
12 Gares - Cite des AbbessesBusgreen (no shape in feed)
13 Grand Hameau - EtretatBusgreen (no shape in feed)
14 Grand Hameau - Parc EstuaireBusgreen (no shape in feed)
15 Gares - Zone IndustrielleBusgreen (no shape in feed)
16 Gares - Mt GaillardBusgreen (no shape in feed)
17 P. Estuaire - Cite des AbbessesBusgreen (no shape in feed)
18 Gares - Zone IndustrielleBusgreen (no shape in feed)
19 Gares - Mt LecomteBusgreen (no shape in feed)
20 Pl. d'Armes - GaresBusgreen (no shape in feed)
21 Gares - EtretatBusgreen (no shape in feed)
25 Gares - Zone industrielleBusgreen (no shape in feed)
60 Lycee J. Prevost - C. HistoriqueBusgreen (no shape in feed)
70 College G. Courbet - P. a MmeBusgreen (no shape in feed)
71 College G. Courbet - F. EngelsBusgreen (no shape in feed)
91 Cite des Abbesses - CFABusgreen (no shape in feed)
A Rond-Point - Grand HameauTram / light railred (no shape in feed)
B Rond-Point - Pre FleuriTram / light railred (no shape in feed)
C1 La Heve - Cite des AbbessesBusgreen (no shape in feed)
C2 Grand Quai - SoquenceBusgreen (no shape in feed)
C3 Grand Hameau - GravilleBusgreen (no shape in feed)
C4 Grand Hameau - GaresBusgreen (no shape in feed)
C5 Dollemard - La VouteBusgreen (no shape in feed)
C6 Hotel de Ville - Mt GaillardBusgreen (no shape in feed)
C7 Hotel de Ville - CaucriauvilleBusgreen (no shape in feed)
C8 Hotel de Ville - Mt GaillardBusgreen (no shape in feed)
FUNI Lycee C. Monet - Pl. ThiersBusgreen (no shape in feed)
LP Gares Magellan - PlageBusgreen (no shape in feed)
NB La Forge - J. MermozBusgreen (no shape in feed)
P+R Mode P+RBusgreen (no shape in feed)
P+V Mode P+VBusgreen (no shape in feed)
SUB BUS - GD HAMEAU/PRE FLEURI/GAREBusgreen (no shape in feed)
List every stop
  • Butee Plage V1
  • Butee Plage V2
  • Butee Grand Hameau V1
  • 5564 Baudin Chateauneuf
  • Desmarais
  • Desmarais
  • 4 Chemins
  • 4 Chemins
  • Ste Honorine
  • Ste Honorine
  • 19-mars-62
  • Dollemard
  • Acacias
  • A. Agasse
  • A. Agasse
  • Bains Maritimes
  • Bains Maritimes
  • Les Halles
  • A. Samain
  • A. Samain
  • S. Allende
  • S. Allende
  • Ingouville
  • Ingouville
  • Ingouville
  • Ingouville
  • A. Croizat
  • A. Croizat
  • La Fermière
  • La Fermière
  • A. Barbès
  • A. Barbès
  • A. Barbès
  • Arromanches
  • Arromanches
  • Arsenal
  • Arsenal
  • Artois
  • A. Blanqui
  • A. Blanqui
  • J. Deschaseaux
  • A. Normand
  • 16ème Port
  • 16ème Port
  • Le Mignot
  • Le Mignot
  • Baticoop
  • Baticoop
  • Bayonvillers
  • Bayonvillers
  • Beaulieu Nord
  • Beaulieu Nord
  • Belle Etoile
  • Belle Etoile
  • M. Berthelot
  • M. Berthelot
  • Jonquilles
  • Bois Cody
  • Bois Cody
  • L. Cherubini
  • Bonsecours
  • Bonsecours
  • Bd du Midi
  • Bd du Midi
  • Bréquigny
  • Broche à Rôtir
  • Broche à Rôtir
  • Camp Dolent
  • Camp Dolent
  • Bléville Église
  • Capuchet
  • Carreau
  • Carreau
  • Carrousel
  • Carrousel
  • Castors
  • Castors
  • Cathédrale
  • Moulin du Vey
  • Rouelles Équestre
  • Rouelles Équestre
  • Ctre Equestre
  • Ctre Equestre
  • F. Léger
  • F. Léger
  • C. Oursel
  • C. Oursel
  • C. Oursel
  • Atahualpa
  • Atahualpa
  • Ch. de Foire
  • Ch. de Foire
  • La Linerie
  • Champs Barêts
  • Champs Barêts
  • La Linerie
  • C. de Gaulle
  • C. de Gaulle
  • C. Perrault
  • C. Perrault
  • L'Ormelle
  • Les Neiges
  • Les Neiges
  • Chateaudun
  • Chateaudun
  • Chef de Caux
  • Chef de Caux
  • Chemin d'Enfer
  • Chemin d'Enfer
  • Ch. du Chouquet
  • Ch. du Chouquet
  • E. Quinet
  • E. Quinet
  • Cité Chauvin
  • Cité Chauvin
  • Albert 1er
  • Albert 1er
  • C. Marot
  • Lt Clérivet
  • Lt Clérivet
  • Clos du Puits
  • Clos du Puits
  • Cochet
  • Cochet
  • Collège de La Hève
  • Collège de La Hève
  • St François
  • ESAT Porte Océane
  • St François
  • Condé
  • Condé
  • Côte d'Orcher
  • Côte d'Orcher
  • Côte de l'Estuaire
  • Côte de l'Estuaire
  • Côtes Blanches
  • Côtes Blanches
  • Erables
  • Erables
  • R. Coty
  • G. Courbet
  • G. Courbet
  • Cronstadt
  • Cronstadt
  • P. Vatine
  • P. Vatine
  • D. Cordonnier
  • D. Cordonnier
  • G. Brindeau
  • G. Brindeau
  • 5566 - Veolia
  • R. Descartes
  • Calvaire
  • Calvaire
  • St Pierre
  • St Pierre
  • Dollemard
  • Stendhal
  • Le Bosquet
  • Route du Ponant
  • H. Genestal
  • Moulin du Vey
  • Hérons
  • Hérons
  • L. Lagrange
  • E. Meyer
  • E. Meyer
  • L. Lagrange
  • J. Deschaseaux
  • J. Deschaseaux
  • Dr Levesque
  • Bléville Église
  • Bléville Église
  • Sanvic Église
  • Sanvic Église
  • Frileuse
  • Frileuse
  • Chapelle
  • D'Estiennne d'Orves
  • D'Estiennne d'Orves
  • E. Boudin
  • E. Boudin
  • G. Lafaurie
  • G. Lafaurie
  • F. Faure
  • Fleurville
  • Fleurville
  • F. Laurent
  • F. Laurent
  • 5548 Le Havre Groupage
  • Pl. St Valéry
  • Hallates
  • Hallates
  • Chapelle
  • F. de Grâce
  • F. de Grâce
  • St Vincent
  • L. Blériot
  • L. Blériot
  • 5106 - Renault Usine
  • Pressensé
  • 5550 - Geodis - Tramar
  • Atrium
  • Atrium
  • Gascogne
  • Gascogne
  • 4934 Bolloré Logistics
  • 4934 Bolloré Logistics
  • 3065 Terminal Europe
  • Gal Chanzy
  • Schuman
  • Gal Dodds
  • Gal Sarrail
  • Gal Sarrail
  • G. Sand
  • G. Sand
  • George V
  • George V
  • O. Niemeyer
  • Verlaine
  • Gobelins
  • Frileuse
  • Frileuse
  • Verlaine
  • Curie
  • Curie
  • Grenouillère
  • Grenouillère
  • St Dignefort
  • St Dignefort
  • Les Guêpes
  • Les Guêpes
  • Les Halles
  • 5386 - Colibris
  • 5362 - Sarcelles
  • 5358 - Hesnault
  • 5555 - Parc du Hode
  • 5521 DB Schenker Mar.
  • Hameau des Corneilles
  • Hameau des Corneilles
  • H. Montlairy
  • H. Montlairy
  • H. Montlairy
  • Parc Éco-Normandie
  • Monceau aux Chiens
  • Bois de Bléville
  • Bois de Bléville
  • H. Mehl
  • H. Mehl
  • Hôpital Flaubert
  • and 844 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

9 findings, ordered by severity.

Show every finding
  • Warning5634 instances

    5634 of 5634 trips don't say whether the vehicle is wheelchair accessible.

    Even with accessible stops, riders need to know the transit vehicle 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 (opens the GTFS Schedule reference on an external site)

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

    Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning584 instances

    584 of 5634 trips have no headsign, the text that tells riders where the transit vehicle is going.

    When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

    Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)

    Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Warning119 instances

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

    Riders may walk to a stop where no transit vehicle 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.)

    Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    A file GTFS asks for (usually feed_info.txt) is missing.

    feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.

    Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)

    Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    feed_info.txt is missing its start/end dates (the file itself is absent)

    Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

    Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)

    Finding code: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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

    Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Info12 instances

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

    The sign should tell riders where the transit vehicle 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 (opens the validator rules on an external site)

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Conformance mark Not yet

One requirement remains for this feed to earn the conformance mark. States wheelchair access on 100% of stops and 0% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 60 days.
Accessible Not yet
States wheelchair access on 100% 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.

Can riders use it?

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

  • 119 of 1094 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.

Realtime reliability

The realtime feed responded on 100.0% of 5 checks over the last 1 day, with 42s 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 right on the schedule, and stayed within 184s nine times in ten. They were on time (about a minute early to five late) 87.9% 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 60 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 79 / 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 85 / 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 61 / 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 LiA 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-pan-84037/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.