Resource details
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
- VehiclePosition
This resource file is part of the dataset Réseau urbain SURF.
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
⚠️1 warning
Validation carried out using the current GTFS file and the GTFS-RT the 2025-07-10 at 09:05 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
timestamp not populated W001 1 error
Timestamps should be populated for all elements
Sample errors
- vehicle_id 11 does not have a timestamp
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 | 18 | 18 times (62 % of validations) |
| W001 | Timestamps should be populated for all elements | 9 | 9 times (31 % 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. | 7 | 4 times (14 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-07-11 at 05:19 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 2025-07-11 at 05:19 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1752203940"
}
}