Resource details

Format: gtfs-rt

Fichier GTFS-RT

This resource file is part of the dataset Réseau interurbain BreizhGo Car.

Download availability

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

Validation details

⚠️4 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2024-06-29 at 09:01 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 1 error

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 5-4598136876 does not have a vehicle_id

Header timestamp is older than 65 seconds W008 1 error

The data in a GTFS-realtime feed should always be less than one minute old

Sample errors
  • header.timestamp is 2156 min 55 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 2 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 5-4598136876 stop_sequence 6 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 5-4598136876 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 22 20 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 44 20 times (100 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 17 17 times (85 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-06-29 at 09:38 Europe/Paris.

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

The timestamp field appears to be too old compared to the current time: the delay is 4 185 seconds. Try to update your feed at most every 30 seconds.

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-06-29 at 09:38 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "SM:5-4599185488", "trip_update": { "stop_time_update": [ { "arrival": { "delay": 1, "time": "1719646880" }, "departure": { "delay": 1, "time": "1719646880" }, "stop_id": "JOS2A3", "stop_sequence": 4 }, { "arrival": { "delay": 1, "time": "1719647840" }, "departure": { "delay": 1, "time": "1719647840" }, "stop_id": "PLL1B3", "stop_sequence": 5 }, { "arrival": { "delay": 1, "time": "1719649220" }, "departure": { "delay": 1, "time": "1719649220" }, "stop_id": "GUR3A3", "stop_sequence": 6 }, { "arrival": { "delay": 1, "time": "1719651620" }, "departure": { "delay": 1, "time": "1719651620" }, "stop_id": "RNS2C1", "stop_sequence": 7 } ], "timestamp": "1719644790", "trip": { "route_id": "274", "trip_id": "5-4599185488" } } } ], "header": { "gtfs_realtime_version": "1.0", "timestamp": "1719646718" } }