Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain TGL.
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
❌640 erreurs, 161 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 01/12/2025 à 08h11 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
Sequential stop_time_update times are not increasing E022 486 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 176876-2020-_ABCDSN-Semaine-01 stop_sequence 35 arrival_time 08:23:39 (1764573819) is equal to previous stop arrival_time 08:23:39 (1764573819) - times must increase between two sequential stops
- trip_id 176876-2020-_ABCDSN-Semaine-01 stop_sequence 35 arrival_time 08:23:39 (1764573819) is equal to previous stop departure_time 08:23:39 (1764573819) - times must increase between two sequential stops
- trip_id 176876-2020-_ABCDSN-Semaine-01 stop_sequence 35 departure_time 08:23:39 (1764573819) is equal to previous stop departure_time 08:23:39 (1764573819) - times must increase between two sequential stops
- trip_id 176876-2020-_ABCDSN-Semaine-01 stop_sequence 35 departure_time 08:23:39 (1764573819) is equal to previous stop arrival_time 08:23:39 (1764573819) - times must increase between two sequential stops
- trip_id 176711-2020-_ABCDSN-Semaine-01 stop_sequence 3 arrival_time 07:37:28 (1764571048) is less than previous stop departure_time 08:10:49 (1764573049) - times must increase between two sequential stops
trip start_time does not match first GTFS arrival_time E023 1 erreur
For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip
Exemples d'erreurs
- GTFS-rt trip_id d3525cf6-5cc7-4697-9b63-1546088dddc8 start_time is 07:45:00 and GTFS initial arrival_time is 07:49:00 - times do not match
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 3ca92c7d-1298-4599-9345-0386f3d0040a stop_sequence 25 departure_time 11:39:26 (1764585566) is less than the same stop arrival_time 11:40:26 (1764585626) - departure time must be equal to or greater than arrival time
- trip_id f570359b-7224-4ffe-8b90-853813fa8c29 stop_sequence 25 departure_time 18:37:26 (1764610646) is less than the same stop arrival_time 18:38:26 (1764610706) - departure time must be equal to or greater than arrival time
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 145 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 d3525cf6-5cc7-4697-9b63-1546088dddc8 stop_sequence 1 has stop_id STP-2001R but GTFS stop_sequence 1 has stop_id 05020 - stop_ids should be the same
- GTFS-rt trip_id d3525cf6-5cc7-4697-9b63-1546088dddc8 stop_sequence 2 has stop_id 05020 but GTFS stop_sequence 2 has stop_id 1705A - stop_ids should be the same
- GTFS-rt trip_id d3525cf6-5cc7-4697-9b63-1546088dddc8 stop_sequence 3 has stop_id 1705A but GTFS stop_sequence 3 has stop_id 1706A - stop_ids should be the same
- GTFS-rt trip_id d3525cf6-5cc7-4697-9b63-1546088dddc8 stop_sequence 4 has stop_id 1706A but GTFS stop_sequence 4 has stop_id 1707A - stop_ids should be the same
- GTFS-rt trip_id d3525cf6-5cc7-4697-9b63-1546088dddc8 stop_sequence 5 has stop_id 1707A but GTFS stop_sequence 5 has stop_id 1700A - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 6 erreurs
All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip
Exemples d'erreurs
- GTFS-rt trip_id 349a5998-1249-4675-a887-c57b59a57c7c contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id b1290f90-21fd-4e05-aa17-47bcdcf16bef contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id c6dd3725-7faa-44ae-9a9b-3e71e3d76fdd contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 30b080b0-b9d8-4db9-bcd9-9cbd037bb3bc contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 9c5e35b5-3d28-4ed8-83f7-df0deb134bf7 contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
Avertissements
timestamp not populated W001 89 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 176859-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id 176876-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id 176711-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id 176740-2020-_ABCDSN-Semaine-01 does not have a timestamp
- trip_id d3525cf6-5cc7-4697-9b63-1546088dddc8 does not have a timestamp
vehicle_id not populated W002 72 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 176750-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 176747-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 176744-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 176741-2020-_ABCDSN-Semaine-01 does not have a vehicle_id
- trip_id 176720-2020-_ABCDSN-Semaine-01 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 |
|---|---|---|---|
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 9 226 | 24 fois (80 % 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. | 63 | 24 fois (80 % 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 | 2 686 | 24 fois (80 % des validations) |
| W001 | Timestamps should be populated for all elements | 1 847 | 24 fois (80 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 479 | 24 fois (80 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 102 | 23 fois (77 % des validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 16 | 16 fois (53 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 01/12/2025 à 23h56 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 01/12/2025 à 23h56 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1764629763"
}
}