Resource details
GTFS-RT (protobuff) de la position des véhicules.
This resource file is part of the dataset Réseau urbain Transurbain.
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
❌23 errors, 22 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-02-22 at 08:02 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 22 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 19 stop_id LEB01 does not exist in GTFS data stops.txt
- vehicle_id 13 stop_id CAM01 does not exist in GTFS data stops.txt
- vehicle_id 44 stop_id MOL01 does not exist in GTFS data stops.txt
- vehicle_id 42 stop_id BER02 does not exist in GTFS data stops.txt
- vehicle_id 45 stop_id BRI02 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 2402 trip_id ATOUMOD004:ServiceJourney:491893:LOC at (49.02771,1.154736) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
Warnings
schedule_relationship not populated W009 22 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id ATOUMOD004:ServiceJourney:490442:LOC does not have a schedule_relationship
- trip_id ATOUMOD004:ServiceJourney:490094:LOC does not have a schedule_relationship
- trip_id ATOUMOD004:ServiceJourney:490070:LOC does not have a schedule_relationship
- trip_id ATOUMOD004:ServiceJourney:491143:LOC does not have a schedule_relationship
- trip_id ATOUMOD004:ServiceJourney:490087:LOC 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 |
|---|---|---|---|
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 788 | 26 times (87 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 788 | 26 times (87 % 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. | 68 | 23 times (77 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 6 | 6 times (20 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-02-22 at 22:18 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (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-02-22 at 22:18 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "1.0",
"timestamp": "1740259117"
}
}