GTFS Scorecard
← All agencies

Feed status · checked 2026-09-13

Move (Vendôme)

Based on the official feed source on file

Service mode Bus

71.0 / 100

unchanged since 2026-09-12

Catalogued in Centre-Val de Loire, France.

Covers 2544 daysAccessibility gapsRealtime not yet published

Heads-up: The score rose 32 points in one step, from 39 on 2026-08-07 to 71 on 2026-09-12. A jump this size usually means the export changed rather than the service. Worth checking the run on this date. (checked 2026-09-12). This can be a brief vendor export glitch; watch the next update before acting.

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 30 hours ago; last changed 30 hours ago.

Measured 3 of 4 score categories from the official feed URL on file.

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

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 02

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

Fix 03

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

98 of 166 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 +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
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.

  1. Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide for scorecard_missing_feed_info_dates

    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.

  2. 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 for scorecard_no_fare_data

    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.

  3. 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 for scorecard_wheelchair_boarding_unknown

    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 2544 days.
Published accessibility data
Accessibility information is stated for 41% 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

Correctness69.0 / 100

The MobilityData validator flagged 9 kinds of issue across 11806 instances (0 error, 11119 warning, 687 informational).

Freshness85.0 / 100

Service data covers the next 2544 days.

Rider experience62.7 / 100

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

Accessibility63.1 / 100

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

2 accessibility depth signals

  • 6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (B, C, D, E, ESAT, and more).

    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.

  • 2 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Av. Colin", "Av. Colin").

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

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

  • A (red)
  • B (green)
  • C (yellow)
  • D (teal)
  • E (orange)
  • ESAT (teal)
  • F (white)
  • G (purple)
  • H (brown)
  • M (black)
  • TGV (green)
Routes in Move (Vendôme)'s feed
RouteTypeLine color
A LIGNE ABusred
B LIGNE BBusgreen
C LIGNE CBusyellow
D LIGNE DBusteal
E LIGNE EBusorange
ESAT LIGNE ESATBusteal
F LIGNE FBuswhite
G LIGNE GBuspurple
H LIGNE HBusbrown
M LIGNE MBusblack
TGV NAVETTE TGVBusgreen
List every stop
  • Ampère
  • Ampère
  • Amphithéâtre
  • Amphithéâtre
  • Place des anciens combattants
  • La Barre
  • La Barre
  • Berlioz
  • Berlioz
  • Saint-Bienheuré
  • Saint-Bienheuré
  • Bois la Barbe
  • Bois la Barbe
  • Antoine de Bourbon
  • Antoine de Bourbon
  • Branly
  • Branly
  • Pont de Braye - Route de Sougé
  • Pont de Braye - Route de Sougé
  • Butte Catherinet
  • Champlés
  • Champlés
  • Chartrain
  • Chautard
  • Chautard
  • Chenillé - D917
  • Chenillé - D917
  • Cheval Blanc
  • Cheval Blanc
  • Cimetière Nord
  • Cimetière Nord
  • Cités Unies
  • Cités Unies
  • Clouseaux
  • Clouseaux
  • Av. Colin
  • Av. Colin
  • Condorcet
  • Condorcet
  • Couture - Église
  • Croix Blanche
  • Croix Blanche
  • Croix Verte
  • Croix Verte
  • Danan
  • Danan
  • Debussy
  • Debussy
  • Eiffel
  • ESAT de Lunay
  • Europe
  • Europe
  • Faton
  • Faton
  • Fauré
  • Fauré
  • Flandres
  • Flandres
  • Fontaines
  • La Garde
  • La Garde
  • Gare TER
  • Gare TER ligne
  • Saint-Georges
  • Saint-Georges
  • Gué du Loir
  • Gué du Loir
  • Guimond
  • Guimond
  • Gérard Yvon
  • Gérard Yvon
  • Hamet
  • Hamet
  • Hôpital
  • Hôpital
  • Île de France
  • Île de France
  • Industrie
  • Industrie
  • Jacques Brel
  • Jeanne d'Albret
  • Jeanne d'Albret
  • Jean Moulin
  • Jean Moulin
  • Jean Emond ligne
  • Jean Emond
  • Jouhaux
  • Jouhaux
  • Jules Valles
  • Jules Valles
  • Kennedy
  • Kennedy
  • Lycée Agricole Montoire
  • Mail Leclerc
  • Mail Leclerc
  • Liberté
  • Louise Michel
  • Louise Michel
  • Saint-Lubin
  • Saint-Lubin
  • Centre Bourg
  • Centre Bourg
  • Mairie d'Areines
  • Mallarmé
  • Mallarmé
  • Mairie de Meslay
  • Monet
  • Mons
  • Mons
  • Collège Janequin
  • Gendarmerie
  • Gendarmerie
  • Mairie de Montoire
  • Montrieux
  • Montrieux
  • Nioche
  • Offenbach
  • Offenbach
  • Les Ormeaux
  • Place des Pâtis
  • La Pointe
  • La Pointe
  • La Poste
  • La Poste
  • Prazerie
  • Prazerie
  • Provinces
  • Robert Lasneau
  • Rochettes
  • Église Les Roches
  • Église Les Roches
  • Roi Henri
  • Roi Henri
  • Lycée Ronsard
  • Lycée Ronsard ligne
  • Lycée Ronsard
  • Route de Blois
  • Route de Blois
  • Église Sougé
  • Église Sougé
  • Église St-Ouen
  • Mairie de St-Ouen
  • Mairie de St-Ouen
  • Saint-Gervais
  • Saint-Gervais
  • Saint-Marc
  • Saint-Marc
  • Saint-Michel
  • Saint-Michel
  • Gare TGV
  • Les Quatre Tilleuls
  • Les Quatre Tilleuls
  • Saint-Quentin-Lès-Trôo
  • Place de la Libération
  • Place de la Libération
  • Saint-Quentin-Lès-Trôo
  • Dumont d'Urville
  • Vallée
  • Saint-Venant
  • Saint-Venant
  • École Villiers-Sur-Loir
  • École Villiers-Sur-Loir
  • ZI Nord
  • ZI Nord
  • Z.I Sud
  • Z.I Sud

Over time

Overall score across the last 4 checks — unchanged since 2026-09-12.

2026-08-06: 39.72026-08-07: 39.32026-09-12: 71.02026-09-13: 71.0
Show the numbers
CheckScoreChange
2026-08-0639.7 first check
2026-08-0739.3 down 0.4
2026-09-1271.0 up 31.7
2026-09-1371.0 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

What changed over time

On 2026-08-06 this feed started at grade F. On 2026-09-12 the grade moved from F to C. On 2026-09-13 the check no longer reported: some files leave out fields that GTFS asks for but does not require; some internal IDs use characters outside the basic text set; service data runs out in 24 day(s); 773 of 773 trips lack rider-facing destination or direction text; about 107 stop names are written in ALL CAPS; 4 of 773 trips don't say whether the vehicle is wheelchair accessible; some files contain columns that are not part of the GTFS spec. As of 2026-09-13 it holds grade C.

A plain-language history of this feed, newest first.

  • 2026-09-12 Grade went F to C, freshness rose 60 points.

Everything we checked

13 findings, ordered by severity.

Show every finding
  • Warning9832 instances

    Some rows in stop_times.txt leave the timepoint column blank.

    That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.

    Fix: Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1. (Usually one export setting.)

    Finding code: missing_timepoint_value · Read the fix guide for missing_timepoint_value · See MobilityData GTFS Validator rules

  • Warning1284 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules

  • Warning98 instances

    98 of 166 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference

  • 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 for missing_recommended_file · See MobilityData GTFS Validator rules

  • Warning1 instance

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

    Finding code: route_color_contrast · Read the fix guide for route_color_contrast · See MobilityData GTFS Validator rules

  • Warning1 instance

    Many of the feed's trips don't run at all in the next 7 days.

    It usually means old service periods are still in the export, making the feed bigger and harder to check.

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

    Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide for trip_coverage_not_active_for_next7_days · See MobilityData GTFS Validator rules

  • 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 for scorecard_missing_feed_info_dates · 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.)

    Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices

  • Info640 instances

    Trip with shape dist traveled but no shape distances (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: trip_with_shape_dist_traveled_but_no_shape_distances · See MobilityData GTFS Validator rules

  • 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 for big_gap_in_service · See MobilityData GTFS Validator rules

  • Info9 instances

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

    Finding code: service_extends_far_in_the_future · See MobilityData GTFS Validator rules

  • Info2 instances

    Platform without parent station (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: platform_without_parent_station · See MobilityData GTFS Validator rules

  • 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 for scorecard_no_feed_contact · See MobilityData GTFS Validator rules

Conformance mark Not yet

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

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 2544 days.
Accessible Not yet
States wheelchair access on 41% 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 2542 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 69 / 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 63 / 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.

Part of the France portfolio: the same scorecards for every feed we track in that group, on one free page.

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.

Move (Vendôme) GTFS data quality grade: C

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/move-vendome/2026-09-13.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-13. 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.