Resource details
Ce fichier au format GTFS-RT contient la position des véhicules en temps réel (vehicle position) pour les lignes exploitées par TNI, à savoir les lignes 26 et 530.
La fréquence de rafraîchissement de ces données est de 30 secondes.
This resource file is part of the dataset Réseau urbain Astuce.
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
❌2 errors, 3 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-09-18 at 09:11 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Vehicle position far from trip shape E029 2 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 0200001002FF8217 trip_id TNI:31 at (49.42057,1.106094) 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 0200001002FF7E01 trip_id TNI:75 at (49.45038,1.059811) 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 3 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id TNI:31 does not have a schedule_relationship
- trip_id TNI:73 does not have a schedule_relationship
- trip_id TNI:75 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 | 60 | 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. | 9 | 7 times (23 % 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 (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-09-19 at 02:48 Europe/Paris.
vehicle_positions (2) 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-09-19 at 02:48 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "VM:TNI:31",
"vehicle": {
"position": {
"latitude": 49.42055892944336,
"longitude": 1.1046390533447266
},
"timestamp": "1789740547",
"trip": {
"directionId": 1,
"routeId": "TNI:530",
"tripId": "TNI:31"
},
"vehicle": {
"id": "0200001002FF8217"
}
}
},
{
"id": "VM:TNI:201",
"vehicle": {
"position": {
"bearing": 287.0,
"latitude": 49.44655990600586,
"longitude": 0.9840111136436462
},
"timestamp": "1789739627",
"trip": {
"routeId": "TNI:530",
"tripId": "TNI:201"
},
"vehicle": {
"id": "0200001002FF821B"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1789778895"
}
}