Resource details
Données position des véhicules en temps réel, au format GTFS-RT PROTOBUF, du réseau TIC (interurbain)
This resource file is part of the dataset Réseau interurbain TIC.
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
❌3 errors, 33 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-11-21 at 08:11 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
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 TAC11057 trip_id 6416 at (49.423897,2.8760862) 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 TAC11052 trip_id 7608 at (49.39593,2.902085) 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 RCH12499 trip_id 7841 at (49.311333,2.7455354) 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 33 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 6416 does not have a schedule_relationship
- trip_id 7793 does not have a schedule_relationship
- trip_id 7620 does not have a schedule_relationship
- trip_id 7792 does not have a schedule_relationship
- trip_id 7646 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 | 245 | 12 times (40 % 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. | 29 | 8 times (27 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 4 | 4 times (13 % 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. | 2 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-11-21 at 14:59 Europe/Paris.
vehicle_positions (1) 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 2024-11-21 at 14:59 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "VM:6878",
"vehicle": {
"current_status": "IN_TRANSIT_TO",
"current_stop_sequence": 12,
"position": {
"bearing": 84.0,
"latitude": 49.42194366455078,
"longitude": 2.8243391513824463
},
"stop_id": "CGARE3",
"timestamp": "1732197267",
"trip": {
"direction_id": 1,
"route_id": "ARC Express",
"trip_id": "6878"
},
"vehicle": {
"id": "TAC10210"
}
}
}
],
"header": {
"gtfs_realtime_version": "1.0",
"timestamp": "1732197540"
}
}