gtfs-rt Transport open dataset - Ar bus - Landerneau-Daoulas for Réseau urbain Ar bus

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

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, 4 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-01 at 08:04 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 1 error

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors

trip_id 1 vacances 19:20 does not exist in the GTFS data and does not have schedule_relationship of ADDED

Warnings

vehicle_id not populated W002 1 error

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 1 vacances 19:20 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 744 min 21 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 1 vacances 19:20 stop_sequence 19 (and potentially more for this trip) does not have a schedule_relationship
trip_id 1 vacances 19:20 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	97	29 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	194	29 times (100 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	28	28 times (97 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	1	1 times (3 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	2	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-10-31 at 19:40 Europe/Paris.

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

The timestamp field appears to be too old compared to the current time: the delay is 91 587 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-10-31 at 19:40 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "SM:1 vacances 19:20",
      "tripUpdate": {
        "stopTimeUpdate": [
          {
            "arrival": {
              "delay": 120,
              "time": "1761936000"
            },
            "stopId": "12",
            "stopSequence": 19
          }
        ],
        "timestamp": "1761935935",
        "trip": {
          "routeId": "1",
          "tripId": "1 vacances 19:20"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "1.0",
    "timestamp": "1761936014"
  }
}