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

2025-03-05
100%
2025-03-06
90.8%
2025-03-07
100%
2025-03-08
100%
2025-03-09
100%
2025-03-10
100%
2025-03-11
100%
2025-03-12
100%
2025-03-13
100%
2025-03-14
100%
2025-03-15
100%
2025-03-16
100%
2025-03-17
100%
2025-03-18
100%
2025-03-19
100%
2025-03-20
100%
2025-03-21
100%
2025-03-22
100%
2025-03-23
100%
2025-03-24
100%
2025-03-25
99.3%
2025-03-26
100%
2025-03-27
99.8%
2025-03-28
100%
2025-03-29
100%
2025-03-30
100%
2025-03-31
99.8%
2025-04-01
99.3%
2025-04-02
99.8%
2025-04-03
99.8%
2025-04-04
99.7%
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

1 error, 3 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-04 at 09:09 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

VehiclePosition and TripUpdate ID pairing mismatch E047 1 error

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_0_1 and vehicle_id 62babc77f4336585d60d0e29 pairing in VehiclePositions does not match trip_id LB-01-01_0_1 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 3 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 LB-01-01_0_1 is in TripUpdates but not in VehiclePositions feed
  • trip_id TGV-02-04_5 is in TripUpdates but not in VehiclePositions feed
  • trip_id LB-02-01_0_1 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
E047 If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. 1 1 times (100 % 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 3 1 times (100 % of validations)

GTFS-RT feed content

Could not decode the GTFS-RT feed.

The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.