Détails de la ressource

Nom du fichier : Réseau Alternéo - RT - service Trip Update
Format : gtfs-rt

Flux GTFS-RT service Trip Update

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

Disponibilité au téléchargement

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

102 erreurs, 228 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 02/05/2025 à 09h10 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

stop_times_updates not strictly sorted E002 2 erreurs

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

Exemples d'erreurs
  • trip_id 2_5987192 stop_sequence [34, 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] is not strictly sorted by increasing stop_sequence
  • trip_id 2_5987143 stop_sequence [52, 53, 54, 1] is not strictly sorted by increasing stop_sequence

GTFS-rt stop_sequence isn't provided for trip that visits same stop_id more than once E009 1 erreur

If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence

Exemples d'erreurs
  • trip_id 2_5987143 visits stop_id [0:05343C] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided

Sequential stop_time_update times are not increasing E022 98 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 2_5987847 stop_sequence 35 arrival_time 11:05:50 (1746169550) is equal to previous stop arrival_time 11:05:50 (1746169550) - times must increase between two sequential stops
  • trip_id 2_5987847 stop_sequence 35 arrival_time 11:05:50 (1746169550) is equal to previous stop departure_time 11:05:50 (1746169550) - times must increase between two sequential stops
  • trip_id 2_5987847 stop_sequence 35 departure_time 11:05:50 (1746169550) is equal to previous stop departure_time 11:05:50 (1746169550) - times must increase between two sequential stops
  • trip_id 2_5987847 stop_sequence 35 departure_time 11:05:50 (1746169550) is equal to previous stop arrival_time 11:05:50 (1746169550) - times must increase between two sequential stops
  • trip_id 2_5988306 stop_sequence 2 arrival_time 10:26:03 (1746167163) is equal to previous stop departure_time 10:26:03 (1746167163) - times must increase between two sequential stops

GTFS-rt stop_sequence not found in GTFS data E051 1 erreur

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 2_5987143 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 141 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id 2_5988273 does not have a timestamp
  • trip_id 2_5988017 does not have a timestamp
  • trip_id 2_5988019 does not have a timestamp
  • trip_id 2_5988283 does not have a timestamp
  • trip_id 2_5987964 does not have a timestamp

vehicle_id not populated W002 87 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id 2_5988273 does not have a vehicle_id
  • trip_id 2_5988017 does not have a vehicle_id
  • trip_id 2_5988019 does not have a vehicle_id
  • trip_id 2_5987964 does not have a vehicle_id
  • trip_id 2_5987963 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
W001 Timestamps should be populated for all elements 2 489 24 fois (92 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 1 576 23 fois (88 % des validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 2 022 20 fois (77 % des validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 60 15 fois (58 % des validations)
E009 If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence 26 15 fois (58 % des validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 52 15 fois (58 % des validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 14 14 fois (54 % des validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 2 2 fois (8 % 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. 1 1 fois (4 % des validations)

Contenu du flux GTFS-RT

Entités

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

{ "header": { "gtfs_realtime_version": "2.0", "timestamp": "1746208427" } }