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
❌28 erreurs, 9 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 18/02/2026 à 08h05 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 2 erreurs
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Exemples d'erreurs
- trip_id TGV-01-02_0_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id TGV-02-02_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt stop_id does not exist in GTFS data E011 9 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id TGV-01-02_0_0 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt
- trip_id TGV-01-01_1 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt
- trip_id TGV-01-03_3 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt
- trip_id TGV-02-02_0 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt
- trip_id TGV-01-04_3 stop_id VENDOME - CITES UNIES does not exist in GTFS data stops.txt
stop_time_update departure time is before arrival time E025 1 erreur
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 TGV-02-03_3 stop_sequence 5 departure_time 08:02:29 (1771398149) is less than the same stop arrival_time 08:03:42 (1771398222) - departure time must be equal to or greater than arrival time
stop_time_update doesn't have arrival or departure E043 9 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 TGV-01-02_0_0 stop_sequence 2 doesn't have arrival or departure
- trip_id TGV-01-01_1 stop_sequence 5 doesn't have arrival or departure
- trip_id TGV-01-01_1 stop_sequence 6 doesn't have arrival or departure
- trip_id TGV-01-03_3 stop_sequence 5 doesn't have arrival or departure
- trip_id TGV-01-03_3 stop_sequence 6 doesn't have arrival or departure
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 7 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 TGV-01-01_1 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 TGV-01-03_3 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 TGV-01-04_3 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 TGV-02-01_2 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-02-03_3 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
Avertissements
ID in one feed missing from the other W003 9 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_1 is in TripUpdates but not in VehiclePositions feed
- trip_id LA-01-02_0_3 is in TripUpdates but not in VehiclePositions feed
- trip_id LA-02-02_0_2 is in TripUpdates but not in VehiclePositions feed
- trip_id TGV-01-03_3 is in TripUpdates but not in VehiclePositions feed
- trip_id LA-01-03_0_2 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 | 464 | 29 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 | 459 | 29 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 | 264 | 29 fois (100 % des validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 94 | 24 fois (83 % 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 | 40 | 10 fois (34 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 27 | 7 fois (24 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 41 | 6 fois (21 % 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. | 7 | 6 fois (21 % 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 (7 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 18/02/2026 à 11h05 Europe/Paris.
service_alerts (2) vehicle_positions (1) trip_updates (1)Entités présentes dans ce flux lors des 7 derniers jours.
service_alerts trip_updates vehicle_positionsService alerts (infos trafic)
Voici un aperçu des informations de trafic présentes dans ce flux le 18/02/2026 à 11h05 Europe/Paris.
NAVETTE TGV - Modification service à compter du 16 février 2026 Service modifié
À compter du 16 FÉVRIER 2026, le service de 17h02 au départ de la Gare TER est avancé à 16H57. Vous trouverez ICI la nouvelle fiche horaire.
Du 06/02/2026 à 01h00 Europe/Paris au 16/03/2026 à 00h59 Europe/Paris
Modifications de services dues aux conditions climatiques Déviation
En raison des conditions climatiques actuelles, une déviation est mise en place pour la NAVETTE TGV dès cet après-midi, lundi 16 février, et ce jusqu'à nouvel ordre : l'arrêt CROIX BLANCHE est transféré à l'arrêt KENNEDY l'arrêt ZI NORD est transféré à l'arrêt JOUHAUX
Du 16/02/2026 à 01h00 Europe/Paris au 21/02/2026 à 00h59 Europe/Paris
Flux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 18/02/2026 à 11h05 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"entity": [
{
"id": "vehicle:5f6b208cf07eca4f072db425",
"vehicle": {
"currentStatus": "STOPPED_AT",
"currentStopSequence": 7,
"position": {
"latitude": 47.79509353637695,
"longitude": 1.0635299682617188
},
"stopId": "VENDOME - ST MICHEL",
"timestamp": "1771409127",
"trip": {
"routeId": "LIGNE A",
"scheduleRelationship": "SCHEDULED",
"tripId": "LA-01-07_0_2"
},
"vehicle": {
"id": "5f6b208cf07eca4f072db425",
"label": "603",
"licensePlate": "FS108QN"
}
}
},
{
"id": "trip:LA-01-07_0_2",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"time": "1771408594"
},
"departure": {
"time": "1771408626"
},
"stopId": "VENDOME - ZI SUD",
"stopSequence": 0
},
{
"arrival": {
"time": "1771408708"
},
"departure": {
"time": "1771408714"
},
"stopId": "VENDOME - EIFFEL",
"stopSequence": 1
},
{
"arrival": {
"time": "1771408753"
},
"departure": {
"time": "1771408763"
},
"stopId": "VENDOME - ROUTE DE BLOIS",
"stopSequence": 2
},
{
"arrival": {
"time": "1771408812"
},
"departure": {
"time": "1771408877"
},
"stopId": "VENDOME - OFFENBACH",
"stopSequence": 3
},
{
"arrival": {
"time": "1771408939"
},
"departure": {
"time": "1771408953"
},
"stopId": "VENDOME - ST LUBIN",
"stopSequence": 4
},
{
"arrival": {
"time": "1771409004"
},
"departure": {
"time": "1771409034"
},
"stopId": "VENDOME - ST GEORGES",
"stopSequence": 5
},
{
"arrival": {
"time": "1771409069"
},
"departure": {
"time": "1771409107"
},
"stopId": "VENDOME - HOPITAL",
"stopSequence": 6
},
{
"arrival": {
"time": "1771409127"
},
"stopId": "VENDOME - ST MICHEL",
"stopSequence": 7
},
{
"arrival": {
"time": "1771409200"
},
"departure": {
"time": "1771409200"
},
"stopId": "VENDOME - KENNEDY",
"stopSequence": 8
},
{
"arrival": {
"time": "1771409260"
},
"departure": {
"time": "1771409260"
},
"stopId": "VENDOME - GERARD YVON",
"stopSequence": 9
},
{
"arrival": {
"time": "1771409320"
},
"departure": {
"time": "1771409320"
},
"stopId": "VENDOME - ST VENANT",
"stopSequence": 10
},
{
"arrival": {
"time": "1771409500"
},
"departure": {
"time": "1771409500"
},
"stopId": "VENDOME - GARE TER",
"stopSequence": 11
},
{
"arrival": {
"time": "1771409620"
},
"departure": {
"time": "1771409620"
},
"stopId": "VENDOME - CIMETIERE NORD",
"stopSequence": 12
},
{
"arrival": {
"time": "1771409680"
},
"departure": {
"time": "1771409680"
},
"stopId": "VENDOME - BRANLY",
"stopSequence": 13
},
{
"arrival": {
"time": "1771409740"
},
"departure": {
"time": "1771409740"
},
"stopId": "VENDOME - DANAN",
"stopSequence": 14
},
{
"arrival": {
"time": "1771409800"
},
"departure": {
"time": "1771409800"
},
"stopId": "VENDOME - LYCEE RONSARD",
"stopSequence": 15
},
{
"arrival": {
"time": "1771409860"
},
"departure": {
"time": "1771409860"
},
"stopId": "VENDOME - EUROPE",
"stopSequence": 16
},
{
"arrival": {
"time": "1771409920"
},
"departure": {
"time": "1771409920"
},
"stopId": "VENDOME - JEAN MOULIN",
"stopSequence": 17
},
{
"arrival": {
"time": "1771409980"
},
"departure": {
"time": "1771409980"
},
"stopId": "VENDOME - JOUHAUX",
"stopSequence": 18
},
{
"arrival": {
"time": "1771410040"
},
"departure": {
"time": "1771410040"
},
"stopId": "VENDOME - INDUSTRIE",
"stopSequence": 19
},
{
"arrival": {
"time": "1771410100"
},
"departure": {
"time": "1771410100"
},
"stopId": "VENDOME - ST MARC",
"stopSequence": 20
},
{
"arrival": {
"time": "1771410220"
},
"departure": {
"time": "1771410220"
},
"stopId": "VENDOME - 4 TILLEULS",
"stopSequence": 21
}
],
"timestamp": "1771409127",
"trip": {
"routeId": "LIGNE A",
"scheduleRelationship": "SCHEDULED",
"tripId": "LA-01-07_0_2"
},
"vehicle": {
"id": "5f6b208cf07eca4f072db425",
"label": "603",
"licensePlate": "FS108QN"
}
}
},
{
"alert": {
"activePeriod": [
{
"end": "1773619140",
"start": "1770336000"
}
],
"cause": "OTHER_CAUSE",
"descriptionText": {
"translation": [
{
"text": "À compter du 16 FÉVRIER 2026, le service de 17h02 au départ de la Gare TER est avancé à 16H57.\n\nVous trouverez ICI la nouvelle fiche horaire."
}
]
},
"effect": "MODIFIED_SERVICE",
"headerText": {
"translation": [
{
"text": "NAVETTE TGV - Modification service à compter du 16 février 2026"
}
]
},
"informedEntity": [
{
"routeId": "NAVETTE TGV"
}
]
},
"id": "alert:69860517b43d113a8606f428"
},
{
"alert": {
"activePeriod": [
{
"end": "1771631940",
"start": "1771200000"
}
],
"cause": "WEATHER",
"descriptionText": {
"translation": [
{
"text": "En raison des conditions climatiques actuelles, une déviation est mise en place pour la NAVETTE TGV dès cet après-midi, lundi 16 février, et ce jusqu'à nouvel ordre :\n\nl'arrêt CROIX BLANCHE est transféré à l'arrêt KENNEDY\nl'arrêt ZI NORD est transféré à l'arrêt JOUHAUX"
}
]
},
"effect": "DETOUR",
"headerText": {
"translation": [
{
"text": "Modifications de services dues aux conditions climatiques"
}
]
},
"informedEntity": [
{
"routeId": "NAVETTE TGV"
},
{
"stopId": "VENDOME - CROIX BLANCHE"
},
{
"stopId": "VENDOME - ZI NORD"
}
]
},
"id": "alert:69931a6533566e95d7c0d3ec"
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1771409133"
}
}