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
❌4 008 erreurs, 7 404 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 09/01/2026 à 08h03 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 31 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 17617277 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 17617278 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 17307462 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 17617276 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 17617559 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 30 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 173 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 17302046 stop_id ROBERV_3 does not exist in GTFS data stops.txt
- trip_id 17301368 stop_id P AMIS_2 does not exist in GTFS data stops.txt
- trip_id 17308225 stop_id P AMIS_2 does not exist in GTFS data stops.txt
- trip_id 17308225 stop_id P GROA_1 does not exist in GTFS data stops.txt
- trip_id 17617277 stop_id DEP_KER2 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 244 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 17301416 stop_sequence 16 arrival_time 08:07:25 (1767942445) is less than previous stop arrival_time 08:07:28 (1767942448) - times must increase between two sequential stops
- trip_id 17301416 stop_sequence 16 arrival_time 08:07:25 (1767942445) is less than previous stop departure_time 08:07:28 (1767942448) - times must increase between two sequential stops
- trip_id 17301416 stop_sequence 16 departure_time 08:07:25 (1767942445) is less than previous stop departure_time 08:07:28 (1767942448) - times must increase between two sequential stops
- trip_id 17301416 stop_sequence 16 departure_time 08:07:25 (1767942445) is less than previous stop arrival_time 08:07:28 (1767942448) - times must increase between two sequential stops
- trip_id 17301416 stop_sequence 23 arrival_time 08:13:24 (1767942804) is less than previous stop arrival_time 08:13:28 (1767942808) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 821 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 17308225 stop_sequence 1 has stop_id P AMIS_2 but GTFS stop_sequence 1 has stop_id PEUPLI_2 - stop_ids should be the same
- GTFS-rt trip_id 17308225 stop_sequence 2 has stop_id PENHO_2 but GTFS stop_sequence 2 has stop_id P_AMIS_2 - stop_ids should be the same
- GTFS-rt trip_id 17308225 stop_sequence 3 has stop_id J_VERN_2 but GTFS stop_sequence 3 has stop_id PENHO_2 - stop_ids should be the same
- GTFS-rt trip_id 17308225 stop_sequence 4 has stop_id PERON_2 but GTFS stop_sequence 4 has stop_id J_VERN_2 - stop_ids should be the same
- GTFS-rt trip_id 17308225 stop_sequence 5 has stop_id KERALE_4 but GTFS stop_sequence 5 has stop_id PERON_2 - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 1 709 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 17307823 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 17307090 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 17308018 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 17447076 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 17301425 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
Avertissements
timestamp not populated W001 1 851 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 17307823 does not have a timestamp
- trip_id 17307090 does not have a timestamp
- trip_id 17308018 does not have a timestamp
- trip_id 17447076 does not have a timestamp
- trip_id 17301425 does not have a timestamp
vehicle_id not populated W002 1 851 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 17307823 does not have a vehicle_id
- trip_id 17307090 does not have a vehicle_id
- trip_id 17308018 does not have a vehicle_id
- trip_id 17447076 does not have a vehicle_id
- trip_id 17301425 does not have a vehicle_id
schedule_relationship not populated W009 3 702 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id 17307823 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 17307823 does not have a schedule_relationship
- trip_id 17307090 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 17307090 does not have a schedule_relationship
- trip_id 17308018 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 | 651 | 30 fois (100 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 631 | 30 fois (100 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 4 072 | 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 | 40 536 | 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 | 41 321 | 30 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 44 376 | 30 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 44 376 | 30 fois (100 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 88 752 | 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. | 4 397 | 29 fois (97 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 1 | 1 fois (3 % des validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 1 | 1 fois (3 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 1 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 10/01/2026 à 02h46 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 10/01/2026 à 02h46 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1768009564"
}
}