gtfs-rt Transport open dataset - Horaires temps réel des lignes du réseau FORBUS for Réseau urbain Forbus

Resource details

File name: Horaires temps réel des lignes 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

❌49 errors, 118 warnings

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

Errors

stop_times_updates not strictly sorted E002 12 errors

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Sample errors

trip_id 58695789 stop_sequence [1, 2, 3, 4, 5, 7, 8, 8] is not strictly sorted by increasing stop_sequence
trip_id 58695790 stop_sequence [1, 2, 3, 4, 5, 7, 8, 8] is not strictly sorted by increasing stop_sequence
trip_id 58695791 stop_sequence [1, 2, 3, 4, 5, 7, 8, 8] is not strictly sorted by increasing stop_sequence
trip_id 58695792 stop_sequence [1, 2, 3, 4, 5, 7, 8, 9, 10, 10] is not strictly sorted by increasing stop_sequence
trip_id 01acb855-ce05-4a89-82a8-3d1c72aa956d stop_sequence [1, 2, 3, 4, 5, 6, 7, 7] is not strictly sorted by increasing stop_sequence

stop_time_update departure time is before arrival time E025 1 error

Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time.

Sample errors

trip_id cfffb67f-7486-4a3d-b19f-aee9fc2ccc03 stop_sequence 4 departure_time 17:05:46 (1743606346) is less than the same stop arrival_time 17:05:57 (1743606357) - departure time must be equal to or greater than arrival time

Sequential stop_time_updates have the same stop_sequence E036 12 errors

Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence

Sample errors

trip_id 58695789 has repeating stop_sequence 8 - stop_sequence must increase for each stop_time_update
trip_id 58695790 has repeating stop_sequence 8 - stop_sequence must increase for each stop_time_update
trip_id 58695791 has repeating stop_sequence 8 - stop_sequence must increase for each stop_time_update
trip_id 58695792 has repeating stop_sequence 10 - stop_sequence must increase for each stop_time_update
trip_id 01acb855-ce05-4a89-82a8-3d1c72aa956d has repeating stop_sequence 7 - stop_sequence must increase for each stop_time_update

Sequential stop_time_updates have the same stop_id E037 12 errors

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Sample errors

trip_id 58695789 has repeating stop_id 160908 at stop_sequence 8 - sequential stop_ids should be different
trip_id 58695790 has repeating stop_id 160908 at stop_sequence 8 - sequential stop_ids should be different
trip_id 58695791 has repeating stop_id 160908 at stop_sequence 8 - sequential stop_ids should be different
trip_id 58695792 has repeating stop_id 161016 at stop_sequence 10 - sequential stop_ids should be different
trip_id 01acb855-ce05-4a89-82a8-3d1c72aa956d has repeating stop_id 160836 at stop_sequence 7 - sequential stop_ids should be different

GTFS-rt stop_sequence not found in GTFS data E051 12 errors

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Sample errors

GTFS-rt trip_id 58695789 contains stop_sequence 8 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 58695790 contains stop_sequence 8 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 58695791 contains stop_sequence 8 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 58695792 contains stop_sequence 10 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 01acb855-ce05-4a89-82a8-3d1c72aa956d contains stop_sequence 7 that does not exist in GTFS stop_times.txt for this trip

Warnings

vehicle_id not populated W002 39 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 9fc6e5df-67a6-48b9-b108-ab6b71de7327 does not have a vehicle_id
trip_id 0bfcfb9d-851a-483b-997c-bdfad65c294e does not have a vehicle_id
trip_id 78c3a9cc-4319-4d3e-b8a0-8e8bb047cae2 does not have a vehicle_id
trip_id 58695789 does not have a vehicle_id
trip_id 58695790 does not have a vehicle_id

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 954 min 6 sec old which is greater than the recommended age of 65 seconds

schedule_relationship not populated W009 78 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 9fc6e5df-67a6-48b9-b108-ab6b71de7327 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 9fc6e5df-67a6-48b9-b108-ab6b71de7327 does not have a schedule_relationship
trip_id 0bfcfb9d-851a-483b-997c-bdfad65c294e stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 0bfcfb9d-851a-483b-997c-bdfad65c294e does not have a schedule_relationship
trip_id 78c3a9cc-4319-4d3e-b8a0-8e8bb047cae2 stop_sequence 1 (and potentially more for this trip) 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
E025	Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time.	54	26 times (87 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	588	26 times (87 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	3 175	26 times (87 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	121	25 times (83 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	3 965	25 times (83 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	7 454	25 times (83 % of validations)
E045	If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt	12 991	25 times (83 % of validations)
W001	Timestamps should be populated for all elements	3 580	25 times (83 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	42	21 times (70 % of validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	31	17 times (57 % of validations)
E043	If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided	14	14 times (47 % 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)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	12	1 times (3 % of validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	12	1 times (3 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	1	1 times (3 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	78	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-04 at 00:40 Europe/Paris.

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

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-04-04 at 00:40 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfs_realtime_version": "1.0",
    "timestamp": "1743720019"
  }
}