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 239 erreurs, 6 988 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 03/03/2026 à 08h14 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
stop_times_updates not strictly sorted E002 1 erreur
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Exemples d'erreurs
- trip_id 17679366 stop_sequence [23, 23] is not strictly sorted by increasing stop_sequence
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 17687744 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 17687760 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 17688214 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 17687755 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 17687754 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 104 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id S41 does not exist in the GTFS data routes.txt
- route_id S44 does not exist in the GTFS data routes.txt
- route_id NAV does not exist in the GTFS data routes.txt
- route_id S42 does not exist in the GTFS data routes.txt
- route_id S78 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 139 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 17687744 stop_id DEP_KER2 does not exist in GTFS data stops.txt
- trip_id 17687744 stop_id BRANDA_2 does not exist in GTFS data stops.txt
- trip_id 17682113 stop_id P AMIS_1 does not exist in GTFS data stops.txt
- trip_id 17682073 stop_id P AMIS_2 does not exist in GTFS data stops.txt
- trip_id 17682087 stop_id P AMIS_2 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 28 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 17679763 stop_sequence 41 arrival_time 09:21:01 (1772526061) is less than previous stop arrival_time 09:45:27 (1772527527) - times must increase between two sequential stops
- trip_id 17679763 stop_sequence 41 arrival_time 09:21:01 (1772526061) is less than previous stop departure_time 09:45:27 (1772527527) - times must increase between two sequential stops
- trip_id 17679763 stop_sequence 41 departure_time 09:21:01 (1772526061) is less than previous stop departure_time 09:45:27 (1772527527) - times must increase between two sequential stops
- trip_id 17679763 stop_sequence 41 departure_time 09:21:01 (1772526061) is less than previous stop arrival_time 09:45:27 (1772527527) - times must increase between two sequential stops
- trip_id 17680625 stop_sequence 33 arrival_time 09:21:00 (1772526060) is less than previous stop arrival_time 09:26:41 (1772526401) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 4 erreurs
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 17684648 stop_sequence 0 departure_time 00:02:31 (1772492551) is less than the same stop arrival_time 23:52:47 (1772578367) - departure time must be equal to or greater than arrival time
- trip_id 17684644 stop_sequence 0 departure_time 00:00:26 (1772492426) is less than the same stop arrival_time 23:54:09 (1772578449) - departure time must be equal to or greater than arrival time
- trip_id 17683410 stop_sequence 0 departure_time 00:03:00 (1772492580) is less than the same stop arrival_time 23:47:59 (1772578079) - departure time must be equal to or greater than arrival time
- trip_id 17685507 stop_sequence 0 departure_time 00:03:10 (1772492590) is less than the same stop arrival_time 23:58:30 (1772578710) - departure time must be equal to or greater than arrival time
Sequential stop_time_updates have the same stop_sequence E036 1 erreur
Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence
Exemples d'erreurs
- trip_id 17679366 has repeating stop_sequence 23 - stop_sequence must increase for each stop_time_update
Sequential stop_time_updates have the same stop_id E037 1 erreur
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Exemples d'erreurs
- trip_id 17679366 has repeating stop_id CAMID_1 at stop_sequence 23 - sequential stop_ids should be different
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 2 338 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 17680998 stop_sequence 17 has stop_id TOURB_2 but GTFS stop_sequence 17 has stop_id STANG_2 - stop_ids should be the same
- GTFS-rt trip_id 17680998 stop_sequence 18 has stop_id KERVIL_2 but GTFS stop_sequence 18 has stop_id TOURB_2 - stop_ids should be the same
- GTFS-rt trip_id 17680998 stop_sequence 19 has stop_id COATAU_2 but GTFS stop_sequence 19 has stop_id KERVIL_2 - stop_ids should be the same
- GTFS-rt trip_id 17680998 stop_sequence 20 has stop_id FROUT_2 but GTFS stop_sequence 20 has stop_id COATAU_2 - stop_ids should be the same
- GTFS-rt trip_id 17680998 stop_sequence 21 has stop_id SALANG_2 but GTFS stop_sequence 21 has stop_id FROUT_2 - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 1 592 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 17679396 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 17685586 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 17685585 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 17680895 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 17680075 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
Avertissements
timestamp not populated W001 1 747 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 17679396 does not have a timestamp
- trip_id 17685586 does not have a timestamp
- trip_id 17685585 does not have a timestamp
- trip_id 17680895 does not have a timestamp
- trip_id 17680075 does not have a timestamp
vehicle_id not populated W002 1 747 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 17679396 does not have a vehicle_id
- trip_id 17685586 does not have a vehicle_id
- trip_id 17685585 does not have a vehicle_id
- trip_id 17680895 does not have a vehicle_id
- trip_id 17680075 does not have a vehicle_id
schedule_relationship not populated W009 3 494 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id 17679396 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 17679396 does not have a schedule_relationship
- trip_id 17685586 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 17685586 does not have a schedule_relationship
- trip_id 17685585 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 | 1 868 | 22 fois (76 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 247 | 22 fois (76 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 9 433 | 22 fois (76 % 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 | 32 386 | 22 fois (76 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 31 758 | 22 fois (76 % des validations) |
| W001 | Timestamps should be populated for all elements | 35 522 | 22 fois (76 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 35 522 | 22 fois (76 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 71 044 | 22 fois (76 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 2 908 | 20 fois (69 % 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. | 11 | 7 fois (24 % des validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 3 | 3 fois (10 % 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 04/03/2026 à 03h28 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 04/03/2026 à 03h28 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1772591297"
}
}