transport.data.gouv.fr transport.data.gouv.fr

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
Télécharger

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

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

❌12 892 erreurs, 900 avertissements

Les shapes présentes dans le GTFS ont été ignorées, certaines règles de validation n'ont pas été vérifiées.

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 08/11/2025 à 08h11 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

stop_times_updates not strictly sorted E002 258 erreurs

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

Exemples d'erreurs
  • trip_id ATOUMOD035:ServiceJourney:3746565x2025xHxMultxSamxSamedix00:LOC stop_sequence [12, 28, 39, 25] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD003:ServiceJourney:4062504x2025x26xGSamHTNIxSamedix00:LOC stop_sequence [16, 31, 20] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD035:ServiceJourney:3747726x2025xHxMultxSamxSamedix00:LOC stop_sequence [21, 32, 33, 7] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD005:ServiceJourney:963:LOC stop_sequence [15, 12] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD035:ServiceJourney:3747774x2025xHxMultxSamxSamedix00:LOC stop_sequence [27, 32, 8] 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 38 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:530:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD005:ServiceJourney:412:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD105:ServiceJourney:5265030141444096x2:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD005:ServiceJourney:266:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id ATOUMOD005:ServiceJourney:474:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED

Sequential stop_time_update times are not increasing E022 11 942 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 ATOUMOD035:ServiceJourney:3746565x2025xHxMultxSamxSamedix00:LOC stop_sequence 25 arrival_time 06:17:46 (1762579066) is less than previous stop arrival_time 06:37:18 (1762580238) - times must increase between two sequential stops
  • trip_id ATOUMOD035:ServiceJourney:3746565x2025xHxMultxSamxSamedix00:LOC stop_sequence 25 arrival_time 06:17:46 (1762579066) is less than previous stop departure_time 06:37:30 (1762580250) - times must increase between two sequential stops
  • trip_id ATOUMOD035:ServiceJourney:3746565x2025xHxMultxSamxSamedix00:LOC stop_sequence 25 departure_time 06:19:33 (1762579173) is less than previous stop departure_time 06:37:30 (1762580250) - times must increase between two sequential stops
  • trip_id ATOUMOD035:ServiceJourney:3746565x2025xHxMultxSamxSamedix00:LOC stop_sequence 25 departure_time 06:19:33 (1762579173) is less than previous stop arrival_time 06:37:18 (1762580238) - times must increase between two sequential stops
  • trip_id ATOUMOD035:ServiceJourney:3746565x2025xHxMultxSamxSamedix00:LOC stop_sequence 22 arrival_time 06:14:00 (1762578840) is less than previous stop arrival_time 06:17:46 (1762579066) - times must increase between two sequential stops

trip direction_id does not match GTFS data E024 255 erreurs

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

Exemples d'erreurs
  • GTFS-rt trip_id ATOUMOD035:ServiceJourney:3746565x2025xHxMultxSamxSamedix00:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
  • GTFS-rt trip_id ATOUMOD003:ServiceJourney:4062504x2025x26xGSamHTNIxSamedix00:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
  • GTFS-rt trip_id ATOUMOD035:ServiceJourney:3747726x2025xHxMultxSamxSamedix00:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
  • GTFS-rt trip_id ATOUMOD005:ServiceJourney:963:LOC trip.direction_id is 2 but GTFS trip.direction_id is 0 - direction_id does not match
  • GTFS-rt trip_id ATOUMOD003:ServiceJourney:4155777x2025x26xGSamHTNIxSamedix00:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match

stop_time_update departure time is before arrival time E025 5 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 ATOUMOD035:ServiceJourney:3747730x2025xHxMultxSamxSamedix00:LOC stop_sequence 26 departure_time 08:04:00 (1762585440) is less than the same stop arrival_time 08:08:44 (1762585724) - departure time must be equal to or greater than arrival time
  • trip_id ATOUMOD035:ServiceJourney:3758119x2025xHxMultxSamxSamedix00x0000010:LOC stop_sequence 22 departure_time 08:07:53 (1762585673) is less than the same stop arrival_time 08:07:56 (1762585676) - departure time must be equal to or greater than arrival time
  • trip_id ATOUMOD035:ServiceJourney:3746612x2025xHxMultxSamxSamedix00:LOC stop_sequence 3 departure_time 05:43:00 (1762576980) is less than the same stop arrival_time 05:43:06 (1762576986) - departure time must be equal to or greater than arrival time
  • trip_id ATOUMOD035:ServiceJourney:3746570x2025xHxMultxSamxSamedix00:LOC stop_sequence 23 departure_time 08:08:00 (1762585680) is less than the same stop arrival_time 08:08:34 (1762585714) - departure time must be equal to or greater than arrival time
  • trip_id ATOUMOD035:ServiceJourney:3745525x2025xHxMultxSamxSamedix00:LOC stop_sequence 5 departure_time 08:06:00 (1762585560) is less than the same stop arrival_time 08:08:31 (1762585711) - departure time must be equal to or greater than arrival time

GTFS-rt trip.trip_id does not belong to GTFS-rt trip.route_id in GTFS trips.txt E035 44 erreurs

The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt

Exemples d'erreurs
  • GTFS-rt entity ID SM:ATOUMOD005:ServiceJourney:963:LOC trip_id ATOUMOD005:ServiceJourney:963:LOC has route_id ATOUMOD005:Line:3:LOC but belongs to GTFS route_id ATOUMOD005:Line:2:LOC in GTFS trips.txt
  • GTFS-rt entity ID SM:ATOUMOD007:ServiceJourney:1119:LOC trip_id ATOUMOD007:ServiceJourney:1119:LOC has route_id ATOUMOD007:Line:25:LOC but belongs to GTFS route_id ATOUMOD007:Line:10:LOC in GTFS trips.txt
  • GTFS-rt entity ID SM:ATOUMOD005:ServiceJourney:187:LOC trip_id ATOUMOD005:ServiceJourney:187:LOC has route_id ATOUMOD005:Line:1:LOC but belongs to GTFS route_id ATOUMOD005:Line:3:LOC in GTFS trips.txt
  • GTFS-rt entity ID SM:ATOUMOD007:ServiceJourney:897:LOC trip_id ATOUMOD007:ServiceJourney:897:LOC has route_id ATOUMOD007:Line:22:LOC but belongs to GTFS route_id ATOUMOD007:Line:26:LOC in GTFS trips.txt
  • GTFS-rt entity ID SM:ATOUMOD007:ServiceJourney:967:LOC trip_id ATOUMOD007:ServiceJourney:967:LOC has route_id ATOUMOD007:Line:23:LOC but belongs to GTFS route_id ATOUMOD007:Line:38:LOC in GTFS trips.txt

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 146 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 ATOUMOD005:ServiceJourney:963:LOC stop_sequence 15 has stop_id FR:76217:ZE:18044:ATOUMOD005 but GTFS stop_sequence 15 has stop_id FR:76217:ZE:18077:ATOUMOD005 - stop_ids should be the same
  • GTFS-rt trip_id ATOUMOD035:ServiceJourney:3747774x2025xHxMultxSamxSamedix00:LOC stop_sequence 27 has stop_id FR:50129:ZE:10HME2:ATOUMOD035 but GTFS stop_sequence 27 has stop_id FR:50129:ZE:10PET2:ATOUMOD035 - stop_ids should be the same
  • GTFS-rt trip_id ATOUMOD035:ServiceJourney:3747774x2025xHxMultxSamxSamedix00:LOC stop_sequence 32 has stop_id FR:50129:ZE:10PAU2:ATOUMOD035 but GTFS stop_sequence 32 has stop_id FR:50129:ZE:10TLL2:ATOUMOD035 - stop_ids should be the same
  • GTFS-rt trip_id ATOUMOD003:ServiceJourney:4075198x2025x26xGSamHLiaxSamedix01:LOC stop_sequence 11 has stop_id FR:76351:ZE:3011:ATOUMOD003 but GTFS stop_sequence 11 has stop_id FR:76351:ZE:3377:ATOUMOD003 - stop_ids should be the same
  • GTFS-rt trip_id ATOUMOD003:ServiceJourney:4075198x2025x26xGSamHLiaxSamedix01:LOC stop_sequence 20 has stop_id FR:76351:ZE:3198:ATOUMOD003 but GTFS stop_sequence 20 has stop_id FR:76351:ZE:3806:ATOUMOD003 - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 204 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 ATOUMOD035:ServiceJourney:3746565x2025xHxMultxSamxSamedix00:LOC contains stop_sequence 25 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD003:ServiceJourney:4062504x2025x26xGSamHTNIxSamedix00:LOC contains stop_sequence 20 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD035:ServiceJourney:3747726x2025xHxMultxSamxSamedix00:LOC contains stop_sequence 7 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD005:ServiceJourney:963:LOC contains stop_sequence 12 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD003:ServiceJourney:4155777x2025x26xGSamHTNIxSamedix00:LOC contains stop_sequence 41 that does not exist in GTFS stop_times.txt for this trip

Avertissements

vehicle_id not populated W002 300 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id ATOUMOD035:ServiceJourney:3746565x2025xHxMultxSamxSamedix00:LOC does not have a vehicle_id
  • trip_id ATOUMOD003:ServiceJourney:4062504x2025x26xGSamHTNIxSamedix00:LOC does not have a vehicle_id
  • trip_id ATOUMOD035:ServiceJourney:3747726x2025xHxMultxSamxSamedix00:LOC does not have a vehicle_id
  • trip_id ATOUMOD005:ServiceJourney:963:LOC does not have a vehicle_id
  • trip_id ATOUMOD003:ServiceJourney:4155777x2025x26xGSamHTNIxSamedix00:LOC does not have a vehicle_id

schedule_relationship not populated W009 600 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs
  • trip_id ATOUMOD035:ServiceJourney:3746565x2025xHxMultxSamxSamedix00:LOC stop_sequence 12 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD035:ServiceJourney:3746565x2025xHxMultxSamxSamedix00:LOC does not have a schedule_relationship
  • trip_id ATOUMOD003:ServiceJourney:4062504x2025x26xGSamHTNIxSamedix00:LOC stop_sequence 16 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD003:ServiceJourney:4062504x2025x26xGSamHTNIxSamedix00:LOC does not have a schedule_relationship
  • trip_id ATOUMOD035:ServiceJourney:3747726x2025xHxMultxSamxSamedix00:LOC stop_sequence 21 (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 9 602 30 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. 434 502 30 fois (100 % des validations)
E024 GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt 10 878 30 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 3 275 30 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 698 30 fois (100 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 12 089 30 fois (100 % des validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 24 049 30 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. 289 26 fois (87 % 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 173 24 fois (80 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 297 20 fois (67 % des validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 8 8 fois (27 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 62 6 fois (20 % des validations)
E035 The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt 196 5 fois (17 % des validations)
E040 All stop_time_updates must contain stop_id or stop_sequence - both fields cannot be left blank 4 1 fois (3 % 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 4 1 fois (3 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 09/11/2025 à 05h38 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/11/2025 à 05h38 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

{ "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1762663116" } }