Détails de la ressource

Nom du fichier : Horaires temps-réel du réseau Tarbes / Lourdes - TLP mobilités (GTFS / GTFS-RT)
Format : gtfs-rt

Les données horaires correspondent à l’ensemble de l’offre du réseau TLP Mobilités : les horaires de l’ensemble des lignes commerciales et les informations géographiques associées (topographie du réseau).

Cette ressource fait partie du jeu de données Réseau urbain TLP.

Disponibilité au téléchargement

16/04/2026
99.2%
17/04/2026
100%
18/04/2026
100%
19/04/2026
100%
20/04/2026
100%
21/04/2026
99.3%
22/04/2026
100%
23/04/2026
99.1%
24/04/2026
99.3%
25/04/2026
100%
26/04/2026
100%
27/04/2026
100%
28/04/2026
100%
29/04/2026
100%
30/04/2026
100%
01/05/2026
100%
02/05/2026
100%
03/05/2026
100%
04/05/2026
100%
05/05/2026
100%
06/05/2026
100%
07/05/2026
100%
08/05/2026
100%
09/05/2026
100%
10/05/2026
100%
11/05/2026
100%
12/05/2026
100%
13/05/2026
100%
14/05/2026
100%
15/05/2026
100%
16/05/2026
100%
En savoir plus
Nous testons la disponibilité de cette ressource au téléchargement toutes les heures, en effectuant une requête HTTP de type HEAD dont le temps de réponse doit être inférieur à 5 secondes. Si nous détectons une indisponibilité, nous effectuons un nouveau test toutes les 10 minutes, jusqu'à ce que la ressource soit à nouveau disponible.

Pour les flux SIRI et SIRI Lite, nous effectuons une requête HTTP de type GET : nous considérons une réponse avec un code 401 ou 405 comme étant disponible. En cas d'erreur 500, nous considèrerons que le flux est indisponible, sauf si il semble contenir du SOAP.

Rapport de validation

746 erreurs, 2 avertissements

De nombreuses erreurs de validation indiquent que les identifiants du GTFS-RT ne correspondent pas aux identifiants du GTFS.

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 13/05/2026 à 09h14 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 59 erreurs

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Exemples d'erreurs
  • vehicle_id zenbus:Vehicle:887170002:LOC trip_id 4896235301371904:2 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 4896235301371904:2 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id zenbus:Vehicle:889210002:LOC trip_id 6579177173024768:2 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 6579177173024768:2 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id zenbus:Vehicle:899870002:LOC trip_id 4883101030285312:2 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 59 erreurs

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Exemples d'erreurs
  • vehicle_id zenbus:Vehicle:887170002:LOC route_id zenbus:Line:860950003:LOC does not exist in the GTFS data routes.txt
  • route_id zenbus:Line:860950003:LOC does not exist in the GTFS data routes.txt
  • vehicle_id zenbus:Vehicle:889210002:LOC route_id zenbus:Line:855090008:LOC does not exist in the GTFS data routes.txt
  • route_id zenbus:Line:855090008:LOC does not exist in the GTFS data routes.txt
  • vehicle_id zenbus:Vehicle:899870002:LOC route_id zenbus:Line:853230005:LOC does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 518 erreurs

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Exemples d'erreurs
  • vehicle_id zenbus:Vehicle:887170002:LOC stop_id zenbus:StopPoint:SP:717220021:LOC does not exist in GTFS data stops.txt
  • trip_id 4896235301371904:2 stop_id zenbus:StopPoint:SP:892890008:LOC does not exist in GTFS data stops.txt
  • trip_id 4896235301371904:2 stop_id zenbus:StopPoint:SP:717220021:LOC does not exist in GTFS data stops.txt
  • trip_id 4896235301371904:2 stop_id zenbus:StopPoint:SP:713360020:LOC does not exist in GTFS data stops.txt
  • trip_id 4896235301371904:2 stop_id zenbus:StopPoint:SP:715300018:LOC does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 110 erreurs

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Exemples d'erreurs
  • trip_id 4896235301371904:2 stop_sequence 13 arrival_time 09:21:24 (1778656884) is less than previous stop departure_time 09:21:25 (1778656885) - times must increase between two sequential stops
  • trip_id 4896235301371904:2 stop_sequence 14 arrival_time 09:22:20 (1778656940) is less than previous stop departure_time 09:22:47 (1778656967) - times must increase between two sequential stops
  • trip_id 4896235301371904:2 stop_sequence 15 arrival_time 09:24:09 (1778657049) is less than previous stop departure_time 09:24:15 (1778657055) - times must increase between two sequential stops
  • trip_id 4896235301371904:2 stop_sequence 17 arrival_time 09:27:59 (1778657279) is less than previous stop departure_time 09:28:26 (1778657306) - times must increase between two sequential stops
  • trip_id 6579177173024768:2 stop_sequence 21 arrival_time 09:28:41 (1778657321) is less than previous stop departure_time 09:29:07 (1778657347) - times must increase between two sequential stops

Avertissements

vehicle_id not populated W002 1 erreur

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id 898170002:6 does not have a vehicle_id

ID in one feed missing from the other W003 1 erreur

a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed

Exemples d'erreurs
  • trip_id 898170002:6 is in TripUpdates but not in VehiclePositions feed
Valider ce GTFS-RT maintenant

Validations précédentes

Voici un récapitulatif des différents types d'erreurs constatés au cours des 30 derniers jours.

Identifiant d'erreur Description Nombre d'erreurs Nombre d'occurences
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 1 140 27 fois (100 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 1 140 27 fois (100 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 8 232 27 fois (100 % des validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 1 812 27 fois (100 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 42 19 fois (70 % des validations)
W003 a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed 42 19 fois (70 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 16/05/2026 à 23h40 Europe/Paris.

vehicle_positions (1) trip_updates (1) service_alerts (0)

Entités présentes dans ce flux lors des 7 derniers jours.

trip_updates vehicle_positions

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 16/05/2026 à 23h40 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

{ "entity": [ { "id": "zenbus:Vehicle:899870002:LOC", "vehicle": { "currentStopSequence": 19, "occupancyStatus": "EMPTY", "position": { "latitude": 43.119361877441406, "longitude": -0.0302910003811121 }, "stopId": "zenbus:StopPoint:SP:5187458056585216:LOC", "timestamp": "1778949950", "trip": { "routeId": "zenbus:Line:853230005:LOC", "scheduleRelationship": "SCHEDULED", "startDate": "20260516", "startTime": "18:25:00", "tripId": "4809460712210432:11" }, "vehicle": { "id": "zenbus:Vehicle:899870002:LOC" } } }, { "id": "20260516:4892840904622080:11", "tripUpdate": { "stopTimeUpdate": [ { "scheduleRelationship": "SKIPPED", "stopId": "zenbus:StopPoint:SP:894910010:LOC", "stopSequence": 17 }, { "scheduleRelationship": "SKIPPED", "stopId": "zenbus:StopPoint:SP:723100022:LOC", "stopSequence": 18 }, { "arrival": { "time": "1778956663" }, "departure": { "time": "1778956673" }, "stopId": "zenbus:StopPoint:SP:5187458056585216:LOC", "stopSequence": 19 }, { "arrival": { "time": "1778956722" }, "departure": { "time": "1778956732" }, "stopId": "zenbus:StopPoint:SP:5203689979510784:LOC", "stopSequence": 20 }, { "arrival": { "time": "1778956765" }, "departure": { "time": "1778956775" }, "stopId": "zenbus:StopPoint:SP:896930011:LOC", "stopSequence": 21 } ], "timestamp": "1778956542", "trip": { "routeId": "zenbus:Line:853230005:LOC", "scheduleRelationship": "SCHEDULED", "startDate": "20260516", "startTime": "18:25:00", "tripId": "4809460712210432:11" }, "vehicle": { "id": "zenbus:Vehicle:899870002:LOC" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1778967628" } }