Resource details

File name: Réseau Alternéo - RT - service position des véhicules
Format: gtfs-rt

GTFS RT service position des véhicules

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

Download availability

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

58 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2025-08-20 at 09:09 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 58 errors

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 155 trip_id 2_3989076 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 156 trip_id 2_31001055 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 159 trip_id 2_3988932 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 160 trip_id 2_31001032 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 161 trip_id 2_3989075 does not exist in the GTFS data and does not have schedule_relationship of ADDED
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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 235 32 times (100 % of validations)
E024 GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt 1 199 25 times (78 % 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. 75 25 times (78 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 4 3 times (9 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-08-20 at 20:52 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 2025-08-20 at 20:52 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "77", "vehicle": { "position": { "bearing": 315.0, "latitude": -21.136829376220703, "longitude": 55.47917175292969, "speed": 0.0 }, "stopId": "0:CI0011C", "timestamp": "1755702677", "trip": { "directionId": 0, "routeId": "6630", "scheduleRelationship": "SCHEDULED", "tripId": "2_3989203" }, "vehicle": { "id": "77", "label": "77" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1755715944" } }