Détails de la ressource
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
- VehiclePosition
- TripUpdate
- ServiceAlert
Cette ressource fait partie du jeu de données Réseau urbain et scolaire Lila Presqu'ile.
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
❌34 erreurs
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 12/03/2026 à 08h13 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
stop_times_updates not strictly sorted E002 1 erreur
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Exemples d'erreurs
- trip_id 310-50987085 stop_sequence [17, 18, 19, 20, 21, 22, 23, 24, 26, 26] is not strictly sorted by increasing stop_sequence
Vehicle position far from trip shape E029 7 erreurs
The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id.
Exemples d'erreurs
- vehicle.id 44 trip_id 310-2986409985 at (47.338383,-2.421438) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 46 trip_id 310-3607298049 at (47.493458,-2.314445) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 54 trip_id 310-3707830273 at (47.44543,-2.320583) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 60 trip_id 310-3170959361 at (47.330765,-2.370201) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 79 trip_id 310-50462751 at (47.277206,-2.337471) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
Sequential stop_time_updates have the same stop_sequence E036 1 erreur
Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence
Exemples d'erreurs
- trip_id 310-50987085 has repeating stop_sequence 26 - stop_sequence must increase for each stop_time_update
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 24 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 310-50987084 stop_sequence 27 has stop_id 265 but GTFS stop_sequence 27 has stop_id 263 - stop_ids should be the same
- GTFS-rt trip_id 310-50987084 stop_sequence 28 has stop_id 1969 but GTFS stop_sequence 28 has stop_id 265 - stop_ids should be the same
- GTFS-rt trip_id 310-4278255743 stop_sequence 13 has stop_id 367 but GTFS stop_sequence 13 has stop_id 1677 - stop_ids should be the same
- GTFS-rt trip_id 310-4278255743 stop_sequence 14 has stop_id 322 but GTFS stop_sequence 14 has stop_id 367 - stop_ids should be the same
- GTFS-rt trip_id 310-4278255743 stop_sequence 15 has stop_id 329 but GTFS stop_sequence 15 has stop_id 322 - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 1 erreur
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 310-50987085 contains stop_sequence 26 that does not exist in GTFS stop_times.txt for this trip
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 | 53 | 25 fois (81 % des validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 53 | 25 fois (81 % 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 | 188 | 25 fois (81 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 53 | 25 fois (81 % des validations) |
| E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 80 | 16 fois (52 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 11 | 3 fois (10 % des validations) |
| W001 | Timestamps should be populated for all elements | 42 | 3 fois (10 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 42 | 3 fois (10 % des validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 42 | 3 fois (10 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 4 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 13/03/2026 à 00h23 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entités présentes dans ce flux lors des 7 derniers jours.
trip_updates vehicle_positionsFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 13/03/2026 à 00h23 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1773357825"
}
}