Resource details

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

Données position des véhicules en temps réel, au format GTFS-RT PROTOBUF, du réseau TIC (urbain)

This resource file is part of the dataset Réseau urbain TIC.

Download availability

2024-10-24
100%
2024-10-25
100%
2024-10-26
100%
2024-10-27
100%
2024-10-28
100%
2024-10-29
100%
2024-10-30
100%
2024-10-31
100%
2024-11-01
100%
2024-11-02
100%
2024-11-03
100%
2024-11-04
100%
2024-11-05
100%
2024-11-06
100%
2024-11-07
100%
2024-11-08
100%
2024-11-09
100%
2024-11-10
100%
2024-11-11
100%
2024-11-12
100%
2024-11-13
100%
2024-11-14
100%
2024-11-15
100%
2024-11-16
100%
2024-11-17
100%
2024-11-18
100%
2024-11-19
100%
2024-11-20
100%
2024-11-21
100%
2024-11-22
100%
2024-11-23
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, 18 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2024-11-23 at 08:07 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 TAC215 trip_id 7367-M17-LMCJVS_ at (49.43686,2.8342528) 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 18 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 7468-M04-_____S_ does not have a schedule_relationship
  • trip_id 7335-M06-LMCJVS_ does not have a schedule_relationship
  • trip_id 7145-M10-_____S_ does not have a schedule_relationship
  • trip_id 7449-M11-LMCJVS_ does not have a schedule_relationship
  • trip_id 6986-M08-_____S_ 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 444 24 times (80 % 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. 20 15 times (50 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 7 7 times (23 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-11-23 at 23:14 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (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 2024-11-23 at 23:14 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfs_realtime_version": "1.0", "timestamp": "1732400085" } }