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
❌743 erreurs, 6 107 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 05/10/2026 à 09h18 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 33 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 18293513 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 18293500 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 18293492 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 18293512 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 18293518 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 55 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id BUSA 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 BUSB does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 145 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 18172198 stop_id P AMIS_3 does not exist in GTFS data stops.txt
- trip_id 18293513 stop_id BRANDA_1 does not exist in GTFS data stops.txt
- trip_id 18293513 stop_id DEP_KER2 does not exist in GTFS data stops.txt
- trip_id 18293500 stop_id DEP_KER2 does not exist in GTFS data stops.txt
- trip_id 18293500 stop_id BRANDA_2 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 92 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 18153073 stop_sequence 16 arrival_time 09:22:21 (1791184941) is equal to previous stop arrival_time 09:22:21 (1791184941) - times must increase between two sequential stops
- trip_id 18153073 stop_sequence 16 arrival_time 09:22:21 (1791184941) is equal to previous stop departure_time 09:22:21 (1791184941) - times must increase between two sequential stops
- trip_id 18153073 stop_sequence 16 departure_time 09:22:21 (1791184941) is equal to previous stop departure_time 09:22:21 (1791184941) - times must increase between two sequential stops
- trip_id 18153073 stop_sequence 16 departure_time 09:22:21 (1791184941) is equal to previous stop arrival_time 09:22:21 (1791184941) - times must increase between two sequential stops
- trip_id 18203046 stop_sequence 17 arrival_time 09:39:38 (1791185978) is less than previous stop arrival_time 09:39:40 (1791185980) - 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 18115453 stop_sequence 1 departure_time 00:00:00 (1791151200) is less than the same stop arrival_time 23:56:02 (1791237362) - departure time must be equal to or greater than arrival time
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 185 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 18172198 stop_sequence 7 has stop_id P AMIS_3 but GTFS stop_sequence 7 has stop_id P_AMIS_3 - stop_ids should be the same
- GTFS-rt trip_id 18153899 stop_sequence 25 has stop_id P AMIS_1 but GTFS stop_sequence 25 has stop_id P_AMIS_1 - stop_ids should be the same
- GTFS-rt trip_id 18153855 stop_sequence 7 has stop_id P AMIS_3 but GTFS stop_sequence 7 has stop_id P_AMIS_3 - stop_ids should be the same
- GTFS-rt trip_id 18296302 stop_sequence 8 has stop_id ALB1ER_3 but GTFS stop_sequence 8 has stop_id ALB1ER_1 - stop_ids should be the same
- GTFS-rt trip_id 18296302 stop_sequence 9 has stop_id CHUM_1 but GTFS stop_sequence 9 has stop_id GLASGO_2 - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 232 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 18298170 contains stop_sequence 3 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 18298244 contains stop_sequence 3 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 18298084 contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 18298216 contains stop_sequence 2 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 18298067 contains stop_sequence 3 that does not exist in GTFS stop_times.txt for this trip
Avertissements
timestamp not populated W001 1 548 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 18297575 does not have a timestamp
- trip_id 18297582 does not have a timestamp
- trip_id 18197524 does not have a timestamp
- trip_id 18297584 does not have a timestamp
- trip_id 18297534 does not have a timestamp
vehicle_id not populated W002 1 463 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 18297575 does not have a vehicle_id
- trip_id 18297582 does not have a vehicle_id
- trip_id 18197524 does not have a vehicle_id
- trip_id 18297584 does not have a vehicle_id
- trip_id 18297534 does not have a vehicle_id
schedule_relationship not populated W009 3 096 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id 18297575 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 18297575 does not have a schedule_relationship
- trip_id 18297582 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 18297582 does not have a schedule_relationship
- trip_id 18197524 stop_sequence 1 (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 | 899 | 30 fois (100 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 693 | 30 fois (100 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 5 791 | 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. | 12 168 | 30 fois (100 % 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 | 4 286 | 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 | 6 762 | 30 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 41 700 | 30 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 39 427 | 30 fois (100 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 83 400 | 30 fois (100 % 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. | 26 | 16 fois (53 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 195 | 2 fois (7 % des validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 195 | 2 fois (7 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 191 | 2 fois (7 % des validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 1 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 06/10/2026 à 03h30 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 06/10/2026 à 03h30 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1791250248"
}
}