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
2025-06-01
96%
2025-06-02
86.1%
2025-06-03
100%
2025-06-04
100%
2025-06-05
100%
2025-06-06
100%
2025-06-07
100%
2025-06-08
76.1%
2025-06-09
79.7%
2025-06-10
86.1%
2025-06-11
100%
2025-06-12
100%
2025-06-13
86.7%
2025-06-14
74.2%
2025-06-15
75.6%
2025-06-16
100%
2025-06-17
100%
2025-06-18
88%
2025-06-19
86.1%
2025-06-20
95%
2025-06-21
100%
2025-06-22
100%
2025-06-23
100%
2025-06-24
96.2%
2025-06-25
85.4%
2025-06-26
98%
2025-06-27
100%
2025-06-28
87.8%
2025-06-29
77.7%
2025-06-30
96.1%
2025-07-01
0%
Learn more
We test this resource download availability every hour by making an HTTP
For SIRI and SIRI Lite feeds, we perform a
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
⚠️1 warning
Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-30 at 09:04 Europe/Paris using the MobilityData GTFS-RT validator.
Warnings
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 788 min 5 sec old which is greater than the recommended age of 65 seconds
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 |
---|---|---|---|
W008 | The data in a GTFS-realtime feed should always be less than one minute old | 25 | 25 times (86 % of validations) |
W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 217 | 18 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. | 19 | 13 times (45 % 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. | 17 | 6 times (21 % of validations) |
W001 | Timestamps should be populated for all elements | 15 | 6 times (21 % of validations) |
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 2 | 2 times (7 % 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.