Détails de la ressource

Nom du fichier : Lien vers le GTFS RT DU SAEIV de Lorient Agglomération
Format : gtfs-rt

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

Disponibilité au téléchargement

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

❌799 erreurs, 87 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 21/11/2026 à 08h14 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 1 erreur

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

Exemples d'erreurs
  • trip_id 417490 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 1 erreur

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

Exemples d'erreurs
  • route_id 113 does not exist in the GTFS data routes.txt

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

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

Exemples d'erreurs
  • trip_id 418344 stop_id GE2 does not exist in GTFS data stops.txt
  • trip_id 418343 stop_id GE2 does not exist in GTFS data stops.txt
  • trip_id 417897 stop_id GE2 does not exist in GTFS data stops.txt
  • trip_id 417898 stop_id GE2 does not exist in GTFS data stops.txt
  • trip_id 418673 stop_id GE6 does not exist in GTFS data stops.txt

stop_times_updates not strictly sorted E002 1 erreur

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Exemples d'erreurs
  • trip_id 417823 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 64, 65] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 744 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 418319 stop_sequence 2 arrival_time 08:14:18 (1795245258) is equal to previous stop departure_time 08:14:18 (1795245258) - times must increase between two sequential stops
  • trip_id 418319 stop_sequence 2 departure_time 08:14:18 (1795245258) is equal to previous stop departure_time 08:14:18 (1795245258) - times must increase between two sequential stops
  • trip_id 418319 stop_sequence 3 arrival_time 08:14:18 (1795245258) is equal to previous stop arrival_time 08:14:18 (1795245258) - times must increase between two sequential stops
  • trip_id 418319 stop_sequence 3 arrival_time 08:14:18 (1795245258) is equal to previous stop departure_time 08:14:18 (1795245258) - times must increase between two sequential stops
  • trip_id 418319 stop_sequence 3 departure_time 08:14:18 (1795245258) is equal to previous stop departure_time 08:14:18 (1795245258) - times must increase between two sequential stops

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 22 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 418344 stop_sequence 21 has stop_id GE2 but GTFS stop_sequence 21 has stop_id GE-B - stop_ids should be the same
  • GTFS-rt trip_id 418343 stop_sequence 21 has stop_id GE2 but GTFS stop_sequence 21 has stop_id GE-B - stop_ids should be the same
  • GTFS-rt trip_id 417897 stop_sequence 31 has stop_id GE2 but GTFS stop_sequence 31 has stop_id GE-B - stop_ids should be the same
  • GTFS-rt trip_id 418673 stop_sequence 1 has stop_id GE6 but GTFS stop_sequence 1 has stop_id GE-D - stop_ids should be the same
  • GTFS-rt trip_id 418675 stop_sequence 1 has stop_id GE6 but GTFS stop_sequence 1 has stop_id GE-D - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 2 erreurs

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Exemples d'erreurs
  • GTFS-rt trip_id 418401 contains stop_sequence 39 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 418400 contains stop_sequence 39 that does not exist in GTFS stop_times.txt for this trip

Avertissements

vehicle_id not populated W002 87 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id 417953 does not have a vehicle_id
  • trip_id 417954 does not have a vehicle_id
  • trip_id 418345 does not have a vehicle_id
  • trip_id 418347 does not have a vehicle_id
  • trip_id 418346 does not have a vehicle_id
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
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 100 30 fois (100 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 2 911 30 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 42 28 fois (93 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 28 28 fois (93 % des validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 19 370 28 fois (93 % des validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 47 27 fois (90 % des validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 21 10 fois (33 % des validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 12 6 fois (20 % 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 31 2 fois (7 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 22/11/2026 à 04h07 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 22/11/2026 à 04h07 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

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