Resource details
This resource file is part of the dataset Réseau urbain RLV Mobilités.
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
❌92 errors, 46 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-30 at 09:01 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 46 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- trip_id 34534_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 34535_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 34522_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 34681_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 34678_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 46 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id 4 does not exist in the GTFS data routes.txt
- route_id 4 does not exist in the GTFS data routes.txt
- route_id 4 does not exist in the GTFS data routes.txt
- route_id 1 does not exist in the GTFS data routes.txt
- route_id 1 does not exist in the GTFS data routes.txt
Warnings
vehicle_id not populated W002 46 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 34534_0 does not have a vehicle_id
- trip_id 34535_0 does not have a vehicle_id
- trip_id 34522_0 does not have a vehicle_id
- trip_id 34681_0 does not have a vehicle_id
- trip_id 34678_0 does not have a vehicle_id
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 |
---|---|---|---|
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1 037 | 25 times (86 % of validations) |
E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 037 | 25 times (86 % of validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 037 | 25 times (86 % of validations) |
E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 6 | 5 times (17 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-07-01 at 05:17 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-07-01 at 05:17 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1751339853"
}
}