Resource details
GTFS-RT : Mise à jour des informations de position des bus du STAR en temps réel
This resource file is part of the dataset Réseau urbain STAR.
Related resources
GTFS (Version en cours)
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
❌5 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2025-07-26 at 09:07 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 2 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 603 stop_id 5-9815 does not exist in GTFS data stops.txt
- vehicle_id 6030 stop_id 5-9821 does not exist in GTFS data stops.txt
Vehicle position far from trip shape E029 3 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 603 trip_id 17_SAMEDI-16099337 at (48.08207,-1.71596) 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 707 trip_id 17_SAMEDI-16097752 at (48.12719,-1.670387) 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 1009 trip_id 17_SAMEDI-16099131 at (48.15472,-1.710476) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
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 |
|---|---|---|---|
| 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. | 65 | 9 times (90 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 20 | 7 times (70 % of validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 2 | 2 times (20 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-07-27 at 01:45 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-27 at 01:45 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1753573555"
}
}