Détails de la ressource
Les mises à jour des trajets vous informent des fluctuations d’horaires.
Elles sont délivrées au format GTFS-realtime, voir https://developers.google.com/transit/gtfs-realtime/guides/trip-updates?hl=fr.
Cette ressource fait partie du jeu de données Réseau urbain Bibus.
Disponibilité au téléchargement
En savoir plus
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
❌1 778 erreurs, 5 466 avertissements
De nombreuses erreurs de validation indiquent que les identifiants du GTFS-RT ne correspondent pas aux identifiants du GTFS.
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 31/07/2026 à 09h07 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 24 erreurs
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Exemples d'erreurs
- trip_id 18185400 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 18185429 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 18185435 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 18185388 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 18185401 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 24 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id NAV does not exist in the GTFS data routes.txt
- route_id NAV does not exist in the GTFS data routes.txt
- route_id NAV does not exist in the GTFS data routes.txt
- route_id NAV does not exist in the GTFS data routes.txt
- route_id NAV does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 273 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 17879887 stop_id P AMIS_1 does not exist in GTFS data stops.txt
- trip_id 17859165 stop_id FIC_LIB2 does not exist in GTFS data stops.txt
- trip_id 17859216 stop_id FIC_LIB2 does not exist in GTFS data stops.txt
- trip_id 17859148 stop_id FIC_LIB2 does not exist in GTFS data stops.txt
- trip_id 18185400 stop_id PSTRAS_2 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 97 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 17901941 stop_sequence 18 arrival_time 09:28:34 (1785482914) is less than previous stop arrival_time 09:28:35 (1785482915) - times must increase between two sequential stops
- trip_id 17901941 stop_sequence 18 arrival_time 09:28:34 (1785482914) is less than previous stop departure_time 09:28:35 (1785482915) - times must increase between two sequential stops
- trip_id 17901941 stop_sequence 18 departure_time 09:28:34 (1785482914) is less than previous stop departure_time 09:28:35 (1785482915) - times must increase between two sequential stops
- trip_id 17901941 stop_sequence 18 departure_time 09:28:34 (1785482914) is less than previous stop arrival_time 09:28:35 (1785482915) - times must increase between two sequential stops
- trip_id 17901941 stop_sequence 32 arrival_time 09:42:37 (1785483757) is less than previous stop arrival_time 09:42:47 (1785483767) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 1 erreur
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.
Exemples d'erreurs
- trip_id 17901967 stop_sequence 0 departure_time 00:04:00 (1785449040) is less than the same stop arrival_time 23:48:59 (1785534539) - departure time must be equal to or greater than arrival time
GTFS-rt stop_sequence not found in GTFS data E051 1 359 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 17906146 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 17890414 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 17879887 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 17906104 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 17859165 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
Avertissements
timestamp not populated W001 1 383 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 17906146 does not have a timestamp
- trip_id 17890414 does not have a timestamp
- trip_id 17879887 does not have a timestamp
- trip_id 17906104 does not have a timestamp
- trip_id 17859165 does not have a timestamp
vehicle_id not populated W002 1 317 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 17906146 does not have a vehicle_id
- trip_id 17890414 does not have a vehicle_id
- trip_id 17879887 does not have a vehicle_id
- trip_id 17906104 does not have a vehicle_id
- trip_id 17859165 does not have a vehicle_id
schedule_relationship not populated W009 2 766 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id 17906146 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 17906146 does not have a schedule_relationship
- trip_id 17890414 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 17890414 does not have a schedule_relationship
- trip_id 17879887 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 4 302 | 30 fois (100 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 123 | 30 fois (100 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 5 245 | 30 fois (100 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 13 821 | 30 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 38 690 | 30 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 36 905 | 30 fois (100 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 77 380 | 30 fois (100 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 34 388 | 29 fois (97 % 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. | 46 | 21 fois (70 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 4 193 | 3 fois (10 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 01/08/2026 à 01h25 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entités présentes dans ce flux lors des 7 derniers jours.
trip_updatesFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 01/08/2026 à 01h25 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1785540338"
}
}