gtfs-rt Transport open dataset - Position des véhicules en temps réel GTFS-RT for Réseau urbain Bibus

Resource details

File name: Position des véhicules en temps réel GTFS-RT

Format: gtfs-rt

Position GPS temps réel des véhicules

This resource file is part of the dataset Réseau urbain Bibus.

Download availability

Learn more

We test this resource download availability every hour by making an HTTP 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

❌2 errors, 234 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2024-12-20 at 08: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 1 error

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 268435679 trip_id 17135 does not exist in the GTFS data and does not have schedule_relationship of ADDED

Vehicle position far from trip shape E029 1 error

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.

Sample errors

vehicle.id 268435645 trip_id 16549797 at (48.40931,-4.4814425) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR

Warnings

timestamp not populated W001 117 errors

Timestamps should be populated for all elements

Sample errors

vehicle_id 268436170 does not have a timestamp
vehicle_id 268435966 does not have a timestamp
vehicle_id 268435761 does not have a timestamp
vehicle_id 268435808 does not have a timestamp
vehicle_id 268435583 does not have a timestamp

schedule_relationship not populated W009 117 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 16550050 does not have a schedule_relationship
trip_id 16549678 does not have a schedule_relationship
trip_id 16551304 does not have a schedule_relationship
trip_id 16551079 does not have a schedule_relationship
trip_id 16549226 does not have a schedule_relationship

Validate this GTFS-RT now

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
W001	Timestamps should be populated for all elements	2 592	29 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	2 592	29 times (100 % 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.	52	23 times (79 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	9	2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-12-22 at 04:22 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (0)

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2024-12-22 at 04:22 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfs_realtime_version": "2.0",
    "timestamp": "1734837749"
  }
}