Resource details

File name: Ar bus - Landerneau-Daoulas
Format: gtfs-rt

Fichier GTFS-RT

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

Download availability

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

⚠️16 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-03-12 at 08:02 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 5 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 3 scolaire 7:32 does not have a vehicle_id
  • trip_id 4 scolaire 07:35 does not have a vehicle_id
  • trip_id 5 scolaire 07:29 does not have a vehicle_id
  • trip_id 1 scolaire 07:41 does not have a vehicle_id
  • trip_id 2 scolaire 8:00 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 9 min 34 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 10 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id 3 scolaire 7:32 stop_sequence 14 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 3 scolaire 7:32 does not have a schedule_relationship
  • trip_id 4 scolaire 07:35 stop_sequence 19 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 4 scolaire 07:35 does not have a schedule_relationship
  • trip_id 5 scolaire 07:29 stop_sequence 21 (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 77 30 times (100 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 30 30 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 154 30 times (100 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-03-12 at 19:39 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 29 930 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 2025-03-12 at 19:39 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "SM:1 scolaire 19:20", "trip_update": { "stop_time_update": [ { "arrival": { "delay": -140, "time": "1741804780" }, "stop_id": "12", "stop_sequence": 19 } ], "timestamp": "1741804737", "trip": { "route_id": "1", "trip_id": "1 scolaire 19:20" } } } ], "header": { "gtfs_realtime_version": "1.0", "timestamp": "1741804792" } }