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

❌16 errors, 2 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-03-12 at 08:00 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 7 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors

vehicle_id 41 trip_id fa3b8792-bc16-4aa2-9341-515a6563633e does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 37 trip_id 9591047c-0f61-491b-b5c0-14f78e74ee9f does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 48 trip_id f9db1194-258a-42e8-94da-86e787440ad6 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 29 trip_id 9172c81a-4f01-49b3-9e90-d7fc90735288 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 50 trip_id 1b28310a-b636-454d-8521-8149cf6d6eff does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 4 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors

vehicle_id 41 route_id 309 does not exist in the GTFS data routes.txt
vehicle_id 37 route_id 129 does not exist in the GTFS data routes.txt
vehicle_id 50 route_id 99 does not exist in the GTFS data routes.txt
vehicle_id 36 route_id 129 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 4 errors

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

Sample errors

vehicle_id 41 stop_id STP-HURLEVENT does not exist in GTFS data stops.txt
vehicle_id 37 stop_id STP-SARREGARE does not exist in GTFS data stops.txt
vehicle_id 29 stop_id STP-THEEBR01 does not exist in GTFS data stops.txt
vehicle_id 6 stop_id STP-STP-SAINT-THEODORE-2 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 37 at (49.106724,7.069813) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.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 11 does not have a timestamp
vehicle_id 7 does not have a timestamp

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
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	92	26 times (87 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	72	26 times (87 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	49	25 times (83 % of validations)
W001	Timestamps should be populated for all elements	39	22 times (73 % 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.	7	7 times (23 % of validations)
E023	For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip	6	6 times (20 % of validations)
E052	Each vehicle should have a unique ID	6	4 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-03-13 at 03:58 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (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 2025-03-13 at 03:58 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfs_realtime_version": "2.0",
    "timestamp": "1741834722"
  }
}