Feed status · checked 2026-09-01
Trains régionaux ZOU ! — Transdev Rail Sud
Based on the official feed source on file
Service mode Rail
First scorecard for this agency
Catalogued in Provence-Alpes-Côte-d’Azur, 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 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 3 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
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.
⏱ Varies.worth about +12 points in its category
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
17 of 17 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
Ask your AVL vendor to send updates at least every 20 seconds. That is the Caltrans guideline.
Realtime data was up to 432 seconds old when sampled. Stale positions and predictions are worse than none: riders watch a transit vehicle that already left.
⏱ A vendor configuration question.worth about +20 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
- Foreign key violation (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- 17 of 17 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
- Realtime data was up to 432 seconds old when sampled.
- Next action
- Ask your AVL vendor to send updates at least every 20 seconds. That is the Caltrans guideline.
- 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.
Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
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. Self-check a feed before you publish.
Ask your AVL vendor to send updates at least every 20 seconds. That is the Caltrans guideline.
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 102 days.
- Published accessibility data
- Accessibility information is stated for 0% 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
- 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
The MobilityData validator flagged 9 kinds of issue across 26731 instances (1 error, 26730 warning, 0 informational).
Service data covers the next 102 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.
1 accessibility depth signal
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (SUD_IV15).
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.
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.
Sampled 3 times: 1 of 1 configured feed healthy; 100.0% of scheduled trips had live predictions; 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 17 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.
| Route | Type | Line color |
|---|---|---|
| SUD_IV15 Nice - Marseille | Rail | gray (no shape in feed) |
List every stop
- Marseille-St-Charles
- Marseille-Blancarde
- La Pomme
- Aubagne
- Cassis
- Toulon
- Carnoules
- Les Arcs-Draguignan
- Nice-Ville
- Nice-St-Augustin
- Villeneuve-Loubet-Plage
- Fréjus
- St-Raphaël-Valescure
- Cannes
- Golfe-Juan-Vallauris
- Antibes
- Biot
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
14 findings, ordered by severity.
Show every finding
- Error1 instance
Foreign key violation (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: foreign_key_violation · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning26723 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3193 instances
3193 of 3193 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)
- Warning17 instances
17 of 17 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)
- Warning1 instance
Some scheduled trips move faster between stops than a transit vehicle can.
Usually a typo'd stop time; riders get arrival times no transit vehicle can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Between two distant stops, the times imply a speed no transit vehicle reaches.
A rider gets a trip plan that cannot happen. Live systems then report delays that are not real.
Fix: Check the two stop times for a wrong digit first. Then check whether a stop sits at the wrong coordinates, or a stop between them is missing. (Minutes per flagged trip once you open it.)
Finding code: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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.)
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
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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Unexpected enum value (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unexpected_enum_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unexpected_enum_value · 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)
- Warning1 instance
Realtime data was up to 432 seconds old when sampled.
Stale positions and predictions are worse than none: riders watch a transit vehicle that already left.
Fix: Ask your AVL vendor to send updates at least every 20 seconds. That is the Caltrans guideline. (A vendor configuration question.)
Finding code: scorecard_rt_stale
- 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
Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 102 days.
- Accessible Not yet
- States wheelchair access on 0% 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.
Realtime reliability
The realtime feed responded on 100.0% of 5 checks over the last 1 day, with 6676s 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 1800s nine times in ten. They were on time (about a minute early to five late) 56.5% 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 102 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 1 validator error, the other thing Maps checks at onboarding; the findings below name each fix.
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 52 / 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 38 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 80 / 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.
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-83448/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.