transport.data.gouv.fr transport.data.gouv.fr

Détails de la ressource

Nom du fichier : Données en temps réel au format GTFS-RT (TripUpdate)
Format : gtfs-rt
Télécharger

Cette ressource fait partie du jeu de données Réseau urbain Kicéo.

Disponibilité au téléchargement

01/03/2025
100%
02/03/2025
100%
03/03/2025
95.8%
04/03/2025
100%
05/03/2025
100%
06/03/2025
99.3%
07/03/2025
100%
08/03/2025
100%
09/03/2025
100%
10/03/2025
99.3%
11/03/2025
99.3%
12/03/2025
98.6%
13/03/2025
100%
14/03/2025
100%
15/03/2025
100%
16/03/2025
100%
17/03/2025
100%
18/03/2025
100%
19/03/2025
99.4%
20/03/2025
100%
21/03/2025
99.3%
22/03/2025
100%
23/03/2025
100%
24/03/2025
100%
25/03/2025
100%
26/03/2025
99.2%
27/03/2025
99.2%
28/03/2025
99.3%
29/03/2025
100%
30/03/2025
100%
31/03/2025
100%
En savoir plus
Nous testons la disponibilité de cette ressource au téléchargement toutes les heures, en effectuant une requête HTTP de type 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 472 erreurs, 432 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 31/03/2025 à 17h30 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 92 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 TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id TRIPID-12069 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 92 erreurs

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Exemples d'erreurs
  • route_id MOBICEO does not exist in the GTFS data routes.txt
  • route_id MOBICEO does not exist in the GTFS data routes.txt
  • route_id MOBICEO does not exist in the GTFS data routes.txt
  • route_id MOBICEO does not exist in the GTFS data routes.txt
  • route_id MOBICEO does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 1 261 erreurs

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Exemples d'erreurs
  • trip_id TRIPID-12069 stop_id STP-DEPART does not exist in GTFS data stops.txt
  • trip_id TRIPID-12069 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
  • trip_id TRIPID-12069 stop_id STP-DEPART does not exist in GTFS data stops.txt
  • trip_id TRIPID-12069 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
  • trip_id TRIPID-12069 stop_id STP-DEPART does not exist in GTFS data stops.txt

All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 E015 30 erreurs

All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt

Exemples d'erreurs
  • trip_id 2-152991563777 stop_id 1727 does not have location_type=0 in GTFS stops.txt
  • trip_id 2-152991563777 stop_id 1729 does not have location_type=0 in GTFS stops.txt
  • trip_id 2-152505024513 stop_id 3369 does not have location_type=0 in GTFS stops.txt
  • trip_id 2-153780158466 stop_id 1758 does not have location_type=0 in GTFS stops.txt
  • trip_id 2-152907677698 stop_id 1724 does not have location_type=0 in GTFS stops.txt

Sequential stop_time_update times are not increasing E022 1 995 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 2-152958074881 stop_sequence 8 arrival_time 17:14:53 (1743434093) is less than previous stop arrival_time 17:16:01 (1743434161) - times must increase between two sequential stops
  • trip_id 2-152958074881 stop_sequence 8 arrival_time 17:14:53 (1743434093) is less than previous stop departure_time 17:16:05 (1743434165) - times must increase between two sequential stops
  • trip_id 2-152958074881 stop_sequence 8 departure_time 17:15:38 (1743434138) is less than previous stop departure_time 17:16:05 (1743434165) - times must increase between two sequential stops
  • trip_id 2-152958074881 stop_sequence 8 departure_time 17:15:38 (1743434138) is less than previous stop arrival_time 17:16:01 (1743434161) - times must increase between two sequential stops
  • trip_id 2-152035262465 stop_sequence 20 arrival_time 17:49:08 (1743436148) is equal to previous stop arrival_time 17:49:08 (1743436148) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 2 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 2-153343819778 stop_sequence 9 departure_time 17:29:17 (1743434957) is less than the same stop arrival_time 17:30:02 (1743435002) - departure time must be equal to or greater than arrival time
  • trip_id 2-153276776450 stop_sequence 3 departure_time 17:28:09 (1743434889) is less than the same stop arrival_time 17:29:25 (1743434965) - departure time must be equal to or greater than arrival time

Avertissements

timestamp not populated W001 296 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id TRIPID-12069 does not have a timestamp
  • trip_id TRIPID-12069 does not have a timestamp
  • trip_id TRIPID-12069 does not have a timestamp
  • trip_id TRIPID-12069 does not have a timestamp
  • trip_id TRIPID-12069 does not have a timestamp

vehicle_id not populated W002 136 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id 2-319160362 does not have a vehicle_id
  • trip_id 2-336134271 does not have a vehicle_id
  • trip_id 2-19139827 does not have a vehicle_id
  • trip_id 2-17044653 does not have a vehicle_id
  • trip_id 2-19211856 does not have a vehicle_id
Valider ce GTFS-RT maintenant

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
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 97 801 26 fois (90 % des validations)
W001 Timestamps should be populated for all elements 14 617 26 fois (90 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 11 302 26 fois (90 % des validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 3 182 24 fois (83 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 2 951 24 fois (83 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 39 301 24 fois (83 % 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. 160 24 fois (83 % des validations)
E015 All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt 1 415 19 fois (66 % des validations)
E041 Unless a trip's schedule_relationship is CANCELED, a trip must have at least one stop_time_update 7 2 fois (7 % des validations)
E023 For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip 6 1 fois (3 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 01/04/2025 à 01h54 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (0)

Entités présentes dans ce flux lors des 7 derniers jours.

trip_updates

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 01/04/2025 à 01h54 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

{ "header": { "gtfs_realtime_version": "2.0", "timestamp": "1743465281" } }