Feed status · checked 2026-07-19
TLP (Tarbes-Lourdes)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Occitanie, 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.2, validator 8.0.1.
Checked for changes 61 minutes ago; last changed 5 hours ago.
Measured 3 of 4 score categories from the agency's own feed.
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 agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export with a validity window that reaches at least 60 days out.Likely your export tool
Service data runs out in 21 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
⏱ One export setting.worth about +59 points in its category
Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 points in its category
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
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.
Re-export with a validity window that reaches at least 60 days out. · 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.
Review the rule documentation for 'trip_distance_exceeds_shape_distance' 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.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · 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 21 days.
- Published accessibility data
- Accessibility information is stated for 100% 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.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 10 kinds of issue across 2469 instances (12 error, 2456 warning, 1 informational).
Service data runs out in 21 day(s). Publish an updated feed soon or riders will lose trip planning.
100% of stops state wheelchair accessibility (2% marked accessible, 98% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
100% of stops state accessibility (2% 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 (T2, T4, T6).
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 ("Saint Joseph / Grotte", "Saint Joseph / Grotte").
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.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- AERO (orange)
- L1 (red)
- L2 (orange)
- L3 (yellow)
- L4 (pink)
- L5 (purple)
- NCV (brown)
- SPEM (purple)
- T1 (red)
- T10 (gray)
- T11 (gray)
- T12 (green)
- T13 (green)
- T2 (pink)
- T3 (orange)
- T4 (teal)
- T5 (teal)
- T6 (teal)
- T7 (white)
- T8 (gray)
- T9 (gray)
- TL (yellow)
| Route | Type | Line color |
|---|---|---|
| AERO Navette aéroport | Bus | orange |
| L1 Route de Julos <> Ophite | Bus | red |
| L2 Gare Routière <> Poueyferré/Lac | Bus | orange |
| L3 Cabicoun<>Lourdes-Gare Routière | Bus | yellow |
| L4 Saint Joseph / Grotte | Bus | pink |
| L5 Cœur de Lourdes | Bus | purple |
| NCV Navettes Centre-ville | Bus | brown |
| SPEM Spécial Marché | Bus | purple |
| T1 Hôpital <> Ibos | Bus | red |
| T10 Odos <> Verdun | Bus | gray |
| T11 Orleix / Bours <> Verdun | Bus | gray |
| T12 Barbazan-Debat <> Verdun | Bus | green |
| T13 Laloubère - Mairie <> Verdun | Bus | green |
| T2 Université <> Laubadère | Bus | pink |
| T3 Bazet - Mairie <> Bastillac | Bus | orange |
| T4 Parc des Expos <> Château d'Urac | Bus | teal |
| T5 Bordères - Pyrénées <> Verdun | Bus | teal |
| T6 Lauriers <> Verdun | Bus | teal |
| T7 Aéroport <> Tarbes - Gare SNCF | Bus | white |
| T8 Séméac - Piscine <> Verdun | Bus | gray |
| T9 Aureilhan - Aubépine <> Verdun | Bus | gray |
| TL Lourdes <>Tarbes | Bus | yellow |
This feed has 605 stops.
List every stop
- Chapelle
- Chapelle
- Hippolyte
- Hippolyte
- Aureilhan - Alouettes
- Aureilhan - Alouettes
- Aureilhan - Aubépine
- Aureilhan - Aubépine
- Batan
- Batan
- Beaugency
- Beaugency
- Blum
- Blum
- Cèdres
- Cèdres
- Chambord
- Chambord
- Aureilhan - Cimetière
- Aureilhan - Cimetière
- Clairière
- Chartreuse
- Chartreuse
- ECLA
- ECLA
- Eglantine
- Florence
- Florence
- Floréal
- Floréal
- Gautier
- Halley
- Halley
- Aureilhan - Mairie
- Aureilhan - Mairie
- Aureilhan - Maison de retraite
- Aureilhan - Maison de retraite
- Aureilhan - Maison de retraite
- Michel
- Michel
- Moisson
- Moisson
- Montagna
- Montagna
- Le Moulin
- Le Moulin
- Aureilhan - Poste
- Aureilhan - Poste
- Roussel
- Roussel
- Roy
- Roy
- Saint-Jean
- Saint-Jean
- Tuilerie
- Tuilerie
- Voltaire
- Cassoulet
- Coquelicots
- Barbazan - Ecole
- Barbazan - Eglise
- Jonquilles
- Bazet - Mairie
- Rosiers
- Rosiers
- Route Bordeaux
- Route de Bordeaux
- Bordères - Pyrénées
- Route Bours
- Route Bours
- Campagnole
- Croizat
- ESAT
- France
- Gayolles
- Jaurès
- Jaurès
- Liberté
- Oussouet
- Paix
- Peyrade
- Pibeste
- Résistance
- Rousseau
- Saint-Laurent
- Sémard
- Sémard
- Tailhade
- Thorez
- Château d'Urac
- Château d'Urac
- Cantères
- Bours - Ecole
- Levant
- Levant
- Loubery
- Bours - Mairie
- Bours - Mairie
- Bas du Pouey
- Bas du Pouey
- Bergos
- Bergos
- Buala
- Buala
- Covoiturage - Ouest
- Haut du Pouey
- Haut du Pouey
- Herran
- Herran
- Isaby
- Ibos - Mairie
- Ibos - Méridien
- Le Parvis
- Passade
- Pradet
- Route de Juillan
- Route de Juillan
- ZAC Pyrénées
- ZAC Pyrénées
- Aéroport - Pyrène
- Aéroport - Pyrène
- Juillan - Ecole
- Juillan - Ecole
- Geune
- Geune
- Juillan - Halle
- Juillan - Intermarché
- Juillan - Intermarché
- Juillan - Mairie
- Morane
- Morane
- Route de Lourdes
- Route de Lourdes
- Agriculture
- Bousquet
- Bousquet
- Graouette
- Graouette
- Hippodrome
- Hippodrome
- Laque
- Laque
- Laloubère - Mairie
- Laloubère - Mairie
- Mermoz
- Plein Sud
- Plein Sud
- Laloubère - Zone Commerciale
- Biscaye - Centre aéré
- Biscaye - Centre aéré
- Alba
- Anclades
- Anclades
- Anclades - Ecole
- Anclades - Ecole
- Arrouza Parking
- Arrouza Parking
- Arriouet
- Arriouet
- Arrouza
- Astazou
- Route de Bagnères
- Route de Bagnères
- Barrière
- Barrière
- Biscaye - Châlet
- Biscaye - Châlet
- Béout
- Béout
- Bretagne
- Cabicoun
- Cabicoun
- Cachot
- Camping de la Forêt
- Lourdes Carel
- Lourdes Carel
- Cazenave
- Châlets
- Châlets
- Cire
- Cité Saint-Pierre
- Cité Saint-Pierre
- Chemin du lac
- Chemin du Lac
- Coustète
- Coustète
- Crabère
- Crabère
- Chantecler
- Saint-Exupéry
- Saint-Exupéry
- Foch
- Fronton
- Fronton
- Lourdes - Gendarmerie
- Lourdes - Gendarmerie
- Lourdes - Gare Routière
- Lourdes - Gare Routière
- Lourdes - Gare SNCF
- Lourdes - Gare SNCF
- Halles - Office de tourisme
- Halles - Office de tourisme
- Lourdes - Hôpital
- Lourdes - Hôpital
- Jardins
- Jardins
- Jeanne d'Arc - Paternelle
- Saint Joseph / Grotte
- Saint Joseph / Grotte
- Labastide
- Lac de Lourdes
- Lannedarré
- Lannedarré
- Lapacca
- Lapacca
- Lourdes Callet
- Lourdes Callet
- Lourdes - Lidl
- Lourdes - Lidl
- Lourdes - Leclerc
- Lourdes - Leclerc
- Lourdes - Leclerc Sud
- Camping du Loup
- Lapacca - Parking
- Lapacca - Parking
- Lycée Sarsan
- Lycée Sarsan
- Lourdes - Mac Donald's
- Lourdes - Mac Donald's
- Madeleine
- Madeleine
- Marcadal
- Marcadal
- Massabielle
- Massabielle
- Matisse
- Mercure
- Lourdes - Carrefour Market
- Mont Clair
- Moulin du Monge
- Moulin du Monge
- Ophite
- Paradis
- Paradis
- Rue de Pau
- Rue de Pau
- Pic du Jer
- Pic du Jer
- Lourdes - Piscine
- Lourdes - Piscine
- and 355 more (see the full list on the map or in the GeoJSON)
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
- Error12 instances
Trip distance exceeds shape distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1593 instances
Some route lines list the same point twice in a row.
Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)
Validator rule: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning632 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Validator rule: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning124 instances
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.)
Validator rule: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning81 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.)
Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning22 instances
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.)
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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.)
Validator rule: mixed_case_recommended_field · 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.)
Validator rule: missing_recommended_file · 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.)
Validator rule: 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
Service data runs out in 21 day(s).
When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Validator rule: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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.)
Validator rule: 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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
Future calendar (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: future_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: 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
This feed is close to the conformance mark. 1 validator error to resolve. Service data runs out in 21 days; renew to qualify.
- Valid Not yet
- 1 validator error to resolve.
- Current Not yet
- Service data runs out in 21 days; renew to qualify.
- Accessible Met
- States wheelchair access on 100% of stops and 100% of trips.
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.
At risk for the Google and Apple Maps four-week coverage bar. This feed has 21 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar. The feed also carries 12 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 32 / 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 20 / 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 77 / 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/tlp-tarbes-lourdes/2026-07-19.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-07-19. 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.