Détails de la ressource
Gtfs-RT flux tripupdates : Mises à jour de trajets (retards, annulations, itinéraires modifiés) au format GTFS-RT
Cette ressource fait partie du jeu de données Réseau urbain SETRAM.
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
❌273 erreurs, 154 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 26/05/2026 à 09h05 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
GTFS-rt stop_id does not exist in GTFS data E011 23 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 4983170-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_id 1100 does not exist in GTFS data stops.txt
- trip_id 4983181-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_id 1100 does not exist in GTFS data stops.txt
- trip_id 4983171-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_id 1100 does not exist in GTFS data stops.txt
- trip_id 4983192-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_id 1100 does not exist in GTFS data stops.txt
- trip_id 4983202-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_id 1100 does not exist in GTFS data stops.txt
stop_times_updates not strictly sorted E002 7 erreurs
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Exemples d'erreurs
- trip_id 4983170-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_sequence for stop_ids [3182, 2547, 2440, 3229, 2183, 2788, 2599, 2524, 3011, 2116, 2205, 2378, 2521, 2475, 2027, 2798, 2832, 2279, 3097, 2809, 2458, 2835, 2015, 1100] is not strictly sorted by increasing stop_sequence
- trip_id 4983171-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_sequence for stop_ids [3182, 2547, 2440, 3229, 2183, 2788, 2599, 2524, 3011, 2116, 2205, 2378, 2521, 2475, 2027, 2798, 2832, 2279, 3097, 2809, 2458, 2835, 2015, 1100] is not strictly sorted by increasing stop_sequence
- trip_id 4983202-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_sequence for stop_ids [3182, 2547, 2440, 3229, 2183, 2788, 2599, 2524, 3011, 2116, 2205, 2378, 2521, 2475, 2027, 2798, 2832, 2279, 3097, 2809, 2458, 2835, 2015, 1100] is not strictly sorted by increasing stop_sequence
- trip_id 4982823-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_sequence for stop_ids [2714, 2254, 2299, 2322, 3095, 2571, 2755, 2485, 2842, 2084, 2403, 2492, 2203, 3039, 2679, 2044, 2064, 2361, 3258, 3260, 2443, 2171] is not strictly sorted by increasing stop_sequence
- trip_id 4982830-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_sequence for stop_ids [2171, 2444, 3261, 3259, 2360, 2063, 2045, 2678, 2389, 2204, 2491, 2404, 2085, 2843, 2484, 2107, 2756, 2572, 3094, 2323, 2298, 2883, 2714] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 151 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 4983882-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_id 2706 arrival_time 09:27:18 (1779780438) is less than previous stop arrival_time 09:27:27 (1779780447) - times must increase between two sequential stops
- trip_id 4983882-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_id 2706 arrival_time 09:27:18 (1779780438) is less than previous stop departure_time 09:27:27 (1779780447) - times must increase between two sequential stops
- trip_id 4983882-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_id 2706 departure_time 09:27:18 (1779780438) is less than previous stop departure_time 09:27:27 (1779780447) - times must increase between two sequential stops
- trip_id 4983882-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_id 2706 departure_time 09:27:18 (1779780438) is less than previous stop arrival_time 09:27:27 (1779780447) - times must increase between two sequential stops
- trip_id 4983882-B-PS26TV11-SE-PS-L-Ma-J-V-00 stop_id 2419 arrival_time 09:30:15 (1779780615) is less than previous stop arrival_time 09:30:24 (1779780624) - times must increase between two sequential stops
timestamp is in the future E050 92 erreurs
All timestamps must be less than the current time
Exemples d'erreurs
- header.timestamp 09:06:47 (1779779207) is 1 min 40 sec greater than 09:05:06 (1779779106098) - the current time in milliseconds
- trip_id 4983890-B-PS26TV11-SE-PS-L-Ma-J-V-00 timestamp 09:06:36 (1779779196) is 1 min 29 sec greater than 09:05:06 (1779779106098) - the current time in milliseconds
- trip_id 4983894-B-PS26TV11-SE-PS-L-Ma-J-V-00 timestamp 09:06:11 (1779779171) is 1 min 4 sec greater than 09:05:06 (1779779106098) - the current time in milliseconds
- trip_id 4983881-B-PS26TV11-SE-PS-L-Ma-J-V-00 timestamp 09:06:26 (1779779186) is 1 min 19 sec greater than 09:05:06 (1779779106098) - the current time in milliseconds
- trip_id 4983882-B-PS26TV11-SE-PS-L-Ma-J-V-00 timestamp 09:06:42 (1779779202) is 1 min 35 sec greater than 09:05:06 (1779779106098) - the current time in milliseconds
Avertissements
vehicle_id not populated W002 154 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 4983894-B-PS26TV11-SE-PS-L-Ma-J-V-00 does not have a vehicle_id
- trip_id 4983906-B-PS26TV11-SE-PS-L-Ma-J-V-00 does not have a vehicle_id
- trip_id 4983907-B-PS26TV11-SE-PS-L-Ma-J-V-00 does not have a vehicle_id
- trip_id 4983892-B-PS26TV11-SE-PS-L-Ma-J-V-00 does not have a vehicle_id
- trip_id 4983893-B-PS26TV11-SE-PS-L-Ma-J-V-00 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 |
|---|---|---|---|
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 162 | 29 fois (97 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 475 | 29 fois (97 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 3 116 | 29 fois (97 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 3 282 | 29 fois (97 % des validations) |
| E050 | All timestamps must be less than the current time | 902 | 28 fois (93 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 27 | 2 fois (7 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 2 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 27/05/2026 à 03h30 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 27/05/2026 à 03h30 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1779845434"
}
}