Resource details
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
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
❌8 errors, 4 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-12-20 at 08:03 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 4 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 trip_id 1-727187457 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id trip_id 1-705888257 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id trip_id 1-25165826 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id trip_id 1-258605065 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Vehicle position outside agency coverage area E028 4 errors
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.
Sample errors
- entity ID 1933337 at (48.509373,-2.489036) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- entity ID 1933528 at (48.5875,-2.53912) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- entity ID 1933836 at (48.466976,-2.520609) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- entity ID 1933844 at (48.47105,-2.516273) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
Warnings
vehicle_id not populated W002 4 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- entity ID 1933337 does not have a vehicle_id
- entity ID 1933528 does not have a vehicle_id
- entity ID 1933836 does not have a vehicle_id
- entity ID 1933844 does not have a vehicle_id
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 | 29 | 9 times (82 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 5 | 2 times (18 % 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. | 4 | 1 times (9 % 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. | 1 | 1 times (9 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-12-22 at 06:40 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (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 2024-12-22 at 06:40 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1734846002"
}
}