Resource details

File name: https://proxy.transport.data.gouv.fr/resource/star-rennes-integration-gtfs-rt-vehicle-position
Format: gtfs-rt

Mise à jour des informations de position des bus du STAR en temps réel

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

Download availability

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

10 errors, 1 warning

Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-11 at 09:09 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt stop_id does not exist in GTFS data E011 3 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors
  • vehicle_id 1003 stop_id 5-9827 does not exist in GTFS data stops.txt
  • vehicle_id 1014 stop_id 5-9824 does not exist in GTFS data stops.txt
  • vehicle_id 5015 stop_id 5-9861 does not exist in GTFS data stops.txt

Vehicle position far from trip shape E029 7 errors

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 606 trip_id 2_VENDREDI-15528241 at (48.159008,-1.640559) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
  • vehicle.id 953 trip_id 2_VENDREDI-16214009 at (48.122368,-1.649173) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
  • vehicle.id 1003 trip_id 2_VENDREDI-15474283 at (48.184498,-1.658397) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
  • vehicle.id 1014 trip_id 2_VENDREDI-15474282 at (48.154503,-1.702778) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
  • vehicle.id 2070 trip_id 2_VENDREDI-16003430 at (48.15352,-1.66256) 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 speed is unrealistic W004 1 error

vehicle.position.speed has an unrealistic speed that may be incorrect

Sample errors
  • vehicle.id 1053 speed of 28.3333 m/s (63.38 mph) is unrealistic
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
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 7 3 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. 26 3 times (100 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 1 1 times (33 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-12 at 05:28 Europe/Paris.

vehicle_positions (4) 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 2025-04-12 at 05:28 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "343", "vehicle": { "position": { "bearing": 225.0, "latitude": 48.12351989746094, "longitude": -1.6016299724578857, "speed": 5.555600166320801 }, "stop_id": "5-2008", "timestamp": "1744428502", "trip": { "direction_id": 0, "route_id": "5-0006", "schedule_relationship": "SCHEDULED", "trip_id": "2_SAMEDI-15468379" }, "vehicle": { "id": "343", "label": "343" } } }, { "id": "1064", "vehicle": { "position": { "bearing": 21.0, "latitude": 48.11330032348633, "longitude": -1.641160011291504, "speed": 2.5 }, "stop_id": "5-1604", "timestamp": "1744428502", "trip": { "direction_id": 1, "route_id": "5-0124", "schedule_relationship": "SCHEDULED", "trip_id": "2_SAMEDI-250412_20" }, "vehicle": { "id": "1064", "label": "1064" } } }, { "id": "1068", "vehicle": { "position": { "bearing": 353.0, "latitude": 48.0964469909668, "longitude": -1.6976640224456787, "speed": 7.2221999168396 }, "stop_id": "5-2286", "timestamp": "1744428502", "trip": { "direction_id": 1, "route_id": "5-0123", "schedule_relationship": "SCHEDULED", "trip_id": "2_SAMEDI-250412_31" }, "vehicle": { "id": "1068", "label": "1068" } } }, { "id": "1070", "vehicle": { "current_status": "STOPPED_AT", "position": { "bearing": 264.0, "latitude": 48.10951614379883, "longitude": -1.678905963897705, "speed": 0.0 }, "stop_id": "5-1732", "timestamp": "1744428502", "trip": { "direction_id": 0, "route_id": "5-0123", "schedule_relationship": "SCHEDULED", "trip_id": "2_SAMEDI-250412_39" }, "vehicle": { "id": "1070", "label": "1070" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1744428512" } }