Détails de la ressource

Nom du fichier : Flux GTFS-RT du réseau de transport public Lignes d'Azur : trip update
Format : gtfs-rt

Cette ressource fait partie du jeu de données Réseau urbain Lignes d'Azur.

Disponibilité au téléchargement

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

❌606 erreurs, 2 838 avertissements

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

Erreurs

Sequential stop_time_update times are not increasing E022 344 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 7059222-08_R_99_0806_08:56-SEPT2026-08-Samedi-08 stop_sequence 7 arrival_time 08:58:04 (1794038284) is less than previous stop arrival_time 09:02:53 (1794038573) - times must increase between two sequential stops
  • trip_id 7059222-08_R_99_0806_08:56-SEPT2026-08-Samedi-08 stop_sequence 7 arrival_time 08:58:04 (1794038284) is less than previous stop departure_time 09:02:53 (1794038573) - times must increase between two sequential stops
  • trip_id 7059222-08_R_99_0806_08:56-SEPT2026-08-Samedi-08 stop_sequence 7 departure_time 08:58:04 (1794038284) is less than previous stop departure_time 09:02:53 (1794038573) - times must increase between two sequential stops
  • trip_id 7059222-08_R_99_0806_08:56-SEPT2026-08-Samedi-08 stop_sequence 7 departure_time 08:58:04 (1794038284) is less than previous stop arrival_time 09:02:53 (1794038573) - times must increase between two sequential stops
  • trip_id 7080906-15_A_50_1506_07:45-SEPT2026-15-Samedi-41 stop_sequence 23 arrival_time 08:06:31 (1794035191) is less than previous stop arrival_time 08:07:35 (1794035255) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_id E037 2 erreurs

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

Exemples d'erreurs
  • trip_id 7083502-37_A_50_3701_09:15-SEPT2026-37-Samedi-35 has repeating stop_id 1447 at stop_sequence 17 - sequential stop_ids should be different
  • trip_id 7083500-37_A_50_3701_08:20-SEPT2026-37-Samedi-35 has repeating stop_id 1447 at stop_sequence 17 - sequential stop_ids should be different

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 258 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 7059222-08_R_99_0806_08:56-SEPT2026-08-Samedi-08 stop_sequence 3 has stop_id 2988 but GTFS stop_sequence 3 has stop_id 326 - stop_ids should be the same
  • GTFS-rt trip_id 7059222-08_R_99_0806_08:56-SEPT2026-08-Samedi-08 stop_sequence 4 has stop_id 326 but GTFS stop_sequence 4 has stop_id 304 - stop_ids should be the same
  • GTFS-rt trip_id 7059222-08_R_99_0806_08:56-SEPT2026-08-Samedi-08 stop_sequence 5 has stop_id 1616 but GTFS stop_sequence 5 has stop_id 479 - stop_ids should be the same
  • GTFS-rt trip_id 7059222-08_R_99_0806_08:56-SEPT2026-08-Samedi-08 stop_sequence 7 has stop_id 2988 but GTFS stop_sequence 7 has stop_id 1349 - stop_ids should be the same
  • GTFS-rt trip_id 7059222-08_R_99_0806_08:56-SEPT2026-08-Samedi-08 stop_sequence 8 has stop_id 326 but GTFS stop_sequence 8 has stop_id 1017 - 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 7137282-57_R_99_5703_07:30-SEPT2026-57-Samedi-08 contains stop_sequence 37 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 7059216-08_R_99_0803_07:47-SEPT2026-08-Samedi-08 contains stop_sequence 22 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 710 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id 7059222-08_R_99_0806_08:56-SEPT2026-08-Samedi-08 does not have a timestamp
  • trip_id 7032456-14_A_50_1404_09:01-SEPT2026-14-Samedi-37 does not have a timestamp
  • trip_id 7137264-57_R_99_5703_09:30-SEPT2026-57-Samedi-08 does not have a timestamp
  • trip_id 7032516-14_R_99_1404_09:33-SEPT2026-14-Samedi-37 does not have a timestamp
  • trip_id 7084714-98_A_50_9802_08:55-SEPT2026-98-Samedi-09 does not have a timestamp

vehicle_id not populated W002 710 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id 7059222-08_R_99_0806_08:56-SEPT2026-08-Samedi-08 does not have a vehicle_id
  • trip_id 7032456-14_A_50_1404_09:01-SEPT2026-14-Samedi-37 does not have a vehicle_id
  • trip_id 7137264-57_R_99_5703_09:30-SEPT2026-57-Samedi-08 does not have a vehicle_id
  • trip_id 7032516-14_R_99_1404_09:33-SEPT2026-14-Samedi-37 does not have a vehicle_id
  • trip_id 7084714-98_A_50_9802_08:55-SEPT2026-98-Samedi-09 does not have a vehicle_id

schedule_relationship not populated W009 1 418 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs
  • trip_id 7059222-08_R_99_0806_08:56-SEPT2026-08-Samedi-08 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 7059222-08_R_99_0806_08:56-SEPT2026-08-Samedi-08 does not have a schedule_relationship
  • trip_id 7032456-14_A_50_1404_09:01-SEPT2026-14-Samedi-37 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 7032456-14_A_50_1404_09:01-SEPT2026-14-Samedi-37 does not have a schedule_relationship
  • trip_id 7137264-57_R_99_5703_09:30-SEPT2026-57-Samedi-08 stop_sequence 2 (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
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 21 275 28 fois (97 % des validations)
W001 Timestamps should be populated for all elements 22 022 28 fois (97 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 22 022 28 fois (97 % des validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 43 961 28 fois (97 % 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 6 012 26 fois (90 % des validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 155 25 fois (86 % des validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 43 17 fois (59 % des validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 10 4 fois (14 % des validations)
E036 Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence 10 4 fois (14 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 08/11/2026 à 02h39 Europe/Paris.

trip_updates (1) 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 08/11/2026 à 02h39 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

{ "entity": [ { "id": "trip:7004657-11_A_50_1101_19:40-SEPT2026-11-Samedi-39", "tripUpdate": { "stopTimeUpdate": [ { "departure": { "time": "1794122555" }, "stopId": "1342", "stopSequence": 1 } ], "trip": { "directionId": 0, "routeId": "11", "tripId": "7004657-11_A_50_1101_19:40-SEPT2026-11-Samedi-39" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1794101958" } }