Feed status · checked 2026-10-15
TAD ligne Arrens-Marsous - Lourdes
Based on the official feed source on file
Service mode Bus
unchanged since 2026-10-14
Cataloged in Occitanie, France.
Source feed: https://www.data.gouv.fr/api/1/datasets/r/382a2cc7-336b-49ff-9fbd-f355629701b6
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.4, validator 8.0.1.
Checked for changes 3 hours ago; last changed 83 days 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.
About this feed
TAD ligne Arrens-Marsous - Lourdes’s published feed lists 1 bus route, 12 scheduled trips and 33 stops. Its service dates run from 2026-01-01 through 2026-09-27. The published file has not changed since our first check on 2026-07-24.
Top things to fix
Publish the calendar for the current or next service period and set feed_info feed_end_date past it.Likely your export tool
This on-demand service has no published calendar. The last one ended 18 day(s) ago. Between service periods this is normal. But if buses are running with no published calendar, trip planners show nothing.
This one is about the feed as a whole, so there is no share of it to count.
⏱ One export when the next period's schedule is set.worth about +50 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
9 of 33 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 9 of 33 stops, about 27% of them.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +7 points in its category
Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Equal shape distance diff coordinates distance below threshold (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.
⏱ Varies.worth about +6 points in its category
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested 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
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.
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.
Fix 02 · 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.
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 was 18 days ago.
- Published accessibility data
- Accessibility information is stated for 72.7% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- 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 4 kinds of issue across 14 instances (0 error, 14 warning, 0 informational).
This on-demand service's published calendar ended 18 day(s) ago. If the next service period is running, publish its calendar so riders can plan it.
73% of stops state wheelchair accessibility (73% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
73% of stops state accessibility (73% 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 (1).
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.
Fares are applied to trips.
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 33 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.
- 1 (pink)
| Route | Type | Line color |
|---|---|---|
| 1 ligne Arrens-Marsous - Lourdes - Arrens-Marsous | Bus | pink |
List every stop
- Rte d_Azun vers Arrens
- Rte d_Azun vers Lourdes
- Dessus - Mairie
- Le Parc vers Arrens
- Le Parc vers Lourdes
- Argeles - Aire de covoiturage
- Foirail vers Arrens
- Foirail vers Lourdes
- Arrassets vers Arrens
- Arrassets vers Lourdes
- Les Gerbes vers Arrens
- Les Gerbes vers Lourdes
- Arras - Mairie vers Arrens
- Arras - Mairie vers Lourdes
- Office de tourisme
- Aucun - Poste vers Arrens
- Aucun - Poste vers Lourdes
- Las Poueyes
- Ayros - Aire de covoiturage
- Boo-Silhen - Aire de covoiturage
- Bun - Croisement
- Bun - Mairie
- Lavoir
- Rte d_Azun
- Rte de Bun vers Arrens
- Rte de Bun vers Lourdes
- Ger - Aire de covoiturage
- Geu - Aire de covoiturage
- Lourdes - SNCF
- Lourdes - Gare routiere
- Lugagnan - Aire de covoiturage
- Abribus vers Arrens
- Abribus vers Lourdes
Over time
Overall score across the last 14 checks — unchanged since 2026-10-14.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-02 | 77.5 | first check |
| 2026-10-03 | 77.5 | no change |
| 2026-10-04 | 77.5 | no change |
| 2026-10-05 | 77.5 | no change |
| 2026-10-06 | 77.5 | no change |
| 2026-10-07 | 72.2 | down 5.3 |
| 2026-10-08 | 77.5 | up 5.3 |
| 2026-10-09 | 77.5 | no change |
| 2026-10-10 | 77.5 | no change |
| 2026-10-11 | 77.5 | no change |
| 2026-10-12 | 77.5 | no change |
| 2026-10-13 | 77.5 | no change |
| 2026-10-14 | 77.5 | no change |
| 2026-10-15 | 77.5 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-10-02 to 2026-10-15 (14 checks) | 259c19026682 | 2026-09-27 | Current rubric: see the trend above |
| 2026-07-25 to 2026-10-01 (65 checks) | 259c19026682 | 2026-09-27 | C, 77.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-24 | 259c19026682 | 2026-09-27 | A, 90 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
What changed over time
On 2026-10-02 this feed started at grade C. On 2026-10-15 the grade held steady. As of 2026-10-15 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-10-08 Score rose 5 points, correctness rose 12 points.
- 2026-10-07 Score fell 5 points, correctness fell 12 points.
Everything we checked
6 findings, ordered by severity.
Show every finding
- Warning9 instances
Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning9 instances
9 of 33 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 (opens the GTFS Schedule reference on an external site)
- Warning2 instances
Stop has too many matches for shape (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_has_too_many_matches_for_shape' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: stop_has_too_many_matches_for_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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 for stop_too_far_from_shape_using_user_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This on-demand service has no published calendar. The last one ended 18 day(s) ago.
Between service periods this is normal. But if buses are running with no published calendar, trip planners show nothing.
Fix: Publish the calendar for the current or next service period and set feed_info feed_end_date past it. (One export when the next period's schedule is set.)
Finding code: scorecard_intermittent_calendar_ended
Conformance mark Not yet
Two requirements remain for this feed to earn the conformance mark. Service data expired 18 days ago. States wheelchair access on 73% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 18 days ago.
- Accessible Not yet
- States wheelchair access on 73% 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
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 82 / 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 50 / 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 93 / 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.
Similar feeds in Occitanie
Other scorecards in Occitanie, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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-83155/2026-10-15.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-10-15. 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.