Détails de la ressource
Flux temps réel du réseau MOVE
Cette ressource fait partie du jeu de données Réseau urbain Move.
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
❌29 erreurs, 8 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 29/09/2025 à 09h00 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
GTFS-rt stop_id does not exist in GTFS data E011 12 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- vehicle_id ba587ff82fd3146c stop_id NAVEIL - SQUARE LIBERTE does not exist in GTFS data stops.txt
- trip_id LB-01-02 stop_id VENDOME - LIBERTE does not exist in GTFS data stops.txt
- trip_id LB-01-02 stop_id VENDOME - ST BIENHEURE does not exist in GTFS data stops.txt
- trip_id LB-01-02 stop_id AREINES - AMPHITHEATRE does not exist in GTFS data stops.txt
- trip_id LB-01-01 stop_id VENDOME - LIBERTE does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 4 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 LC-01-02 stop_sequence 9 arrival_time 08:49:18 (1759128558) is less than previous stop arrival_time 08:51:01 (1759128661) - times must increase between two sequential stops
- trip_id LC-01-02 stop_sequence 9 arrival_time 08:49:18 (1759128558) is less than previous stop departure_time 08:51:14 (1759128674) - times must increase between two sequential stops
- trip_id LC-01-02 stop_sequence 9 departure_time 08:50:11 (1759128611) is less than previous stop departure_time 08:51:14 (1759128674) - times must increase between two sequential stops
- trip_id LC-01-02 stop_sequence 9 departure_time 08:50:11 (1759128611) is less than previous stop arrival_time 08:51:01 (1759128661) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 11 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 LB-01-02 stop_sequence 8 has stop_id VENDOME - LIBERTE but GTFS stop_sequence 8 has stop_id VENDOME - LIBERTÉ - stop_ids should be the same
- GTFS-rt trip_id LB-01-02 stop_sequence 9 has stop_id VENDOME - ST BIENHEURE but GTFS stop_sequence 9 has stop_id VENDOME - ST BIENHEURÉ - stop_ids should be the same
- GTFS-rt trip_id LB-01-02 stop_sequence 10 has stop_id AREINES - AMPHITHEATRE but GTFS stop_sequence 10 has stop_id AREINES - AMPHITHÉÂTRE - stop_ids should be the same
- GTFS-rt trip_id LB-01-01 stop_sequence 8 has stop_id VENDOME - LIBERTE but GTFS stop_sequence 8 has stop_id VENDOME - LIBERTÉ - stop_ids should be the same
- GTFS-rt trip_id LB-01-01 stop_sequence 9 has stop_id VENDOME - ST BIENHEURE but GTFS stop_sequence 9 has stop_id VENDOME - ST BIENHEURÉ - stop_ids should be the same
VehiclePosition and TripUpdate ID pairing mismatch E047 2 erreurs
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Exemples d'erreurs
- trip_id LB-01-02 and vehicle_id 5f6d9a5d9fe0c82317175d1f pairing in VehiclePositions does not match trip_id LB-02-01 and vehicle_id 5f6d9a5d9fe0c82317175d1f pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id LA-02-04 and vehicle_id 5f6b207af07eca4ec325afdc pairing in VehiclePositions does not match trip_id LA-01-04 and vehicle_id 5f6b207af07eca4ec325afdc pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
Avertissements
ID in one feed missing from the other W003 8 erreurs
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
Exemples d'erreurs
- trip_id LA-02-01 is in TripUpdates but not in VehiclePositions feed
- trip_id LA-02-02 is in TripUpdates but not in VehiclePositions feed
- trip_id LA-02-03 is in TripUpdates but not in VehiclePositions feed
- trip_id LA-01-03 is in TripUpdates but not in VehiclePositions feed
- trip_id LA-01-02 is in TripUpdates but not in VehiclePositions feed
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 |
|---|---|---|---|
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 297 | 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 | 274 | 25 fois (81 % 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 | 207 | 25 fois (81 % des validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 48 | 24 fois (77 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 31 | 10 fois (32 % des validations) |
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 24 | 10 fois (32 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 16 | 4 fois (13 % 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. | 2 | 2 fois (6 % 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. | 1 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 30/09/2025 à 00h32 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entités présentes dans ce flux lors des 7 derniers jours.
service_alerts trip_updates vehicle_positionsFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 30/09/2025 à 00h32 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1759185125"
}
}