Resource details

File name: Position du véhicule suburbain
Format: gtfs-rt

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

Download availability

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

2 errors

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

Errors

Vehicle position far from trip shape E029 2 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 731 trip_id 202604231583160658 at (43.549847,3.7142386) 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 644 trip_id 202604231583159921 at (43.646957,3.8328774) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
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
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. 77 22 times (73 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 82 4 times (13 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 82 4 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-04-24 at 02:00 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-04-24 at 02:00 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "793", "vehicle": { "position": { "bearing": 246.0, "latitude": 43.67935562133789, "longitude": 3.9864983558654785, "speed": 7.0 }, "stopId": "0:35202", "timestamp": "1776946352", "trip": { "directionId": 1, "routeId": "46", "scheduleRelationship": "SCHEDULED", "tripId": "202604231583198955" }, "vehicle": { "id": "793", "label": "793" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1776988819" } }