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

Détails de la ressource

Nom du fichier : filbleu-gtfsrt-tripupdates
Format : gtfs-rt
Télécharger

Version Fil Bleu des alertes de services au format GTFS-RT

Cette ressource fait partie du jeu de données Réseau urbain et périurbain Fil Bleu.

Disponibilité au téléchargement

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

❌4 412 erreurs, 412 avertissements

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

Erreurs

stop_times_updates not strictly sorted E002 96 erreurs

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

Exemples d'erreurs
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659194 stop_sequence [9, 17, 15] is not strictly sorted by increasing stop_sequence
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659122 stop_sequence [18, 19, 20, 21, 15] is not strictly sorted by increasing stop_sequence
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:654127 stop_sequence [9, 18, 16, 11, 10, 15, 7, 12, 13, 8, 14, 17] is not strictly sorted by increasing stop_sequence
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:654110 stop_sequence [14, 10] is not strictly sorted by increasing stop_sequence
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:654001 stop_sequence [11, 27, 18] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 4 230 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 TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659194 stop_sequence 15 arrival_time 10:17:44 (1746778664) is less than previous stop arrival_time 10:20:44 (1746778844) - times must increase between two sequential stops
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659194 stop_sequence 15 arrival_time 10:17:44 (1746778664) is less than previous stop departure_time 10:20:44 (1746778844) - times must increase between two sequential stops
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659194 stop_sequence 15 departure_time 10:17:44 (1746778664) is less than previous stop departure_time 10:20:44 (1746778844) - times must increase between two sequential stops
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659194 stop_sequence 15 departure_time 10:17:44 (1746778664) is less than previous stop arrival_time 10:20:44 (1746778844) - times must increase between two sequential stops
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659194 stop_sequence 12 arrival_time 10:13:53 (1746778433) is less than previous stop arrival_time 10:17:44 (1746778664) - times must increase between two sequential stops

GTFS-rt stop_sequence not found in GTFS data E051 86 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 TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659194 contains stop_sequence 15 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659122 contains stop_sequence 15 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:654110 contains stop_sequence 10 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:654001 contains stop_sequence 18 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:653963 contains stop_sequence 26 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 103 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659463 does not have a timestamp
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659194 does not have a timestamp
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659122 does not have a timestamp
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:654127 does not have a timestamp
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:654110 does not have a timestamp

vehicle_id not populated W002 103 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659463 does not have a vehicle_id
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659194 does not have a vehicle_id
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659122 does not have a vehicle_id
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:654127 does not have a vehicle_id
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:654110 does not have a vehicle_id

schedule_relationship not populated W009 206 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659463 stop_sequence 26 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659463 does not have a schedule_relationship
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659194 stop_sequence 9 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659194 does not have a schedule_relationship
  • trip_id TTR:BUSTRAM2024-2025_V2:1572_PT2-PH1-VENDREDI:659122 stop_sequence 18 (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 2 305 29 fois (97 % des validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 96 172 29 fois (97 % des validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 1 989 29 fois (97 % des validations)
W001 Timestamps should be populated for all elements 2 509 29 fois (97 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 2 509 29 fois (97 % des validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 5 018 29 fois (97 % des validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 25 2 fois (7 % des validations)

Contenu du flux GTFS-RT

Impossible de décoder le flux GTFS-RT

Le flux GTFS-RT doit être accessible en HTTP, sans authentification et utiliser le format Protobuf.