Feed status · checked 2026-08-01
SEMO (Seine-Eure)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Normandie, France.
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 9 hours ago; last changed 2 days ago.
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
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
460 of 461 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
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
8475 of 8475 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
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
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
- 460 of 461 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- Feed evidence
- 8475 of 8475 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
- Feed evidence
- feed_info.txt is missing its start/end dates (the file itself is absent)
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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.
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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 333 days.
- Published accessibility data
- Accessibility information is stated for 0.2% 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
The MobilityData validator flagged 6 kinds of issue across 233976 instances (0 error, 233940 warning, 36 informational).
Service data covers the next 333 days.
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.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (7a, 7b, C1).
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.
14 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("St Exupéry Louviers", "St Exupéry Louviers", "St Hildevert", 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.
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.
This feed has 461 stops.
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.
- 10 (brown)
- 2 (orange)
- 3 (white)
- 4 (purple)
- 5 (teal)
- 6 (white)
- 6a (white)
- 6b (white)
- 7a (brown)
- 7b (brown)
- 8 (teal)
- 9 (green)
- C1 (orange)
- D1 (gray)
- E1 (yellow)
- NHP (black)
- S1 (yellow)
- S25 (yellow)
- S2 (yellow)
- S3 (yellow)
- S4 (yellow)
- S5 (yellow)
- S7 (yellow)
| Route | Type | Line color |
|---|---|---|
| 10 Acquigny Les Sablons / Louviers Lycée Les Fontenelles | Bus | brown |
| 2 Louviers Lycée Les Fontenelles / Val-de-Reuil Gare SNCF | Bus | orange |
| 3 Louviers Rendez-Vous Bus / Louviers Glacéo | Bus | white |
| 4 Val-de-Reuil Gare SNCF /Léry / Val-de-Reuil Gare SNCF | Bus | purple |
| 5 Pîtres Espace des 2 Rives / Val-de-Reuil Gare SNCF | Bus | teal |
| 6 Le Val d'Hazey Gare SNCF Gaillon-Aubevoye | Bus | white |
| 6a Le Val d'Hazey Gare SNCF Gaillon-Aubevoye - Sens Anti-Horaire | Bus | white |
| 6b Le Val d'Hazey Gare SNCF Gaillon-Aubevoye - Sens Horaire | Bus | white |
| 7a Val-de-Reuil Gare SNCF - Sens Horaire | Bus | brown |
| 7b Val-de-Reuil Gare SNCF - Sens Anti-Horaire | Bus | brown |
| 8 Val-de-Reuil Gare SNCF / Connelles Mairie | Bus | teal |
| 9 Louviers Rendez-vous Bus / Heudebouville Ecoparc Clos Desruets | Bus | green |
| C1 Val-de-Reuil Gare SNCF / Louviers Rendez-Vous bus | Bus | orange |
| D1 Louviers Lycée Les Fontenelles / Val-de-Reuil Gare SNCF | Bus | gray |
| E1 St Aubin Les Elbeuf Hôpital / Le Val d'Hazey Gare SNCF Gaillon | Bus | yellow |
| NHP Navette Hauts Prés | Bus | black |
| S1 Porte-de-Seine / Louviers | Bus | yellow |
| S25 Louviers College Lipinska / Val-de-Reuil Mairie | Bus | yellow |
| S2 Val de Reuil / Incarville / Louviers / Pinterville | Bus | yellow |
| S3 Pinterville / Louviers | Bus | yellow |
| S4 Louviers Les Monts / Louviers Les Fontenelles | Bus | yellow |
| S5 Porte-de-Seine / Val-de-Reuil | Bus | yellow |
| S7 Pont-de-L'Arche | Bus | yellow |
List every stop
- Ecole
- Bourg
- Bourg
- Les Sablons
- Les Sablons
- Aristide Briand
- Aristide Briand
- Ecole
- Anciens Commerces
- Anciens Commerces
- Centre Commercial
- Centre Commercial
- Garenne
- Garenne
- Poste Alizay
- Poste Alizay
- Rousselle
- Rousselle
- Saules
- Saules
- Stade Alizay
- Stade Alizay
- Capucines
- Capucines
- Le Moulin Andé
- Le Moulin Andé
- Pierre Ricard
- Pierre Ricard
- Prunus
- Prunus
- VIEUX-VILLEZ
- VIEUX-VILLEZ
- Avenue de l'Europe
- Avenue de l'Europe
- Charles De Gaulle
- Charles De Gaulle
- Jardinerie
- Jardinerie
- Clg Simone Signoret
- Centre Technique
- Gaillon-Abvye SNCF
- Mairie Val d'Hazey
- Mairie Val d'Hazey
- St Fiacre
- St Fiacre
- Grosmesnil
- Grosmesnil
- Les Vallets
- Les Vallets
- Mairie Connelles
- Les Canadiens
- Bonport
- Bonport
- Rond de l'Eure
- Rond de l'Eure
- Martinet
- Martinet
- Les Canadiens
- Rougemont
- Charmes
- Charmes
- Clinique Les Damps
- Clinique Les Damps
- Escarpolette
- Escarpolette
- FONTAINE-BELLENGER
- FONTAINE-BELLENGER
- Aquaval
- Aquaval
- Eglise Gaillon
- Château Gaillon
- Château Gaillon
- Claude Monet
- Claude Monet
- Gailloncel
- Gailloncel
- Estouteville
- Les Lavandieres
- Les Lavandieres
- Mairie Gaillon
- Marché Gaillon
- Centre Médical
- Centre Médical
- Les Mésanges
- Maréchal Leclerc
- Maréchal Leclerc
- Roland Roche
- Marché Gaillon
- Centre Commercial
- Marché Gaillon
- Mairie Herqueville
- Mairie Herqueville
- Village Herqueville
- La Limousine
- La Limousine
- La Butte a Colas
- La Butte a Colas
- Les Brelondes
- Centre Routier
- Fosse Moret
- Les Érables
- Les Tilleuls
- Les Tilleuls
- Sous-Maillé
- Clos Desruets
- Centre Commercial
- Centre Commercial
- Commerces Igoville
- Commerces Igoville
- Pont-de-l'Arche SNCF
- Pont-de-l'Arche SNCF
- Rue du 8 Mai
- Rue du 8 Mai
- Rue de Lyons
- Rue de Lyons
- Coquelicots
- Epreville
- Epreville
- La Source
- La Source
- Mairie Incarville
- Mairie Incarville
- INCARVILLE St-Cyr
- INCARVILLE St-Cyr
- INCARVILLE Village
- INCARVILLE Village
- La Ronciere
- La Ronciere
- Charles De Gaulle
- Cryo
- Jules Ferry
- Mairie Léry
- Mairie Léry
- Marcel Picard
- Parc de Loisirs
- Voltaire
- Le Golf Val-de-Reuil
- Victor Hugo Léry
- Souvenir
- Delaunay
- Delaunay
- L'Eure
- L'Eure
- Coquelicots
- 11 Novembre
- 11 Novembre
- Abattoirs
- Abattoirs
- Adrien Breton
- Adrien Breton
- Acacias
- Acacias
- Alexandre Dumas
- Alexandre Dumas
- Beaulieu
- Belgique
- Bois Vacher
- Plaine des Loisirs
- Plaine des Loisirs
- Charles Cros
- Charles Cros
- Chaussée Decrétot
- Chaussée Decrétot
- College les Fougeres
- College les Fougeres
- College Lipinska
- Châtel
- Châtel
- Cimetiere Louviers
- Cimetiere Louviers
- Clinique Louviers
- Chemin des Monts
- Côte des Monts
- Clos des Vignes
- Champ de Ville
- Champ de Ville
- Champ de Ville
- College F.Buisson
- College F.Buisson
- François Mitterrand
- François Mitterrand
- Foch
- Foch
- Le Hub
- Le Hub
- Guy De Maupassant
- Guy De Maupassant
- Hélene Boucher
- Hélene Boucher
- Hôpital Louviers
- Hôpital Louviers
- Joffre
- Joffre
- Jardin Public
- Jardin Public
- Jean Zay
- Jean Zay
- Kolysé
- Kolysé
- La Mare
- Les Cascades
- Les Cascades
- Lycée Decrétot
- Lycée Decrétot
- Lyc Les Fontenelles
- Lyc. Les Fontenelles
- Les Joncquilles
- La Londe
- La Londe
- Leroy Mary
- Leroy Mary
- Le Parc
- Le Parc
- La Plaquette
- La Plaquette
- La Plaquette
- La Plaquette
- La Roquette
- Les Vignes
- Les Vignes
- La Villette
- La Villette
- Maréchal Leclerc
- Maison Rouge
- Nouveau Monde
- Nouveau Monde
- Olivier De Serres
- Olivier De Serres
- Paris
- Paris
- Porte de l'Eau
- Porte de l'Eau
- Pichou
- Pichou
- Point du Jour
- Point du Jour
- Ravine
- Rendez-Vous Bus
- Rendez-Vous Bus
- Roger Martin Du Gard
- Roger Martin Du Gard
- Raoul Verlet
- Raoul Verlet
- Seine
- Seine
- St Exupéry Louviers
- St Exupéry Louviers
- St Hildevert
- St Hildevert
- Thorel
- and 211 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 48.1 | first check |
| 2026-07-30 | 62.4 | up 14.3 |
| 2026-07-31 | 62.4 | no change |
| 2026-08-01 | 62.4 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
What changed over time
On 2026-07-25 this feed started at grade F. On 2026-07-30 the grade moved from F to D. As of 2026-08-01 it holds grade D.
A plain-language history of this feed, newest first.
- 2026-07-30 Grade went F to D, correctness rose 32 points.
Everything we checked
11 findings, ordered by severity.
Show every finding
- Warning224546 instances
Missing timepoint value (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_timepoint_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning8475 instances
8475 of 8475 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning7457 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.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1932 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.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning460 instances
460 of 461 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning4 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)
- 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)
- Info36 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.)
Finding code: big_gap_in_service · Read the fix guide · 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).
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.)
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
This feed is close to the conformance mark. States wheelchair access on 0% 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 333 days.
- Accessible Not yet
- States wheelchair access on 0% 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 333 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 67 / 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 37 / 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.
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/semo-seine-eure/2026-08-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-08-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.