GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-10-15

Transvilles (Valenciennes)

Grade F · 33.1 / 100

Unchanged since 2026-10-14.

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.

What changed since the last check

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

Top three things to fix

  1. Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.

    Service data ended 45 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist.

    This one is about the feed as a whole, so there is no share of it to count.

    Effort: Usually one export setting; export on a schedule so it never lapses again.

  2. Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.

    This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

    Effort: Varies.

  3. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

    1528 of 1890 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.

    Fixing this covers 1,528 of 1,890 stops, about 81% of them.

    Effort: A column in stops.txt; your scheduling software likely has it.

Riders and need behind these fixes

  • Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
  • The served-area need overlays cover the United States and Canada, so none of them applies to this feed.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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
Service data ended 45 day(s) ago.
Next action
Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.
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

Ready to send to the agency

Hi Transvilles (Valenciennes) team, Service data ended 45 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist. The fix is usually one export setting: Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/transvilles-valenciennes/

Copy this note from the full scorecard.

Key facts

Feed URL
https://transport.data.gouv.fr/resources/82442/download
Last checked
2026-10-15
Service window
Feed has expired. Last service date 2026-08-31.
Location
Hauts-de-France, France

Part of the France portfolio: see where this agency sits among the other feeds in that group before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.2, validator 8.0.1.