transport.data.gouv.fr transport.data.gouv.fr

Resource details

File name: Position des véhicules du réseau FORBUS
Format: gtfs-rt
Download

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

Download availability

2026-01-11
64.7%
2026-01-12
82.4%
2026-01-13
81.6%
2026-01-14
79.3%
2026-01-15
81.5%
2026-01-16
80.5%
2026-01-17
82.9%
2026-01-18
56.8%
2026-01-19
82.1%
2026-01-20
81.3%
2026-01-21
68.7%
2026-01-22
69.3%
2026-01-23
82.2%
2026-01-24
80.9%
2026-01-25
51.7%
2026-01-26
81.2%
2026-01-27
73.2%
2026-01-28
82.1%
2026-01-29
91.6%
2026-01-30
77%
2026-01-31
81.2%
2026-02-01
58.9%
2026-02-02
82.3%
2026-02-03
100%
2026-02-04
100%
2026-02-05
87%
2026-02-06
82.9%
2026-02-07
69.8%
2026-02-08
49.7%
2026-02-09
85.1%
2026-02-10
0%
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, 10 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-09 at 08:12 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 190 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 8 at (49.22094,6.937051) 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 1 error

Timestamps should be populated for all elements

Sample errors
  • vehicle_id 190 does not have a timestamp

schedule_relationship not populated W009 9 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors
  • trip_id b43b2498-70a7-4140-a11c-ae64c6e0f2c3 does not have a schedule_relationship
  • trip_id bc706336-e4e1-4606-8404-9d7d2a16812c does not have a schedule_relationship
  • trip_id a3771287-b9c4-4265-85e0-5d753a3bedbb does not have a schedule_relationship
  • trip_id 2c61ca2f-3976-4643-a5de-35c86a314462 does not have a schedule_relationship
  • trip_id 8cc89595-5360-49fd-ab8a-af60a414efdc 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 341 23 times (82 % 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. 41 20 times (71 % of validations)
W001 Timestamps should be populated for all elements 39 19 times (68 % of validations)
W008 The data in a GTFS-realtime feed should always be less than one minute old 17 17 times (61 % 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. 8 6 times (21 % of validations)

GTFS-RT feed content

Could not decode the GTFS-RT feed.

The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.