Détails de la ressource
GTFS-RT Mises à jour des trajets en temps réel
Cette ressource fait partie du jeu de données Réseau urbain Tango.
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 410 erreurs, 331 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 03/04/2025 à 09h08 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 214 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 1_48531927 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1_48331012 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1_48623398 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1_48342256 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1_48331255 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt stop_id does not exist in GTFS data E011 3 119 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 1_48531927 stop_id 0:MASX does not exist in GTFS data stops.txt
- trip_id 1_48331012 stop_id 0:ALEST does not exist in GTFS data stops.txt
- trip_id 1_48331012 stop_id 0:MARGR does not exist in GTFS data stops.txt
- trip_id 1_48331012 stop_id 0:PARAR does not exist in GTFS data stops.txt
- trip_id 1_48331012 stop_id 0:PILOR does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 77 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 1_48331300 stop_sequence 25 arrival_time 10:28:55 (1743668935) is less than previous stop arrival_time 10:29:00 (1743668940) - times must increase between two sequential stops
- trip_id 1_48331300 stop_sequence 25 arrival_time 10:28:55 (1743668935) is less than previous stop departure_time 10:29:00 (1743668940) - times must increase between two sequential stops
- trip_id 1_48331300 stop_sequence 25 departure_time 10:28:55 (1743668935) is less than previous stop departure_time 10:29:00 (1743668940) - times must increase between two sequential stops
- trip_id 1_48331300 stop_sequence 25 departure_time 10:28:55 (1743668935) is less than previous stop arrival_time 10:29:00 (1743668940) - times must increase between two sequential stops
- trip_id 1_48331297 stop_sequence 25 arrival_time 09:56:46 (1743667006) is less than previous stop arrival_time 09:59:00 (1743667140) - times must increase between two sequential stops
Avertissements
timestamp not populated W001 215 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 1_48531927 does not have a timestamp
- trip_id 1_48331012 does not have a timestamp
- trip_id 1_48623398 does not have a timestamp
- trip_id 1_48342256 does not have a timestamp
- trip_id 1_48331255 does not have a timestamp
vehicle_id not populated W002 116 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 1_48531927 does not have a vehicle_id
- trip_id 1_48331012 does not have a vehicle_id
- trip_id 1_48623398 does not have a vehicle_id
- trip_id 1_48331255 does not have a vehicle_id
- trip_id 1_48331300 does not have a vehicle_id
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 043 | 6 fois (100 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 15 097 | 6 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. | 563 | 6 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 1 047 | 6 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 599 | 6 fois (100 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 04/04/2025 à 04h15 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 à 04h15 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1743732958"
}
}