Resource details
Les données horaires correspondent à l’ensemble de l’offre du réseau TLP Mobilités : les horaires de l’ensemble des lignes commerciales et les informations géographiques associées (topographie du réseau).
This resource file is part of the dataset Réseau urbain TLP.
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
❌578 errors, 6 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-04 at 09:14 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 59 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 zenbus:Vehicle:903620003:LOC trip_id 4884945051844608:0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4884945051844608:0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:887170002:LOC trip_id 4896235301371904:2 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4896235301371904:2 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:889210002:LOC trip_id 6253152573587456:2 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 59 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id zenbus:Vehicle:903620003:LOC route_id zenbus:Line:885150004:LOC does not exist in the GTFS data routes.txt
- route_id zenbus:Line:885150004:LOC does not exist in the GTFS data routes.txt
- vehicle_id zenbus:Vehicle:887170002:LOC route_id zenbus:Line:860950003:LOC does not exist in the GTFS data routes.txt
- route_id zenbus:Line:860950003:LOC does not exist in the GTFS data routes.txt
- vehicle_id zenbus:Vehicle:889210002:LOC route_id zenbus:Line:855090008:LOC does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 460 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id zenbus:Vehicle:903620003:LOC stop_id zenbus:StopPoint:SP:715300018:LOC does not exist in GTFS data stops.txt
- trip_id 4884945051844608:0 stop_id zenbus:StopPoint:SP:715300018:LOC does not exist in GTFS data stops.txt
- trip_id 4884945051844608:0 stop_id zenbus:StopPoint:SP:855080012:LOC does not exist in GTFS data stops.txt
- vehicle_id zenbus:Vehicle:887170002:LOC stop_id zenbus:StopPoint:SP:713360020:LOC does not exist in GTFS data stops.txt
- trip_id 4896235301371904:2 stop_id zenbus:StopPoint:SP:892890008:LOC does not exist in GTFS data stops.txt
Warnings
vehicle_id not populated W002 3 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 898170002:6 does not have a vehicle_id
- trip_id 4832578965078016:5 does not have a vehicle_id
- trip_id 4893880496422912:3 does not have a vehicle_id
ID in one feed missing from the other W003 3 errors
a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed
Sample errors
- trip_id 4832578965078016:5 is in TripUpdates but not in VehiclePositions feed
- trip_id 898170002:6 is in TripUpdates but not in VehiclePositions feed
- trip_id 4893880496422912:3 is in TripUpdates but not in VehiclePositions feed
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 | 1 396 | 26 times (87 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 396 | 26 times (87 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 10 830 | 26 times (87 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 32 | 19 times (63 % of validations) |
| W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 32 | 19 times (63 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 8 | 6 times (20 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-04-04 at 23:40 Europe/Paris.
vehicle_positions (1) trip_updates (1) service_alerts (0)Entities seen in the last 7 days.
trip_updates vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-04-04 at 23:40 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "zenbus:Vehicle:885480002:LOC",
"vehicle": {
"current_stop_sequence": 21,
"position": {
"latitude": 43.24134063720703,
"longitude": 0.01432000007480383
},
"stop_id": "zenbus:StopPoint:SP:896940011:LOC",
"timestamp": "1743802741",
"trip": {
"route_id": "zenbus:Line:838040009:LOC",
"schedule_relationship": "SCHEDULED",
"start_date": "20250404",
"start_time": "18:10:00",
"trip_id": "5173139178782720:2"
},
"vehicle": {
"id": "zenbus:Vehicle:885480002:LOC"
}
}
},
{
"id": "20250404:5093263574827008:2",
"trip_update": {
"stop_time_update": [
{
"schedule_relationship": "SKIPPED",
"stop_id": "zenbus:StopPoint:SP:723130016:LOC",
"stop_sequence": 12
},
{
"schedule_relationship": "SKIPPED",
"stop_id": "zenbus:StopPoint:SP:896950010:LOC",
"stop_sequence": 13
},
{
"schedule_relationship": "SKIPPED",
"stop_id": "zenbus:StopPoint:SP:723110016:LOC",
"stop_sequence": 14
},
{
"schedule_relationship": "SKIPPED",
"stop_id": "zenbus:StopPoint:SP:680300016:LOC",
"stop_sequence": 15
},
{
"schedule_relationship": "SKIPPED",
"stop_id": "zenbus:StopPoint:SP:692560016:LOC",
"stop_sequence": 16
},
{
"schedule_relationship": "SKIPPED",
"stop_id": "zenbus:StopPoint:SP:902940008:LOC",
"stop_sequence": 17
},
{
"schedule_relationship": "SKIPPED",
"stop_id": "zenbus:StopPoint:SP:912830013:LOC",
"stop_sequence": 18
},
{
"schedule_relationship": "SKIPPED",
"stop_id": "zenbus:StopPoint:SP:864910011:LOC",
"stop_sequence": 19
},
{
"schedule_relationship": "SKIPPED",
"stop_id": "zenbus:StopPoint:SP:904940009:LOC",
"stop_sequence": 20
},
{
"arrival": {
"time": "1743803420"
},
"departure": {
"time": "1743803430"
},
"stop_id": "zenbus:StopPoint:SP:896940011:LOC",
"stop_sequence": 21
}
],
"timestamp": "1743802743",
"trip": {
"route_id": "zenbus:Line:838040009:LOC",
"schedule_relationship": "SCHEDULED",
"start_date": "20250404",
"start_time": "18:10:00",
"trip_id": "5173139178782720:2"
},
"vehicle": {
"id": "zenbus:Vehicle:885480002:LOC"
}
}
}
],
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1743802810"
}
}