Resource details

File name: Position des véhicules temps réel (GTFS-RT PROTOBUF) - réseau TIC (interurbain)
Format: gtfs-rt

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

2026-02-19
100%
2026-02-20
100%
2026-02-21
100%
2026-02-22
100%
2026-02-23
100%
2026-02-24
100%
2026-02-25
100%
2026-02-26
100%
2026-02-27
100%
2026-02-28
100%
2026-03-01
100%
2026-03-02
100%
2026-03-03
100%
2026-03-04
100%
2026-03-05
100%
2026-03-06
100%
2026-03-07
100%
2026-03-08
100%
2026-03-09
100%
2026-03-10
100%
2026-03-11
100%
2026-03-12
100%
2026-03-13
100%
2026-03-14
100%
2026-03-15
100%
2026-03-16
100%
2026-03-17
100%
2026-03-18
100%
2026-03-19
100%
2026-03-20
100%
2026-03-21
100%
Learn more
We test this resource download availability every hour by making an HTTP 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

1 error, 5 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-21 at 08:05 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

Vehicle position far from trip shape E029 1 error

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 7609 at (49.3959,2.8901727) 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 5 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 7659 does not have a schedule_relationship
  • trip_id 6730 does not have a schedule_relationship
  • trip_id 7609 does not have a schedule_relationship
  • trip_id 7650 does not have a schedule_relationship
  • trip_id 7714 does not have a schedule_relationship
Validate this GTFS-RT now

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 452 23 times (72 % 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. 58 19 times (59 % 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 (6 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 2 2 times (6 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-21 at 10:18 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-03-21 at 10:18 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1774084725" } }