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

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

❌2 810 erreurs, 272 avertissements

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

Erreurs

stop_times_updates not strictly sorted E002 63 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:1573_PT2-PH1-SAMEDI:659289 stop_sequence [17, 15] is not strictly sorted by increasing stop_sequence
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:659236 stop_sequence [18, 19, 20, 21, 23, 24, 17] is not strictly sorted by increasing stop_sequence
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:632337 stop_sequence [35, 36, 34] is not strictly sorted by increasing stop_sequence
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:632324 stop_sequence [17, 20, 14] is not strictly sorted by increasing stop_sequence
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:632317 stop_sequence [21, 18] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 2 692 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:1573_PT2-PH1-SAMEDI:659289 stop_sequence 15 arrival_time 09:02:06 (1749279726) is less than previous stop arrival_time 09:04:06 (1749279846) - times must increase between two sequential stops
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:659289 stop_sequence 15 arrival_time 09:02:06 (1749279726) is less than previous stop departure_time 09:04:06 (1749279846) - times must increase between two sequential stops
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:659289 stop_sequence 15 departure_time 09:02:06 (1749279726) is less than previous stop departure_time 09:04:06 (1749279846) - times must increase between two sequential stops
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:659289 stop_sequence 15 departure_time 09:02:06 (1749279726) is less than previous stop arrival_time 09:04:06 (1749279846) - times must increase between two sequential stops
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:659289 stop_sequence 22 arrival_time 09:10:29 (1749280229) is less than previous stop arrival_time 09:13:06 (1749280386) - times must increase between two sequential stops

GTFS-rt stop_sequence not found in GTFS data E051 55 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:1573_PT2-PH1-SAMEDI:659289 contains stop_sequence 15 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:659236 contains stop_sequence 17 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:632324 contains stop_sequence 14 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:632317 contains stop_sequence 18 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:632302 contains stop_sequence 31 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 68 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:659289 does not have a timestamp
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:659236 does not have a timestamp
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:632337 does not have a timestamp
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:632324 does not have a timestamp
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:632317 does not have a timestamp

vehicle_id not populated W002 68 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:659289 does not have a vehicle_id
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:659236 does not have a vehicle_id
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:632337 does not have a vehicle_id
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:632324 does not have a vehicle_id
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:632317 does not have a vehicle_id

schedule_relationship not populated W009 136 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:659289 stop_sequence 17 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:659289 does not have a schedule_relationship
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:659236 stop_sequence 18 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:659236 does not have a schedule_relationship
  • trip_id TTR:BUSTRAM2024-2025_V2:1573_PT2-PH1-SAMEDI:632337 stop_sequence 35 (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 314 28 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 934 28 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 2 040 28 fois (97 % des validations)
W001 Timestamps should be populated for all elements 2 549 28 fois (97 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 2 549 28 fois (97 % des validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 5 098 28 fois (97 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 08/06/2025 à 01h10 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 08/06/2025 à 01h10 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1749337836" } }