Resource details

File name: GTFS-RT vehicle-positions Côte&Bus Beaune
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Côte&Bus.

Download availability

2026-10-14
100%
2026-10-15
100%
2026-10-16
100%
2026-10-17
100%
2026-10-18
93.9%
2026-10-19
100%
2026-10-20
100%
2026-10-21
100%
2026-10-22
100%
2026-10-23
100%
2026-10-24
100%
2026-10-25
94%
2026-10-26
100%
2026-10-27
100%
2026-10-28
100%
2026-10-29
100%
2026-10-30
100%
2026-10-31
100%
2026-11-01
94.1%
2026-11-02
100%
2026-11-03
100%
2026-11-04
100%
2026-11-05
100%
2026-11-06
100%
2026-11-07
100%
2026-11-08
93.8%
2026-11-09
100%
2026-11-10
100%
2026-11-11
93.8%
2026-11-12
100%
2026-11-13
100%
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, 9 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-11-13 at 08:05 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
  • entity ID 12 trip_id 6713_0 at (47.034004,4.846253) 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

vehicle_id not populated W002 9 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • entity ID 12 does not have a vehicle_id
  • entity ID 22 does not have a vehicle_id
  • entity ID 24 does not have a vehicle_id
  • entity ID 25 does not have a vehicle_id
  • entity ID 26 does not have a vehicle_id
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
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 58 20 times (67 % 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. 5 4 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-11-13 at 22:58 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-11-13 at 22:58 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "215", "vehicle": { "position": { "bearing": 0.0, "latitude": 46.90461349487305, "longitude": 4.761809825897217 }, "timestamp": "1794586024", "trip": { "routeId": "20.3", "scheduleRelationship": "SCHEDULED", "tripId": "6738_0" }, "vehicle": { "label": "163140" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1794607083" } }