Détails de la ressource

Nom du fichier : GTFS-RT trip_updates
Format : gtfs-rt

Cette ressource fait partie du jeu de données Réseau interurbain liO Occitanie.

Disponibilité au téléchargement

09/06/2026
100%
10/06/2026
100%
11/06/2026
100%
12/06/2026
100%
13/06/2026
100%
14/06/2026
100%
15/06/2026
100%
16/06/2026
100%
17/06/2026
100%
18/06/2026
100%
19/06/2026
100%
20/06/2026
100%
21/06/2026
100%
22/06/2026
100%
23/06/2026
100%
24/06/2026
100%
25/06/2026
100%
26/06/2026
100%
27/06/2026
100%
28/06/2026
100%
29/06/2026
100%
30/06/2026
100%
01/07/2026
100%
02/07/2026
100%
03/07/2026
99.6%
04/07/2026
100%
05/07/2026
100%
06/07/2026
100%
07/07/2026
100%
08/07/2026
100%
09/07/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

212 erreurs, 163 avertissements

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

Erreurs

Sequential stop_time_update times are not increasing E022 203 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 379|26403650:T4|7:50:00 stop_sequence 22 arrival_time 09:03:26 (1783494206) is equal to previous stop departure_time 09:03:26 (1783494206) - times must increase between two sequential stops
  • trip_id 369|26530981:T3|8:10:00 stop_sequence 20 arrival_time 09:11:07 (1783494667) is equal to previous stop arrival_time 09:11:07 (1783494667) - times must increase between two sequential stops
  • trip_id 369|26530981:T3|8:10:00 stop_sequence 20 arrival_time 09:11:07 (1783494667) is equal to previous stop departure_time 09:11:07 (1783494667) - times must increase between two sequential stops
  • trip_id 369|26530981:T3|8:10:00 stop_sequence 20 departure_time 09:11:07 (1783494667) is equal to previous stop departure_time 09:11:07 (1783494667) - times must increase between two sequential stops
  • trip_id 369|26530981:T3|8:10:00 stop_sequence 20 departure_time 09:11:07 (1783494667) is equal to previous stop arrival_time 09:11:07 (1783494667) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 7 erreurs

Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time.

Exemples d'erreurs
  • trip_id 121|26403328:T9|7:55:00 stop_sequence 17 departure_time 09:04:18 (1783494258) is less than the same stop arrival_time 09:04:58 (1783494298) - departure time must be equal to or greater than arrival time
  • trip_id 319|26073253:T3|8:10:00 stop_sequence 27 departure_time 09:04:01 (1783494241) is less than the same stop arrival_time 09:04:36 (1783494276) - departure time must be equal to or greater than arrival time
  • trip_id 571|26102431:T2|8:25:00 stop_sequence 8 departure_time 09:04:31 (1783494271) is less than the same stop arrival_time 09:04:50 (1783494290) - departure time must be equal to or greater than arrival time
  • trip_id 720|26597486:T3|8:35:00 stop_sequence 11 departure_time 09:04:33 (1783494273) is less than the same stop arrival_time 09:04:40 (1783494280) - departure time must be equal to or greater than arrival time
  • trip_id 703|26087225:T12|8:45:00 stop_sequence 4 departure_time 09:03:42 (1783494222) is less than the same stop arrival_time 09:04:19 (1783494259) - departure time must be equal to or greater than arrival time

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 2 erreurs

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Exemples d'erreurs
  • GTFS-rt trip_id 457|26185117:T4|8:00:00 stop_sequence 19 has stop_id 0905006 but GTFS stop_sequence 19 has stop_id 0905005 - stop_ids should be the same
  • GTFS-rt trip_id 452|26184862:T1|8:20:00 stop_sequence 23 has stop_id 3101561 but GTFS stop_sequence 23 has stop_id 3101560 - stop_ids should be the same

Avertissements

timestamp not populated W001 163 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id 283|26405917:T1|6:50:00 does not have a timestamp
  • trip_id 452|26185297:T3|7:25:00 does not have a timestamp
  • trip_id 132|24438751:T4|7:30:00 does not have a timestamp
  • trip_id 121|24437896:T4|7:30:00 does not have a timestamp
  • trip_id 932|25607840:T3|7:38:00 does not have a timestamp
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
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 2 233 9 fois (100 % des validations)
E025 Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. 41 9 fois (100 % des validations)
W001 Timestamps should be populated for all elements 1 710 9 fois (100 % des validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 17 8 fois (89 % des validations)
E045 If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt 13 8 fois (89 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 9 3 fois (33 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 64 3 fois (33 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 09/07/2026 à 04h53 Europe/Paris.

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

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

trip_updates

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 09/07/2026 à 04h53 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1783565631" } }