Détails de la ressource
fichier GTFS-RT
Cette ressource fait partie du jeu de données Réseau urbain T2C.
Ressources associées
GTFS
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
❌389 erreurs, 1 621 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 04/06/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 202 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 4503749951632835 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4503749951632959 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4503749951632973 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4503749951632913 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4503749951633218 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 7 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id 11822099345702942 does not exist in the GTFS data routes.txt
- route_id 11822099345702941 does not exist in the GTFS data routes.txt
- route_id 11822099345702941 does not exist in the GTFS data routes.txt
- route_id 11822099345702940 does not exist in the GTFS data routes.txt
- route_id 11822099345702940 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 11 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 4503749951611630 stop_id 3377704015495719 does not exist in GTFS data stops.txt
- trip_id 4503749951611630 stop_id 3377704015497105 does not exist in GTFS data stops.txt
- trip_id 4503749951611630 stop_id 3377704015496393 does not exist in GTFS data stops.txt
- trip_id 4503749951628039 stop_id 3377837159481482 does not exist in GTFS data stops.txt
- trip_id 4503749951628039 stop_id 3377837159481485 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 167 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 4503749951625936 stop_sequence 26 arrival_time 08:44:16 (1749019456) is equal to previous stop arrival_time 08:44:16 (1749019456) - times must increase between two sequential stops
- trip_id 4503749951625936 stop_sequence 26 arrival_time 08:44:16 (1749019456) is equal to previous stop departure_time 08:44:16 (1749019456) - times must increase between two sequential stops
- trip_id 4503749951625936 stop_sequence 26 departure_time 08:44:16 (1749019456) is equal to previous stop departure_time 08:44:16 (1749019456) - times must increase between two sequential stops
- trip_id 4503749951625936 stop_sequence 26 departure_time 08:44:16 (1749019456) is equal to previous stop arrival_time 08:44:16 (1749019456) - times must increase between two sequential stops
- trip_id 4503749951625936 stop_sequence 27 arrival_time 08:44:16 (1749019456) is equal to previous stop arrival_time 08:44:16 (1749019456) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 2 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 4503749951627376 stop_sequence 7 has stop_id 3377704015495336 but GTFS stop_sequence 7 has stop_id 3377704015497018 - stop_ids should be the same
- GTFS-rt trip_id 4503749951627401 stop_sequence 7 has stop_id 3377704015495336 but GTFS stop_sequence 7 has stop_id 3377704015497018 - stop_ids should be the same
Avertissements
vehicle_id not populated W002 1 621 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 4503749951625858 does not have a vehicle_id
- trip_id 4503749951625936 does not have a vehicle_id
- trip_id 4503749951625996 does not have a vehicle_id
- trip_id 4503749951626148 does not have a vehicle_id
- trip_id 4503749951625502 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 |
|---|---|---|---|
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 39 081 | 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 020 | 29 fois (97 % 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 | 128 | 29 fois (97 % 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 629 | 27 fois (90 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 294 | 20 fois (67 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 161 | 19 fois (63 % des validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 1 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 05/06/2025 à 01h33 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 05/06/2025 à 01h33 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1749079983"
}
}