gtfs-rt Transport open dataset - GTFS-RT MOVE for Réseau urbain Move

Resource details

File name: GTFS-RT MOVE

Format: gtfs-rt

Flux temps réel du réseau MOVE

This resource file is part of the dataset Réseau urbain Move.

Download availability

Learn more

We test this resource download availability every hour by making an HTTP 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

❌37 errors, 10 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-19 at 08:02 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt stop_id does not exist in GTFS data E011 16 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors

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-03_0_0 stop_id VENDOME - GARE TER LIGNE does not exist in GTFS data stops.txt
trip_id LB-02-01_0_0 stop_id AREINES - AMPHITHEATRE does not exist in GTFS data stops.txt
trip_id LB-02-01_0_0 stop_id VENDOME - ST BIENHEURE does not exist in GTFS data stops.txt

Vehicle position far from trip shape E029 1 error

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.

Sample errors

vehicle.id 62c5a41bd5f098dd792fcb19 trip_id LM-02-03_0_0 at (47.817516,0.9520547) 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 1 error

If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided

Sample errors

trip_id LA-02-02_0_0 stop_sequence 17 doesn't have arrival or departure

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 16 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 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-03_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
GTFS-rt trip_id LB-02-01_0_0 stop_sequence 1 has stop_id AREINES - AMPHITHEATRE but GTFS stop_sequence 1 has stop_id AREINES - AMPHITHÉÂTRE - stop_ids should be the same
GTFS-rt trip_id LB-02-01_0_0 stop_sequence 3 has stop_id VENDOME - ST BIENHEURE but GTFS stop_sequence 3 has stop_id VENDOME - ST BIENHEURÉ - stop_ids should be the same

VehiclePosition and TripUpdate ID pairing mismatch E047 3 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 TGV-01-04_5 and vehicle_id 5f6d9a699fe0c8233a3636a0 pairing in VehiclePositions does not match trip_id TGV-02-02_4 and vehicle_id 5f6d9a699fe0c8233a3636a0 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
trip_id LA-01-04_0_0 and vehicle_id 5f6b207af07eca4ec325afdc pairing in VehiclePositions does not match trip_id LA-02-02_0_0 and vehicle_id 5f6b207af07eca4ec325afdc pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
trip_id LB-02-01_0_0 and vehicle_id 62babc77f4336585d60d0e29 pairing in VehiclePositions does not match trip_id LB-01-01_0_0 and vehicle_id 62babc77f4336585d60d0e29 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 10 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 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 LA-02-02_0_0 is in TripUpdates but not in VehiclePositions feed
trip_id LA-01-02_0_0 is in TripUpdates but not in VehiclePositions feed
trip_id TGV-01-03_2 is in TripUpdates but not in VehiclePositions feed

Validate this GTFS-RT now

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
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	167	28 times (93 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	250	26 times (87 % 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	223	26 times (87 % of validations)
E047	If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.	53	23 times (77 % 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	182	13 times (43 % 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.	13	10 times (33 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	30	8 times (27 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	11	5 times (17 % 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.	4	4 times (13 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	1	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-11-20 at 00:30 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-11-20 at 00:30 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1763595024"
  }
}