gtfs-rt Transport open dataset - Tilt - Lannion-Trégor Communauté for Réseau urbain Tilt

Resource details

File name: Tilt - Lannion-Trégor Communauté

Format: gtfs-rt

Fichier GTFS-RT

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

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

⚠️25 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2024-12-11 at 08:00 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

vehicle_id not populated W002 8 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id A01-02 does not have a vehicle_id
trip_id B02-02 does not have a vehicle_id
trip_id C02-01 does not have a vehicle_id
trip_id B01-02 does not have a vehicle_id
trip_id LM01-02 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 11 min 54 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 16 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id A01-02 stop_sequence 8 (and potentially more for this trip) does not have a schedule_relationship
trip_id A01-02 does not have a schedule_relationship
trip_id B02-02 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id B02-02 does not have a schedule_relationship
trip_id C02-01 stop_sequence 15 (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	114	30 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	228	30 times (100 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	29	29 times (97 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-12-11 at 19:46 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 8 417 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-12-11 at 19:46 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "SM:A02-20",
      "trip_update": {
        "stop_time_update": [
          {
            "arrival": {
              "delay": 1,
              "time": "1733942780"
            },
            "departure": {
              "delay": 1,
              "time": "1733942780"
            },
            "stop_id": "924",
            "stop_sequence": 14
          }
        ],
        "timestamp": "1733942731",
        "trip": {
          "direction_id": 1,
          "route_id": "A",
          "trip_id": "A02-20"
        }
      }
    }
  ],
  "header": {
    "gtfs_realtime_version": "1.0",
    "timestamp": "1733942772"
  }
}