Resource details
This resource file is part of the dataset Réseau urbain TaM.
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
❌16 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-04 at 08:11 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 8 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- vehicle_id 907 trip_id 202601041583201130 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 809 trip_id 202601041583198807 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 731 trip_id 202601041583200876 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 642 trip_id 202601041583180630 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 762 trip_id 202601041583176226 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt stop_id does not exist in GTFS data E011 8 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 907 stop_id 0:32257 does not exist in GTFS data stops.txt
- vehicle_id 809 stop_id 0:21123 does not exist in GTFS data stops.txt
- vehicle_id 731 stop_id 0:18206 does not exist in GTFS data stops.txt
- vehicle_id 642 stop_id 0:25101 does not exist in GTFS data stops.txt
- vehicle_id 762 stop_id 0:39103 does not exist in GTFS data stops.txt
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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 45 | 3 times (100 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 46 | 3 times (100 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-01-07 at 02:34 Europe/Paris.
vehicle_positions (1) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2026-01-07 at 02:34 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "643",
"vehicle": {
"currentStatus": "STOPPED_AT",
"position": {
"bearing": 335.0,
"latitude": 43.6540641784668,
"longitude": 3.856316328048706,
"speed": 12.0
},
"stopId": "0:23104",
"timestamp": "1767711726",
"trip": {
"directionId": 0,
"routeId": "26",
"scheduleRelationship": "SCHEDULED",
"tripId": "202601061583156628"
},
"vehicle": {
"id": "643",
"label": "643"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1767749665"
}
}