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.

Validation details

⚠️13 warnings

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

Warnings

vehicle_id not populated W002 4 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 1 scolaire 07:41 does not have a vehicle_id
trip_id 2 scolaire 07:05 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 97 min 38 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 8 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 3 scolaire 7:32 stop_sequence 10 (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 2 (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 1 scolaire 07:41 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	53	28 times (100 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	28	28 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	106	28 times (100 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	2	2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-09-16 at 19:42 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 5 217 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-09-16 at 19:42 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "SM:1 scolaire 19:20",
      "trip_update": {
        "stop_time_update": [
          {
            "arrival": {
              "delay": 1,
              "time": "1726508540"
            },
            "departure": {
              "delay": 1,
              "time": "1726508540"
            },
            "stop_id": "12",
            "stop_sequence": 19
          }
        ],
        "timestamp": "1726508086",
        "trip": {
          "route_id": "1",
          "trip_id": "1 scolaire 19:20"
        }
      }
    }
  ],
  "header": {
    "gtfs_realtime_version": "1.0",
    "timestamp": "1726508575"
  }
}