Détails de la ressource
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
- TripUpdate
Cette ressource fait partie du jeu de données Réseau urbain SURF.
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
❌120 erreurs, 137 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 19/09/2025 à 09h10 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 9 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-712376334-22-__CJV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-712376336-22-__CJV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-712638494-22-__CJV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-712310789-22-__CJV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1-709361666-22-__CJV__ does not exist in the GTFS data and does not have schedule_relationship of ADDED
Sequential stop_time_update times are not increasing E022 109 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-691470341 stop_sequence 12 departure_time 09:09:53 (1758265793) is equal to previous stop departure_time 09:09:53 (1758265793) - times must increase between two sequential stops
- trip_id 1-724762628 stop_sequence 17 arrival_time 09:13:55 (1758266035) is equal to previous stop arrival_time 09:13:55 (1758266035) - times must increase between two sequential stops
- trip_id 1-724762628 stop_sequence 17 arrival_time 09:13:55 (1758266035) is equal to previous stop departure_time 09:13:55 (1758266035) - times must increase between two sequential stops
- trip_id 1-724762628 stop_sequence 17 departure_time 09:13:55 (1758266035) is equal to previous stop departure_time 09:13:55 (1758266035) - times must increase between two sequential stops
- trip_id 1-724762628 stop_sequence 17 departure_time 09:13:55 (1758266035) is equal to previous stop arrival_time 09:13:55 (1758266035) - 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 1-691470341 stop_sequence 12 departure_time 09:09:53 (1758265793) is less than the same stop arrival_time 09:10:13 (1758265813) - departure time must be equal to or greater than arrival time
- trip_id 1-762970113 stop_sequence 8 departure_time 09:10:15 (1758265815) is less than the same stop arrival_time 09:10:17 (1758265817) - departure time must be equal to or greater than arrival time
Avertissements
timestamp not populated W001 73 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 1-691666966 does not have a timestamp
- trip_id 1-712376334-22-__CJV__ does not have a timestamp
- trip_id 1-712704027 does not have a timestamp
- trip_id 1-691470341 does not have a timestamp
- trip_id 1-729219110 does not have a timestamp
vehicle_id not populated W002 64 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 1-712376336-22-__CJV__ does not have a vehicle_id
- trip_id 1-712638494-22-__CJV__ does not have a vehicle_id
- trip_id 1-712310789-22-__CJV__ does not have a vehicle_id
- trip_id 1-709361666-22-__CJV__ does not have a vehicle_id
- trip_id 1-712704032-22-__CJV__ 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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 1 575 | 26 fois (84 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 2 411 | 25 fois (81 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 373 | 25 fois (81 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 96 | 14 fois (45 % 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. | 14 | 8 fois (26 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 20/09/2025 à 04h42 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 20/09/2025 à 04h42 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1758336145"
}
}