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

❌1 error, 282 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-09-22 at 09:07 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

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 268435863 trip_id 18110062 at (48.38227,-4.491758) 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 141 errors

Timestamps should be populated for all elements

Sample errors

vehicle_id 268435862 does not have a timestamp
vehicle_id 268435625 does not have a timestamp
vehicle_id 268436459 does not have a timestamp
vehicle_id 268435715 does not have a timestamp
vehicle_id 268435645 does not have a timestamp

schedule_relationship not populated W009 141 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 18115541 does not have a schedule_relationship
trip_id 18150889 does not have a schedule_relationship
trip_id 18297675 does not have a schedule_relationship
trip_id 18153029 does not have a schedule_relationship
trip_id 18197482 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,940	30 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	2,940	30 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.	47	22 times (73 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	271	14 times (47 % 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.	3	3 times (10 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-09-23 at 04:42 Europe/Paris.

vehicle_positions (1) service_alerts (0) trip_updates (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 2026-09-23 at 04:42 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "entity": [
    {
      "id": "vehicle:268436464",
      "vehicle": {
        "position": {
          "bearing": 74.0,
          "latitude": 48.37663269042969,
          "longitude": -4.5518999099731445
        },
        "timestamp": "0",
        "trip": {
          "routeId": "A",
          "tripId": "18297453"
        },
        "vehicle": {
          "id": "268436464"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1790131343"
  }
}