Resource details
Flux temps réel du réseau MOVE
This resource file is part of the dataset Réseau urbain Move.
Download availability
Learn more
HEAD request with a timeout of 5 seconds. If we detect a downtime, we perform subsequent tests every 10 minutes, until the resource is back online.For SIRI and SIRI Lite feeds, we perform a
GET request: a 401 or 405 status code is considered successful. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.Validation details
❌29 errors, 8 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-29 at 09:00 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 12 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- 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 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- 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 errors
If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt
Sample errors
- 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 errors
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Sample errors
- 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
Warnings
ID in one feed missing from the other W003 8 errors
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
Sample errors
- 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
Previous validations
Here is a recap of all the error types encountered over the last 30 days.
| Error ID | Description | Errors count | Number of occurences |
|---|---|---|---|
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 297 | 25 times (81 % of 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 times (81 % of 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 times (81 % of validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 48 | 24 times (77 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 31 | 10 times (32 % of 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 times (32 % of 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 times (13 % of 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 times (6 % of 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 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-30 at 02:43 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
service_alerts trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-09-30 at 02:43 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1759193007"
}
}