Jeu de données ouvert gtfs-rt - Lien vers le GTFS RT DU SAEIV de Lorient Agglomération pour Réseau urbain Izilo

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

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

❌4 233 erreurs, 148 avertissements

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

Erreurs

stop_times_updates not strictly sorted E002 6 erreurs

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

Exemples d'erreurs

trip_id 322744 stop_sequence [1, 2, 3, 4, 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] is not strictly sorted by increasing stop_sequence
trip_id 322683 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, 42, 43, 44, 45, 46, 47, 48, 49] is not strictly sorted by increasing stop_sequence
trip_id 322682 stop_sequence [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, 45, 42] is not strictly sorted by increasing stop_sequence
trip_id 316491 stop_sequence [1, 2, 6, 3] is not strictly sorted by increasing stop_sequence
trip_id 316488 stop_sequence [6, 4] is not strictly sorted by increasing stop_sequence

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 2 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

trip_id 316339 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 322454 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 16 erreurs

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

Exemples d'erreurs

trip_id 325280 stop_id CLAI_EXT does not exist in GTFS data stops.txt
trip_id 325273 stop_id CLAI_EXT does not exist in GTFS data stops.txt
trip_id 325279 stop_id CLAI_EXT does not exist in GTFS data stops.txt
trip_id 325278 stop_id CLAI_EXT does not exist in GTFS data stops.txt
trip_id 325277 stop_id CLAI_EXT does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 4 190 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 320074 stop_sequence 2 arrival_time 08:02:33 (1770966153) is equal to previous stop departure_time 08:02:33 (1770966153) - times must increase between two sequential stops
trip_id 320074 stop_sequence 2 departure_time 08:02:33 (1770966153) is equal to previous stop departure_time 08:02:33 (1770966153) - times must increase between two sequential stops
trip_id 320074 stop_sequence 3 arrival_time 08:02:33 (1770966153) is equal to previous stop arrival_time 08:02:33 (1770966153) - times must increase between two sequential stops
trip_id 320074 stop_sequence 3 arrival_time 08:02:33 (1770966153) is equal to previous stop departure_time 08:02:33 (1770966153) - times must increase between two sequential stops
trip_id 320074 stop_sequence 3 departure_time 08:02:33 (1770966153) is equal to previous stop departure_time 08:02:33 (1770966153) - times must increase between two sequential stops

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 381682 stop_sequence 18 has stop_id CESG but GTFS stop_sequence 18 has stop_id COUP - stop_ids should be the same
GTFS-rt trip_id 381682 stop_sequence 19 has stop_id EJPP but GTFS stop_sequence 19 has stop_id CESG - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 16 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 325280 contains stop_sequence 43 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 325273 contains stop_sequence 43 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 325279 contains stop_sequence 43 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 325278 contains stop_sequence 43 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 325277 contains stop_sequence 43 that does not exist in GTFS stop_times.txt for this trip

Avertissements

vehicle_id not populated W002 148 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id 322384 does not have a vehicle_id
trip_id 320074 does not have a vehicle_id
trip_id 316451 does not have a vehicle_id
trip_id 316450 does not have a vehicle_id
trip_id 320066 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	415	29 fois (100 % des validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	347	29 fois (100 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	3 278	29 fois (100 % des validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	125	25 fois (86 % des validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	61	25 fois (86 % des validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	25	25 fois (86 % des validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	101 169	25 fois (86 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	32	17 fois (59 % 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	123	16 fois (55 % des validations)

Contenu du flux GTFS-RT

Entités

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


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