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
❌6 errors, 3 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-10-29 at 08:05 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 3 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- vehicle_id 0200001002FF8218 trip_id 43 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 0200001002FF9707 trip_id 61 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 0200001002FFDAE6 trip_id 79 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 3 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 0200001002FF8218 route_id 530 does not exist in the GTFS data routes.txt
- vehicle_id 0200001002FF9707 route_id 530 does not exist in the GTFS data routes.txt
- vehicle_id 0200001002FFDAE6 route_id 26 does not exist in the GTFS data routes.txt
Warnings
schedule_relationship not populated W009 3 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 43 does not have a schedule_relationship
- trip_id 61 does not have a schedule_relationship
- trip_id 79 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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 38 | 21 times (70 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 38 | 21 times (70 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 38 | 21 times (70 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-10-29 at 17:51 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 2025-10-29 at 17:51 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "VM:477",
"vehicle": {
"position": {
"bearing": 72.0,
"latitude": 49.481201171875,
"longitude": 0.957444429397583
},
"timestamp": "1761756565",
"trip": {
"directionId": 1,
"routeId": "26",
"tripId": "477"
},
"vehicle": {
"id": "0200001002FF821F"
}
}
},
{
"id": "VM:461",
"vehicle": {
"position": {
"bearing": 313.0,
"latitude": 49.48236083984375,
"longitude": 1.0182689428329468
},
"timestamp": "1761756510",
"trip": {
"routeId": "26",
"tripId": "461"
},
"vehicle": {
"id": "0200001002FFDAE6"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1761756700"
}
}