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

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

❌684 erreurs, 68 avertissements

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

Erreurs

stop_times_updates not strictly sorted E002 16 erreurs

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

Exemples d'erreurs
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658382 stop_sequence [28, 22] is not strictly sorted by increasing stop_sequence
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658360 stop_sequence [23, 61, 46] is not strictly sorted by increasing stop_sequence
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658301 stop_sequence [25, 11] is not strictly sorted by increasing stop_sequence
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658283 stop_sequence [26, 47, 41] is not strictly sorted by increasing stop_sequence
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658160 stop_sequence [5, 14, 18, 23, 15] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 652 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:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658382 stop_sequence 22 arrival_time 09:05:32 (1753599932) is less than previous stop arrival_time 09:10:31 (1753600231) - times must increase between two sequential stops
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658382 stop_sequence 22 arrival_time 09:05:32 (1753599932) is less than previous stop departure_time 09:10:31 (1753600231) - times must increase between two sequential stops
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658382 stop_sequence 22 departure_time 09:05:32 (1753599932) is less than previous stop departure_time 09:10:31 (1753600231) - times must increase between two sequential stops
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658382 stop_sequence 22 departure_time 09:05:32 (1753599932) is less than previous stop arrival_time 09:10:31 (1753600231) - times must increase between two sequential stops
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658382 stop_sequence 25 arrival_time 09:07:43 (1753600063) is less than previous stop arrival_time 09:09:30 (1753600170) - times must increase between two sequential stops

GTFS-rt stop_sequence not found in GTFS data E051 16 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:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658382 contains stop_sequence 22 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658360 contains stop_sequence 46 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658301 contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658283 contains stop_sequence 41 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658160 contains stop_sequence 15 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 17 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658382 does not have a timestamp
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658360 does not have a timestamp
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658301 does not have a timestamp
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658283 does not have a timestamp
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658275 does not have a timestamp

vehicle_id not populated W002 17 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658382 does not have a vehicle_id
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658360 does not have a vehicle_id
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658301 does not have a vehicle_id
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658283 does not have a vehicle_id
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658275 does not have a vehicle_id

schedule_relationship not populated W009 34 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658382 stop_sequence 28 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658382 does not have a schedule_relationship
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658360 stop_sequence 23 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658360 does not have a schedule_relationship
  • trip_id TTR:BUSTRAMETE_2025_V2:1640_PT2-PH3-DIMANCHE:658301 stop_sequence 25 (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 1 651 27 fois (90 % des validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 68 332 27 fois (90 % des validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 1 404 27 fois (90 % des validations)
W001 Timestamps should be populated for all elements 1 790 27 fois (90 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 1 790 27 fois (90 % des validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 3 580 27 fois (90 % des validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 2 2 fois (7 % des validations)

Contenu du flux GTFS-RT

Entités

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

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