Resource details

File name: Horaire temps réel (GTFS-RT PROTOBUF) - réseau TIC (urbain)
Format: gtfs-rt

Données horaires 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-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%
2024-11-24
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

⚠️159 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.

Warnings

vehicle_id not populated W002 53 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 7041-M07-_____S_ does not have a vehicle_id
  • trip_id 7282-M03-_____S_ does not have a vehicle_id
  • trip_id 6957-M07-_____S_ does not have a vehicle_id
  • trip_id 6985-M14-_____S_ does not have a vehicle_id
  • trip_id 6986-M08-_____S_ does not have a vehicle_id

schedule_relationship not populated W009 106 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 7041-M07-_____S_ stop_sequence 2 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 7041-M07-_____S_ does not have a schedule_relationship
  • trip_id 7282-M03-_____S_ stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 7282-M03-_____S_ does not have a schedule_relationship
  • trip_id 6957-M07-_____S_ stop_sequence 1 (and potentially more for this trip) 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
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 1 358 24 times (80 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 2 708 24 times (80 % of validations)
E025 Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. 1 1 times (3 % 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 2024-11-24 at 01:13 Europe/Paris.

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

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2024-11-24 at 01:13 Europe/Paris. You can look at the GTFS-RT documentation.

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