gtfs-rt Transport open dataset - GTFS-RT - VehiclePosition for Réseau urbain SETRAM

Resource details

File name: GTFS-RT - VehiclePosition

Format: gtfs-rt

Gtfs-RT flux vehicleposition: Mises à jour de la position des véhicules au format GTFS-RT

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

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

❌5 errors, 13 warnings

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

Errors

GTFS-rt stop_id does not exist in GTFS data E011 1 error

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

Sample errors

vehicle_id 232 stop_id 35 does not exist in GTFS data stops.txt

Vehicle position outside agency coverage area E028 1 error

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.

Sample errors

vehicle.id 439 at (-1.0,-1.0) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area

Vehicle position far from trip shape E029 3 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 207 trip_id 5062494-B-ETE-2026-HB-SE-ET-Semaine-26 at (47.97768,0.208397) 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 422 trip_id 5063907-B-ETE-2026-HB-SE-ET-Semaine-26 at (47.97808,0.212077) 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 1005 trip_id 5057316-T-ETE-2026-TETE26-Semaine-26 at (47.955997,0.222477) 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 13 errors

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

Sample errors

vehicle.id 144 speed of 31.0 m/s (69.35 mph) is unrealistic
vehicle.id 145 speed of 45.0 m/s (100.66 mph) is unrealistic
vehicle.id 148 speed of 28.0 m/s (62.63 mph) is unrealistic
vehicle.id 202 speed of 36.0 m/s (80.53 mph) is unrealistic
vehicle.id 221 speed of 33.0 m/s (73.82 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
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.	61	27 times (100 % of validations)
W004	vehicle.position.speed has an unrealistic speed that may be incorrect	417	27 times (100 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	27	16 times (59 % 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.	4	4 times (15 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	22	1 times (4 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-07-28 at 01:36 Europe/Paris.

vehicle_positions (2) 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-07-28 at 01:36 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "entity": [
    {
      "id": "1014",
      "vehicle": {
        "position": {
          "bearing": 50.0,
          "latitude": 47.959598541259766,
          "longitude": 0.22871699929237366,
          "speed": 0.0
        },
        "stopId": "27",
        "timestamp": "1785195412",
        "vehicle": {
          "id": "1014",
          "label": "1014"
        }
      }
    },
    {
      "id": "1020",
      "vehicle": {
        "position": {
          "bearing": 329.0,
          "latitude": 47.96000289916992,
          "longitude": 0.2301570028066635,
          "speed": 17.0
        },
        "stopId": "27",
        "timestamp": "1785195409",
        "vehicle": {
          "id": "1020",
          "label": "1020"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1785195415"
  }
}