Feed status · checked 2026-09-01
TAD réseau CoqueliGO
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Auvergne-Rhône-Alpes, 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 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
Review the rule documentation for 'invalid_row_length' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid row length (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
Review the rule documentation for 'point_near_origin' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Point near origin (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
86 of 86 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
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
- Invalid row length (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'invalid_row_length' 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
- Point near origin (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'point_near_origin' 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
- 86 of 86 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
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 'invalid_row_length' 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.
Review the rule documentation for 'point_near_origin' 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.
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 121 days.
- Published accessibility data
- Accessibility information is stated for 0% 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 391 instances (2 error, 389 warning, 0 informational).
Service data covers the next 121 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 (TAD 1, TAD 2, TAD 3).
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.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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 85 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.
- TAD 1 (teal)
- TAD 2 (orange)
- TAD 3 (yellow)
- TAD 4 (pink)
| Route | Type | Line color |
|---|---|---|
| TAD 1 TAD Zone 1 | Bus | teal |
| TAD 2 TAD Zone 2 | Bus | orange |
| TAD 3 TAD Zone 3 | Bus | yellow |
| TAD 4 TAD Zone 4 | Bus | pink |
List every stop
- ANNONAY - Gare routière
- ANNONAY - Toissieu
- VILLEVOCANCE - Plats
- VILLEVOCANCE - Mairie
- VANOSC - Pouillas
- VANOSC - Route de Burdigne
- VANOSC - Mairie
- VOCANCE - Mairie
- MONESTIER - Mairie
- SAINT-JULIEN-VOCANCE - Mairie
- ROIFFIEUX - Fély
- ROIFFIEUX - Rue des terres
- ROIFFIEUX - Picancel
- QUINTENAS - Le mas
- QUINTENAS - Le pontet
- QUINTENAS - Goueille
- ARDOIX - ZI
- ARDOIX - Chamas
- ARDOIX - Mairie
- VERNOSC-LES-ANNONAY - Mourio
- VERNOSC-LES-ANNONAY - Les Priaux
- VERNOSC-LES-ANNONAY - Village
- VERNOSC-LES-ANNONAY - Vert
- SAINT-CYR - Village
- SAINT-CYR - Le rond
- THORRENC - Mairie
- SAINT-DESIRAT - Mairie
- TALENCIEUX - Mairie
- SAINT-JACQUES-D'ATTICIEUX - Village
- BROSSAINC - Village
- VINZIEUX - Village
- SAVAS - Mairie
- SAINT-CLAIR - Monument
- LIMONY - Village
- CHARNAS - Mairie
- SERRIERES - Mairie
- FELINES - Mairie
- FELINES - La remise
- PEAUGRES - Entrée nord
- PEAUGRES - Mairie
- BOGY - Mairie
- COLOMBIER-LE-CARDINAL - Mairie
- ANNONAY - Gare routière
- ANNONAY - Toissieu
- VILLEVOCANCE - Plats
- VILLEVOCANCE - Mairie
- VANOSC - Pouillas
- VANOSC - Route de Burdigne
- VANOSC - Mairie
- VOCANCE - Mairie
- MONESTIER - Mairie
- SAINT-JULIEN-VOCANCE - Mairie
- ROIFFIEUX - Fély
- ROIFFIEUX - Rue des terres
- ROIFFIEUX - Picancel
- QUINTENAS - Le mas
- QUINTENAS - Le pontet
- QUINTENAS - Goueille
- ARDOIX - ZI
- ARDOIX - Chamas
- ARDOIX - Mairie
- VERNOSC-LES-ANNONAY - Mourio
- VERNOSC-LES-ANNONAY - Les Priaux
- VERNOSC-LES-ANNONAY - Village
- VERNOSC-LES-ANNONAY - Vert
- SAINT-CYR - Village
- SAINT-CYR - Le rond
- THORRENC - Mairie
- THORRENC - Château
- SAINT-DESIRAT - Mairie
- TALENCIEUX - Mairie
- SAINT-JACQUES-D'ATTICIEUX - Village
- BROSSAINC - Village
- VINZIEUX - Village
- SAVAS - Mairie
- SAINT-CLAIR - Monument
- LIMONY - Village
- CHARNAS - Mairie
- SERRIERES - Mairie
- FELINES - Mairie
- FELINES - La remise
- PEAUGRES - Entrée nord
- PEAUGRES - Mairie
- BOGY - Mairie
- COLOMBIER-LE-CARDINAL - Mairie
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
12 findings, ordered by severity.
Show every finding
- Error1 instance
Invalid row length (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_row_length' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_row_length · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Point near origin (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'point_near_origin' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: point_near_origin · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning352 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)
- Warning86 instances
86 of 86 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)
- Warning34 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)
- Warning32 instances
32 of 32 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)
- Warning2 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus 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)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference 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
Two requirements remain for this feed to earn the conformance mark. 2 validator errors to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Met
- Service data covers the next 121 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 2 of 43 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 121 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 2 validator errors, 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 54 / 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/fr-pan-82904/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.