Resource details
This resource file is part of the dataset Réseau urbain Maelis.
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
❌14 errors, 9 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-07-27 at 09:06 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 7 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- vehicle_id 2495 trip_id 9222333 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 2387 trip_id 9222357 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 2494 trip_id 9222452 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 2440 trip_id 9222319 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 2384 trip_id 9222376 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 7 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 2495 stop_id 1697713 does not exist in GTFS data stops.txt
- vehicle_id 2387 stop_id 1697676 does not exist in GTFS data stops.txt
- vehicle_id 2494 stop_id 1697718 does not exist in GTFS data stops.txt
- vehicle_id 2440 stop_id 1697927 does not exist in GTFS data stops.txt
- vehicle_id 2384 stop_id 1697532 does not exist in GTFS data stops.txt
Warnings
vehicle speed is unrealistic W004 2 errors
vehicle.position.speed has an unrealistic speed that may be incorrect
Sample errors
- vehicle.id 2387 speed of 32.0 m/s (71.58 mph) is unrealistic
- vehicle.id 2384 speed of 34.0 m/s (76.06 mph) is unrealistic
schedule_relationship not populated W009 7 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 9222333 does not have a schedule_relationship
- trip_id 9222357 does not have a schedule_relationship
- trip_id 9222452 does not have a schedule_relationship
- trip_id 9222319 does not have a schedule_relationship
- trip_id 9222376 does not have a schedule_relationship
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 |
|---|---|---|---|
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 74 | 8 times (80 % of validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 27 | 7 times (70 % 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. | 5 | 4 times (40 % of validations) |
| E012 | No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp | 5 | 3 times (30 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 7 | 1 times (10 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 7 | 1 times (10 % of validations) |
| E028 | The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. | 1 | 1 times (10 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-07-29 at 22:15 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-07-29 at 22:15 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1785356104"
}
}