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

2025-04-29
100%
2025-04-30
100%
2025-05-01
100%
2025-05-02
100%
2025-05-03
100%
2025-05-04
100%
2025-05-05
100%
2025-05-06
100%
2025-05-07
100%
2025-05-08
100%
2025-05-09
100%
2025-05-10
100%
2025-05-11
100%
2025-05-12
100%
2025-05-13
100%
2025-05-14
100%
2025-05-15
100%
2025-05-16
100%
2025-05-17
100%
2025-05-18
100%
2025-05-19
100%
2025-05-20
100%
2025-05-21
100%
2025-05-22
100%
2025-05-23
100%
2025-05-24
99.3%
2025-05-25
100%
2025-05-26
100%
2025-05-27
100%
2025-05-28
100%
2025-05-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. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.

Validation details

⚠️19 warnings

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

Warnings

vehicle_id not populated W002 6 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id A01-04 does not have a vehicle_id
  • trip_id D02-04 does not have a vehicle_id
  • trip_id E02-03 does not have a vehicle_id
  • trip_id A01-05 does not have a vehicle_id
  • trip_id B01-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 6 min 21 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 12 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id A01-04 stop_sequence 16 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id A01-04 does not have a schedule_relationship
  • trip_id D02-04 stop_sequence 8 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id D02-04 does not have a schedule_relationship
  • trip_id E02-03 stop_sequence 10 (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 163 29 times (100 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 326 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)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 11 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-05-28 at 19:47 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 32 292 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-05-28 at 19:47 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "SM:A02-20", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "delay": 1, "time": "1748454439" }, "departure": { "delay": 1, "time": "1748454440" }, "stopId": "925", "stopSequence": 13 }, { "arrival": { "delay": 1, "time": "1748454315" }, "departure": { "delay": 1, "time": "1748454500" }, "stopId": "924", "stopSequence": 14 } ], "timestamp": "1748454453", "trip": { "directionId": 1, "routeId": "A", "tripId": "A02-20" } } } ], "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1748454469" } }