Resource details
This resource file is part of the dataset Réseau urbain TAC.
Download availability
Learn more
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 warning
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-13 at 09:11 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
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 650 min 28 sec old which is greater than the recommended age of 65 seconds
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 | 2 238 | 24 times (77 % of validations) |
W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 4 476 | 24 times (77 % of validations) |
W008 | The data in a GTFS-realtime feed should always be less than one minute old | 17 | 17 times (55 % of validations) |
E025 | Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. | 52 | 4 times (13 % of validations) |
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 39 | 3 times (10 % of validations) |
E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 1 | 1 times (3 % of validations) |
E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 1 | 1 times (3 % of validations) |
E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 1 | 1 times (3 % of validations) |
E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-06-12 at 22:20 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-06-12 at 22:20 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1749759658"
}
}