Resource details
Gtfs-RT flux vehicleposition: Mises à jour de la position des véhicules au format GTFS-RT
This resource file is part of the dataset Réseau urbain SETRAM.
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
❌7 errors, 21 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-03 at 09:01 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 3 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 228 stop_id 35 does not exist in GTFS data stops.txt
- vehicle_id 407 stop_id 683 does not exist in GTFS data stops.txt
- vehicle_id 907 stop_id 35 does not exist in GTFS data stops.txt
Vehicle position far from trip shape E029 4 errors
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 144 trip_id 4169586-B-PS24TVX4-SEMTVX4-L-Ma-J-V-00 at (48.006317,0.196797) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 423 trip_id 4169637-B-PS24TVX4-SEMTVX4-L-Ma-J-V-00 at (47.979603,0.223437) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 1010 trip_id 4507024-T-PS25TAC3-SEMTACP3-Semaine-00 at (47.96112,0.226957) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id 1026 trip_id 4507023-T-PS25TAC3-SEMTACP3-Semaine-00 at (47.95608,0.222317) 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
vehicle speed is unrealistic W004 21 errors
vehicle.position.speed has an unrealistic speed that may be incorrect
Sample errors
- vehicle.id 103 speed of 30.0 m/s (67.11 mph) is unrealistic
- vehicle.id 104 speed of 59.0 m/s (131.98 mph) is unrealistic
- vehicle.id 105 speed of 34.0 m/s (76.06 mph) is unrealistic
- vehicle.id 106 speed of 54.0 m/s (120.79 mph) is unrealistic
- vehicle.id 119 speed of 32.0 m/s (71.58 mph) is unrealistic
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 |
---|---|---|---|
W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 301 | 16 times (100 % 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. | 83 | 15 times (94 % of validations) |
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 38 | 14 times (88 % of validations) |
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 10 | 1 times (6 % of validations) |
E024 | GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt | 35 | 1 times (6 % of validations) |
E035 | The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt | 39 | 1 times (6 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-04-04 at 03:27 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-04-04 at 03:27 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1743730042"
}
}