Resource details
Gtfs-RT flux vehiclepositions : Positions de véhicules (informations sur les véhicules, notamment leur emplacement) au format GTFS-RT
This resource file is part of the dataset Réseau urbain et scolaire TBM.
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
❌3 errors, 567 warnings
Shapes present in the GTFS have been ignored, some rules are not enforced.
Validation carried out using the current GTFS file and the GTFS-RT the 2024-12-20 at 08:09 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
trip start_time does not match first GTFS arrival_time E023 3 errors
For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip
Sample errors
- GTFS-rt vehicle_id ineo-bus:80002 trip_id 268440697_20 start_time is 08:00:00 and GTFS initial arrival_time is 05:25:00 - times do not match
- GTFS-rt vehicle_id ineo-bus:80003 trip_id 268440677_20 start_time is 07:45:00 and GTFS initial arrival_time is 05:15:00 - times do not match
- GTFS-rt vehicle_id ineo-bus:80007 trip_id 268440254_20 start_time is 07:45:00 and GTFS initial arrival_time is 06:40:00 - times do not match
Warnings
schedule_relationship not populated W009 567 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 268441326_20 does not have a schedule_relationship
- trip_id 268440616_20 does not have a schedule_relationship
- trip_id 268437942_20 does not have a schedule_relationship
- trip_id 268441345_20 does not have a schedule_relationship
- trip_id 268440879_20 does not have a schedule_relationship
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 |
|---|---|---|---|
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 12 036 | 28 times (100 % of validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 90 | 16 times (57 % 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. | 7 | 7 times (25 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 91 | 2 times (7 % of validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 1 | 1 times (4 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-12-22 at 04:12 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 04:12 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "1.0",
"timestamp": "1734837162"
}
}