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
❌2 418 erreurs, 271 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 18/07/2025 à 09h00 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 168 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 5_58767893 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 5_58768311 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 5_58767597 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 5_58752732 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 5_58767565 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 2 194 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 5_58767893 stop_id 0:CHAPT2 does not exist in GTFS data stops.txt
- trip_id 5_58767893 stop_id 0:SCVEA does not exist in GTFS data stops.txt
- trip_id 5_58767893 stop_id 0:SCBRAR does not exist in GTFS data stops.txt
- trip_id 5_58767893 stop_id 0:VALFA does not exist in GTFS data stops.txt
- trip_id 5_58767893 stop_id 0:CATEMA does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 55 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 5_58768708 stop_sequence 1 departure_time 08:48:37 (1752821317) is less than previous stop arrival_time 09:17:52 (1752823072) - times must increase between two sequential stops
- trip_id 5_58768708 stop_sequence 2 arrival_time 08:51:18 (1752821478) is less than previous stop arrival_time 09:17:52 (1752823072) - times must increase between two sequential stops
- trip_id 5_58768708 stop_sequence 2 departure_time 08:51:18 (1752821478) is less than previous stop arrival_time 09:17:52 (1752823072) - times must increase between two sequential stops
- trip_id 5_58768708 stop_sequence 23 arrival_time 09:18:00 (1752823080) is less than previous stop arrival_time 09:18:26 (1752823106) - times must increase between two sequential stops
- trip_id 5_58768708 stop_sequence 23 arrival_time 09:18:00 (1752823080) is less than previous stop departure_time 09:18:26 (1752823106) - times must increase between two sequential stops
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 5_58768959 has repeating stop_id 0:GARALA - sequential stop_ids should be different
Avertissements
timestamp not populated W001 169 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 5_58767893 does not have a timestamp
- trip_id 5_58768311 does not have a timestamp
- trip_id 5_58767597 does not have a timestamp
- trip_id 5_58752732 does not have a timestamp
- trip_id 5_58767565 does not have a timestamp
vehicle_id not populated W002 102 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 5_58768311 does not have a vehicle_id
- trip_id 5_58767597 does not have a vehicle_id
- trip_id 5_58752732 does not have a vehicle_id
- trip_id 5_58767565 does not have a vehicle_id
- trip_id 5_58876784 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 | 4 636 | 29 fois (100 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 63 096 | 29 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. | 1 571 | 29 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 4 643 | 29 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 2 749 | 29 fois (100 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 10 | 6 fois (21 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 19/07/2025 à 03h47 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 19/07/2025 à 03h47 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1752889674"
}
}