gtfs-rt Transport open dataset - Position des véhicules du réseau FORBUS for Réseau urbain Forbus

Resource details

File name: Position des véhicules du réseau FORBUS

Format: gtfs-rt

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

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

❌2 errors, 20 warnings

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

Errors

Vehicle position outside agency coverage area E028 2 errors

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 57 at (0.0,0.0) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
vehicle.id 54 at (0.0,0.0) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area

Warnings

timestamp not populated W001 2 errors

Timestamps should be populated for all elements

Sample errors

vehicle_id 57 does not have a timestamp
vehicle_id 54 does not have a timestamp

Header timestamp is older than 65 seconds W008 1 error

The data in a GTFS-realtime feed should always be less than one minute old

Sample errors

header.timestamp is 2 min 9 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 17 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 8cc89595-5360-49fd-ab8a-af60a414efdc does not have a schedule_relationship
trip_id 77c6868c-3c30-45a9-95e4-5d3e6a15a46d does not have a schedule_relationship
trip_id 201c8bc4-f6ee-497a-95fd-7a77b431e50c does not have a schedule_relationship
trip_id 02116063-57c4-4615-9b06-b9bc688e15cb does not have a schedule_relationship
trip_id b43b2498-70a7-4140-a11c-ae64c6e0f2c3 does not have a schedule_relationship

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
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	256	18 times (86 % 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.	26	16 times (76 % of validations)
W001	Timestamps should be populated for all elements	26	16 times (76 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	13	13 times (62 % 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.	12	10 times (48 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-01-23 at 20:19 Europe/Paris.

vehicle_positions (1) service_alerts (0) trip_updates (0)

The timestamp field appears to be too old compared to the current time: the delay is 305 seconds. Try to update your feed at most every 30 seconds.

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-01-23 at 20:19 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "entity": [
    {
      "id": "VM:8a425480-7760-466e-a05d-ae3627c9839e",
      "vehicle": {
        "currentStopSequence": 24,
        "position": {
          "bearing": 58.0,
          "latitude": 49.16094970703125,
          "longitude": 6.9351887702941895
        },
        "stopId": "STP-LONGUE",
        "timestamp": "1769195555",
        "trip": {
          "routeId": "124",
          "tripId": "8a425480-7760-466e-a05d-ae3627c9839e"
        },
        "vehicle": {
          "id": "189"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "1.0",
    "timestamp": "1769195992"
  }
}