Resource details
File name:
Données en temps réel au format GTFS-RT (VehiclePosition)
Format: gtfs-rt
Le message VehiclePosition au format GTFS-RT est disponibles dans ce flux.
This resource file is part of the dataset Réseau urbain Distribus.
Download availability
2025-03-20
100%
2025-03-21
100%
2025-03-22
100%
2025-03-23
13%
2025-03-24
89.5%
2025-03-25
100%
2025-03-26
100%
2025-03-27
100%
2025-03-28
100%
2025-03-29
100%
2025-03-30
8.8%
2025-03-31
72.3%
2025-04-01
100%
2025-04-02
100%
2025-04-03
100%
2025-04-04
100%
2025-04-05
100%
2025-04-06
8.8%
2025-04-07
93.7%
2025-04-08
100%
2025-04-09
100%
2025-04-10
100%
2025-04-11
100%
2025-04-12
100%
2025-04-13
8.4%
2025-04-14
93.7%
2025-04-15
100%
2025-04-16
100%
2025-04-17
100%
2025-04-18
100%
2025-04-19
100%
Learn more
We test this resource download availability every hour by making an HTTP
For SIRI and SIRI Lite feeds, we perform a
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
✅No error detected
Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-19 at 09:00 Europe/Paris using the MobilityData GTFS-RT validator.
Validate this GTFS-RT nowPrevious 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 | 91 | 24 times (89 % of validations) |
E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 20 | 14 times (52 % of validations) |
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 1 | 1 times (4 % of validations) |
E028 | The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. | 1 | 1 times (4 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-04-19 at 19:04 Europe/Paris.
vehicle_positions (3) 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 2025-04-19 at 19:04 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "48",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 48.46881866455078,
"longitude": -2.5149919986724854
},
"timestamp": "1745082295",
"trip": {
"route_id": "1",
"schedule_relationship": "SCHEDULED",
"trip_id": "25-24838162"
},
"vehicle": {
"label": "75569"
}
}
},
{
"id": "49",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 48.47296142578125,
"longitude": -2.514141082763672
},
"timestamp": "1745082294",
"trip": {
"route_id": "15",
"schedule_relationship": "SCHEDULED",
"trip_id": "25-257622018"
},
"vehicle": {
"label": "73173"
}
}
},
{
"id": "50",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 48.46644592285156,
"longitude": -2.509716033935547
},
"timestamp": "1745082295",
"trip": {
"route_id": "43",
"schedule_relationship": "SCHEDULED",
"trip_id": "25-727121943"
},
"vehicle": {
"label": "37253"
}
}
}
],
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1745082296"
}
}