Détails de la ressource

Nom du fichier : Base de données multimodale des horaires aux arrêts des réseaux de transport public normands en temps réel
Format : gtfs-rt

La base de données multimodale présente de manière agrégée les horaires et les arrêts des réseaux de transport public normands en temps réel. Elle est le support du calculateur d’itinéraires Atoumod.fr, piloté par le Syndicat mixte Atoumod.

Cette ressource fait partie du jeu de données Agrégat des réseaux urbains et interurbains de Normandie.

Disponibilité au téléchargement

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

22 946 erreurs, 2 334 avertissements

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

Erreurs

stop_times_updates not strictly sorted E002 516 erreurs

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

Exemples d'erreurs
  • trip_id ATOUMOD012:ServiceJourney:300000387:LOC stop_sequence [15, 5] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD005:ServiceJourney:201:LOC stop_sequence [1, 28, 33, 23] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD006:ServiceJourney:7x1470488:LOC stop_sequence [8, 17, 13] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD001:ServiceJourney:TAEx7003:LOC stop_sequence [27, 22] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD001:ServiceJourney:TAEx1006:LOC stop_sequence [13, 18, 10] 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 25 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 ATOUMOD005:ServiceJourney:107:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD036:ServiceJourney:4819710769102848x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD036:ServiceJourney:5198893567442944x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD036:ServiceJourney:6676591728918528x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD036:ServiceJourney:4943586962440192x0:LOC 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 25 erreurs

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

Exemples d'erreurs
  • route_id ATOUMOD005:Line:500:LOC does not exist in the GTFS data routes.txt
  • route_id ATOUMOD036:Line:5466936700829696:LOC does not exist in the GTFS data routes.txt
  • route_id ATOUMOD036:Line:5229274752614400:LOC does not exist in the GTFS data routes.txt
  • route_id ATOUMOD036:Line:5326622602297344:LOC does not exist in the GTFS data routes.txt
  • route_id ATOUMOD036:Line:6704313154928640:LOC does not exist in the GTFS data routes.txt

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

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

Exemples d'erreurs
  • trip_id ATOUMOD005:ServiceJourney:107:LOC stop_id FR:76217:ZE:18030:ATOUMOD005 does not exist in GTFS data stops.txt
  • trip_id ATOUMOD005:ServiceJourney:107:LOC stop_id FR:76217:ZE:18246:ATOUMOD005 does not exist in GTFS data stops.txt
  • trip_id ATOUMOD005:ServiceJourney:107:LOC stop_id FR:76545:ZE:18225:ATOUMOD005 does not exist in GTFS data stops.txt
  • trip_id ATOUMOD005:ServiceJourney:107:LOC stop_id FR:76545:ZE:18215:ATOUMOD005 does not exist in GTFS data stops.txt
  • trip_id ATOUMOD005:ServiceJourney:107:LOC stop_id FR:76545:ZE:18014:ATOUMOD005 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 20 763 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 ATOUMOD012:ServiceJourney:300000387:LOC stop_sequence 5 arrival_time 08:08:30 (1768806510) is less than previous stop arrival_time 08:29:30 (1768807770) - times must increase between two sequential stops
  • trip_id ATOUMOD012:ServiceJourney:300000387:LOC stop_sequence 5 arrival_time 08:08:30 (1768806510) is less than previous stop departure_time 08:29:30 (1768807770) - times must increase between two sequential stops
  • trip_id ATOUMOD012:ServiceJourney:300000387:LOC stop_sequence 5 departure_time 08:08:30 (1768806510) is less than previous stop departure_time 08:29:30 (1768807770) - times must increase between two sequential stops
  • trip_id ATOUMOD012:ServiceJourney:300000387:LOC stop_sequence 5 departure_time 08:08:30 (1768806510) is less than previous stop arrival_time 08:29:30 (1768807770) - times must increase between two sequential stops
  • trip_id ATOUMOD012:ServiceJourney:300000387:LOC stop_sequence 8 arrival_time 08:14:30 (1768806870) is less than previous stop arrival_time 08:21:30 (1768807290) - times must increase between two sequential stops

trip direction_id does not match GTFS data E024 753 erreurs

GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt

Exemples d'erreurs
  • GTFS-rt trip_id ATOUMOD012:ServiceJourney:300000387:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
  • GTFS-rt trip_id ATOUMOD005:ServiceJourney:201:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
  • GTFS-rt trip_id ATOUMOD006:ServiceJourney:7x1470488:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
  • GTFS-rt trip_id ATOUMOD001:ServiceJourney:TAEx7003:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
  • GTFS-rt trip_id ATOUMOD001:ServiceJourney:TAEx1006:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match

Sequential stop_time_updates have the same stop_id E037 1 erreur

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Exemples d'erreurs
  • trip_id ATOUMOD036:ServiceJourney:6566385116250112x0:LOC has repeating stop_id FR:14431:ZE:5975052756451328:ATOUMOD036 at stop_sequence 1 - sequential stop_ids should be different

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 147 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 ATOUMOD003:ServiceJourney:4011337x2025x26xGSemHLiaxSemainex02:LOC stop_sequence 29 has stop_id FR:76351:ZE:3666:ATOUMOD003 but GTFS stop_sequence 29 has stop_id FR:76351:ZE:3690:ATOUMOD003 - stop_ids should be the same
  • GTFS-rt trip_id ATOUMOD003:ServiceJourney:4011337x2025x26xGSemHLiaxSemainex02:LOC stop_sequence 32 has stop_id FR:76351:ZE:3506:ATOUMOD003 but GTFS stop_sequence 32 has stop_id FR:76351:ZE:3381:ATOUMOD003 - stop_ids should be the same
  • GTFS-rt trip_id ATOUMOD036:ServiceJourney:5772306824560640x1:LOC stop_sequence 14 has stop_id FR:14366:ZE:19270005:ATOUMOD036 but GTFS stop_sequence 14 has stop_id FR:14366:ZE:658330001:ATOUMOD036 - stop_ids should be the same
  • GTFS-rt trip_id ATOUMOD003:ServiceJourney:4230667x2025x26xGSemHLiaxSemainex02:LOC stop_sequence 25 has stop_id FR:76351:ZE:5183:ATOUMOD003 but GTFS stop_sequence 25 has stop_id FR:76351:ZE:3200:ATOUMOD003 - stop_ids should be the same
  • GTFS-rt trip_id ATOUMOD003:ServiceJourney:4230667x2025x26xGSemHLiaxSemainex02:LOC stop_sequence 34 has stop_id FR:76351:ZE:3386:ATOUMOD003 but GTFS stop_sequence 34 has stop_id FR:76351:ZE:3047:ATOUMOD003 - stop_ids should be the same

timestamp is in the future E050 1 erreur

All timestamps must be less than the current time

Exemples d'erreurs
  • header.timestamp 08:01:43 (1768806103) is 1 min 14 sec greater than 08:00:28 (1768806028410) - the current time in milliseconds

GTFS-rt stop_sequence not found in GTFS data E051 591 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 ATOUMOD012:ServiceJourney:300000387:LOC contains stop_sequence 5 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD005:ServiceJourney:201:LOC contains stop_sequence 23 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD006:ServiceJourney:7x1470488:LOC contains stop_sequence 13 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD001:ServiceJourney:TAEx7003:LOC contains stop_sequence 22 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD001:ServiceJourney:TAEx1006:LOC contains stop_sequence 10 that does not exist in GTFS stop_times.txt for this trip

Avertissements

vehicle_id not populated W002 778 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id ATOUMOD012:ServiceJourney:300000387:LOC does not have a vehicle_id
  • trip_id ATOUMOD005:ServiceJourney:201:LOC does not have a vehicle_id
  • trip_id ATOUMOD006:ServiceJourney:7x1470488:LOC does not have a vehicle_id
  • trip_id ATOUMOD001:ServiceJourney:TAEx7003:LOC does not have a vehicle_id
  • trip_id ATOUMOD001:ServiceJourney:TAEx1006:LOC does not have a vehicle_id

schedule_relationship not populated W009 1 556 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs
  • trip_id ATOUMOD012:ServiceJourney:300000387:LOC stop_sequence 15 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD012:ServiceJourney:300000387:LOC does not have a schedule_relationship
  • trip_id ATOUMOD005:ServiceJourney:201:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD005:ServiceJourney:201:LOC does not have a schedule_relationship
  • trip_id ATOUMOD006:ServiceJourney:7x1470488:LOC stop_sequence 8 (and potentially more for this trip) does not have a schedule_relationship
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
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 10 506 26 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. 437 869 26 fois (100 % des validations)
E024 GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt 11 440 26 fois (100 % 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 2 479 26 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 8 385 26 fois (100 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 13 178 26 fois (100 % des validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 26 317 26 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. 167 24 fois (92 % des validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 1 730 19 fois (73 % des validations)
E040 All stop_time_updates must contain stop_id or stop_sequence - both fields cannot be left blank 132 18 fois (69 % des validations)
E043 If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided 132 18 fois (69 % des validations)
E050 All timestamps must be less than the current time 13 13 fois (50 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 750 9 fois (35 % des validations)
E035 The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt 15 8 fois (31 % des validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 19 8 fois (31 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 146 7 fois (27 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 20/01/2026 à 01h52 Europe/Paris.

trip_updates (2) vehicle_positions (0) service_alerts (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 20/01/2026 à 01h52 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

{ "entity": [ { "id": "SM:ATOUMOD001:ServiceJourney:TCARx4790:LOC", "tripUpdate": { "stopTimeUpdate": [ { "departure": { "time": "1768869300" }, "stopId": "FR:76451:ZE:TCARxMTMAL1:ATOUMOD001", "stopSequence": 1 }, { "arrival": { "time": "1768869393" }, "departure": { "time": "1768869393" }, "stopId": "FR:76451:ZE:TCARxCBLBE1:ATOUMOD001", "stopSequence": 3 }, { "arrival": { "time": "1768870264" }, "departure": { "time": "1768870264" }, "stopId": "FR:76540:ZE:TCARxPMARC1:ATOUMOD001", "stopSequence": 13 }, { "arrival": { "time": "1768870195" }, "departure": { "time": "1768870195" }, "stopId": "FR:76540:ZE:TCARxREPUB1:ATOUMOD001", "stopSequence": 12 }, { "arrival": { "time": "1768869485" }, "departure": { "time": "1768869485" }, "stopId": "FR:76451:ZE:TCARxCAMPU1:ATOUMOD001", "stopSequence": 4 }, { "arrival": { "time": "1768869316" }, "departure": { "time": "1768869316" }, "stopId": "FR:76451:ZE:TCARxCOQUE1:ATOUMOD001", "stopSequence": 2 }, { "arrival": { "time": "1768870444" }, "stopId": "FR:76540:ZE:TCARxCHRUT1:ATOUMOD001", "stopSequence": 15 }, { "arrival": { "time": "1768870140" }, "departure": { "time": "1768870140" }, "stopId": "FR:76540:ZE:TCARxCATHE1:ATOUMOD001", "stopSequence": 11 }, { "arrival": { "time": "1768870320" }, "departure": { "time": "1768870320" }, "stopId": "FR:76540:ZE:TCARxMARTT1:ATOUMOD001", "stopSequence": 14 }, { "arrival": { "time": "1768869662" }, "departure": { "time": "1768869662" }, "stopId": "FR:76540:ZE:TCARxFDVAL1:ATOUMOD001", "stopSequence": 5 }, { "arrival": { "time": "1768870093" }, "departure": { "time": "1768870093" }, "stopId": "FR:76540:ZE:TCARxTARTT1:ATOUMOD001", "stopSequence": 10 } ], "timestamp": "1768869266", "trip": { "directionId": 1, "routeId": "ATOUMOD001:Line:TCARx91:LOC", "tripId": "ATOUMOD001:ServiceJourney:TCARx4790:LOC" } } }, { "id": "SM:ATOUMOD001:ServiceJourney:TCARx4791:LOC", "tripUpdate": { "stopTimeUpdate": [ { "departure": { "time": "1768871190" }, "stopId": "FR:76451:ZE:TCARxMTMAL1:ATOUMOD001", "stopSequence": 1 }, { "arrival": { "time": "1768872241" }, "departure": { "time": "1768872241" }, "stopId": "FR:76540:ZE:TCARxMARTT1:ATOUMOD001", "stopSequence": 14 }, { "arrival": { "time": "1768871367" }, "departure": { "time": "1768871367" }, "stopId": "FR:76451:ZE:TCARxCAMPU1:ATOUMOD001", "stopSequence": 4 }, { "arrival": { "time": "1768872184" }, "departure": { "time": "1768872184" }, "stopId": "FR:76540:ZE:TCARxPMARC1:ATOUMOD001", "stopSequence": 13 }, { "arrival": { "time": "1768871244" }, "departure": { "time": "1768871244" }, "stopId": "FR:76451:ZE:TCARxCOQUE1:ATOUMOD001", "stopSequence": 2 }, { "arrival": { "time": "1768871610" }, "departure": { "time": "1768871610" }, "stopId": "FR:76540:ZE:TCARxFDVAL1:ATOUMOD001", "stopSequence": 5 }, { "arrival": { "time": "1768872049" }, "departure": { "time": "1768872049" }, "stopId": "FR:76540:ZE:TCARxCATHE1:ATOUMOD001", "stopSequence": 11 }, { "arrival": { "time": "1768872120" }, "departure": { "time": "1768872120" }, "stopId": "FR:76540:ZE:TCARxREPUB1:ATOUMOD001", "stopSequence": 12 }, { "arrival": { "time": "1768871310" }, "departure": { "time": "1768871310" }, "stopId": "FR:76451:ZE:TCARxCBLBE1:ATOUMOD001", "stopSequence": 3 }, { "arrival": { "time": "1768872361" }, "stopId": "FR:76540:ZE:TCARxCHRUT1:ATOUMOD001", "stopSequence": 15 }, { "arrival": { "time": "1768872000" }, "departure": { "time": "1768872000" }, "stopId": "FR:76540:ZE:TCARxTARTT1:ATOUMOD001", "stopSequence": 10 } ], "timestamp": "1768870186", "trip": { "directionId": 1, "routeId": "ATOUMOD001:Line:TCARx91:LOC", "tripId": "ATOUMOD001:ServiceJourney:TCARx4791:LOC" } } } ], "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1768870331" } }