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
❌76 erreurs, 7 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 26/11/2025 à 08h06 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
GTFS-rt stop_id does not exist in GTFS data E011 16 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id LA-01-03_0_0 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt
- trip_id TGV-02-01_1 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt
- trip_id TGV-01-04_5 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt
- trip_id LM-01-01_0_0 stop_id TROO - PLACE DE LA LIBERATION does not exist in GTFS data stops.txt
- trip_id LM-02-02_0_0 stop_id VENDOME - GARE TER LIGNE does not exist in GTFS data stops.txt
Vehicle position far from trip shape E029 1 erreur
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 62c5a41bd5f098dd792fcb19 trip_id LM-02-03_0_0 at (47.820713,0.9483263) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
stop_time_update doesn't have arrival or departure E043 41 erreurs
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Exemples d'erreurs
- trip_id LA-01-03_0_0 stop_sequence 1 doesn't have arrival or departure
- trip_id LA-01-03_0_0 stop_sequence 2 doesn't have arrival or departure
- trip_id LA-01-03_0_0 stop_sequence 3 doesn't have arrival or departure
- trip_id LA-01-03_0_0 stop_sequence 5 doesn't have arrival or departure
- trip_id LA-01-03_0_0 stop_sequence 6 doesn't have arrival or departure
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 16 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 LA-01-03_0_0 stop_sequence 23 has stop_id VENDOME - CITES UNIES but GTFS stop_sequence 23 has stop_id VENDOME - CITÉS UNIES - stop_ids should be the same
- GTFS-rt trip_id TGV-02-01_1 stop_sequence 1 has stop_id VENDOME - CITES UNIES but GTFS stop_sequence 1 has stop_id VENDOME - CITÉS UNIES - stop_ids should be the same
- GTFS-rt trip_id TGV-01-04_5 stop_sequence 9 has stop_id VENDOME - CITES UNIES but GTFS stop_sequence 9 has stop_id VENDOME - CITÉS UNIES - stop_ids should be the same
- GTFS-rt trip_id LM-01-01_0_0 stop_sequence 5 has stop_id TROO - PLACE DE LA LIBERATION but GTFS stop_sequence 5 has stop_id TROO - LE PONT - stop_ids should be the same
- GTFS-rt trip_id LM-02-02_0_0 stop_sequence 0 has stop_id VENDOME - GARE TER LIGNE but GTFS stop_sequence 0 has stop_id VENDOME - GARE TER LIGNE - 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 TGV-01-04_5 and vehicle_id 5f6d9a699fe0c8233a3636a0 pairing in VehiclePositions does not match trip_id TGV-01-02_2 and vehicle_id 5f6d9a699fe0c8233a3636a0 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id TGV-02-03_1 and vehicle_id 5f6d9a4e9fe0c822fdf0088b pairing in VehiclePositions does not match trip_id TGV-01-03_2 and vehicle_id 5f6d9a4e9fe0c822fdf0088b 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 7 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 TGV-01-01_2 is in TripUpdates but not in VehiclePositions feed
- trip_id TGV-01-02_2 is in TripUpdates but not in VehiclePositions feed
- trip_id TGV-01-03_2 is in TripUpdates but not in VehiclePositions feed
- trip_id TGV-02-02_4 is in TripUpdates but not in VehiclePositions feed
- trip_id LB-01-01_0_0 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 | 327 | 30 fois (100 % 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 | 293 | 30 fois (100 % 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 | 191 | 29 fois (97 % des validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 61 | 24 fois (80 % 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 | 236 | 17 fois (57 % 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. | 17 | 14 fois (47 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 38 | 8 fois (27 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 19 | 7 fois (23 % 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. | 4 | 4 fois (13 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 26/11/2025 à 23h01 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 26/11/2025 à 23h01 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1764194499"
}
}