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
❌3 536 erreurs, 6 652 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 03/04/2025 à 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 29 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 16957525 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 16957535 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 16958640 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 16957546 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 16957539 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 29 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 161 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 16549706 stop_id ROBERV_3 does not exist in GTFS data stops.txt
- trip_id 16957525 stop_id DEP_KER2 does not exist in GTFS data stops.txt
- trip_id 16550007 stop_id P GROA_2 does not exist in GTFS data stops.txt
- trip_id 16550007 stop_id P AMIS_1 does not exist in GTFS data stops.txt
- trip_id 16957535 stop_id DEP_KER2 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 376 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 16550595 stop_sequence 28 arrival_time 09:41:09 (1743666069) is less than previous stop arrival_time 09:41:26 (1743666086) - times must increase between two sequential stops
- trip_id 16550595 stop_sequence 28 arrival_time 09:41:09 (1743666069) is less than previous stop departure_time 09:41:26 (1743666086) - times must increase between two sequential stops
- trip_id 16550595 stop_sequence 28 departure_time 09:41:09 (1743666069) is less than previous stop departure_time 09:41:26 (1743666086) - times must increase between two sequential stops
- trip_id 16550595 stop_sequence 28 departure_time 09:41:09 (1743666069) is less than previous stop arrival_time 09:41:26 (1743666086) - times must increase between two sequential stops
- trip_id 17021100 stop_sequence 3 arrival_time 18:20:00 (1743697200) is less than previous stop arrival_time 18:37:05 (1743698225) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 398 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 16550595 stop_sequence 1 has stop_id STMICH_2 but GTFS stop_sequence 1 has stop_id BRANDA_1 - stop_ids should be the same
- GTFS-rt trip_id 16550595 stop_sequence 2 has stop_id VHUGO_2 but GTFS stop_sequence 2 has stop_id STMICH_2 - stop_ids should be the same
- GTFS-rt trip_id 16550595 stop_sequence 3 has stop_id REPUBL_2 but GTFS stop_sequence 3 has stop_id VHUGO_2 - stop_ids should be the same
- GTFS-rt trip_id 16550595 stop_sequence 4 has stop_id GAMBET_2 but GTFS stop_sequence 4 has stop_id REPUBL_2 - stop_ids should be the same
- GTFS-rt trip_id 16550595 stop_sequence 5 has stop_id KENNED_3 but GTFS stop_sequence 5 has stop_id GAMBET_2 - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 1 543 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 16550308 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 17020994 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 16561155 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 17020987 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 16550497 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
Avertissements
timestamp not populated W001 1 663 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 16550308 does not have a timestamp
- trip_id 17020994 does not have a timestamp
- trip_id 16561155 does not have a timestamp
- trip_id 16550595 does not have a timestamp
- trip_id 17020987 does not have a timestamp
vehicle_id not populated W002 1 663 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 16550308 does not have a vehicle_id
- trip_id 17020994 does not have a vehicle_id
- trip_id 16561155 does not have a vehicle_id
- trip_id 16550595 does not have a vehicle_id
- trip_id 17020987 does not have a vehicle_id
schedule_relationship not populated W009 3 326 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id 16550308 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 16550308 does not have a schedule_relationship
- trip_id 17020994 stop_sequence 0 (and potentially more for this trip) does not have a schedule_relationship
- trip_id 17020994 does not have a schedule_relationship
- trip_id 16561155 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 | 2 212 | 30 fois (100 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 735 | 30 fois (100 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 4 539 | 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. | 5 085 | 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 | 42 571 | 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 | 42 538 | 30 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 47 341 | 30 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 47 341 | 30 fois (100 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 94 682 | 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. | 1 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 04/04/2025 à 02h55 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/04/2025 à 02h55 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1743728129"
}
}