Resource details
This resource file is part of the dataset Réseau urbain Forbus.
Download availability
Learn more
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
❌72 errors, 429 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-20 at 09:12 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 14 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id b43b2498-70a7-4140-a11c-ae64c6e0f2c3 stop_sequence [8, 9, 10, 11, 12, 13, 13] is not strictly sorted by increasing stop_sequence
- trip_id cc2a5ad5-9315-41e6-b477-d1fc04eb0b9d stop_sequence [5, 6, 7, 9, 10, 13, 14, 14] is not strictly sorted by increasing stop_sequence
- trip_id 6eff4cc7-35ae-4a02-8061-81434c0dfe34 stop_sequence [1, 2, 3, 4, 5, 6, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 43] is not strictly sorted by increasing stop_sequence
- trip_id 198cd496-71bb-4c49-a6ad-7ed84e49deb3 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 11] is not strictly sorted by increasing stop_sequence
- trip_id 22f5f408-6bf2-4de6-a0a5-95c2e5b55854 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 11] 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 d1da5d74-fcc0-4bcc-81fc-7611ede5e7d7 stop_sequence 6 departure_time 09:11:03 (1758352263) is less than the same stop arrival_time 09:11:07 (1758352267) - departure time must be equal to or greater than arrival time
Sequential stop_time_updates have the same stop_sequence E036 14 errors
Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence
Sample errors
- trip_id b43b2498-70a7-4140-a11c-ae64c6e0f2c3 has repeating stop_sequence 13 - stop_sequence must increase for each stop_time_update
- trip_id cc2a5ad5-9315-41e6-b477-d1fc04eb0b9d has repeating stop_sequence 14 - stop_sequence must increase for each stop_time_update
- trip_id 6eff4cc7-35ae-4a02-8061-81434c0dfe34 has repeating stop_sequence 43 - stop_sequence must increase for each stop_time_update
- trip_id 198cd496-71bb-4c49-a6ad-7ed84e49deb3 has repeating stop_sequence 11 - stop_sequence must increase for each stop_time_update
- trip_id 22f5f408-6bf2-4de6-a0a5-95c2e5b55854 has repeating stop_sequence 11 - stop_sequence must increase for each stop_time_update
Sequential stop_time_updates have the same stop_id E037 29 errors
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Sample errors
- trip_id b43b2498-70a7-4140-a11c-ae64c6e0f2c3 has repeating stop_id stp-thefor01 at stop_sequence 13 - sequential stop_ids should be different
- trip_id 1c9da668-854b-4f28-b49b-53ac1542ee7e has repeating stop_id 161016 at stop_sequence 12 - sequential stop_ids should be different
- trip_id 26ed67e0-d78b-4527-bd09-8c5d84318d4e has repeating stop_id 161016 at stop_sequence 12 - sequential stop_ids should be different
- trip_id 42fb6533-419e-4fb5-a231-152667d73b51 has repeating stop_id 161016 at stop_sequence 12 - sequential stop_ids should be different
- trip_id 4d8ad55c-f6b7-4400-9fd8-3c06e9828ecd has repeating stop_id 161016 at stop_sequence 12 - sequential stop_ids should be different
GTFS-rt stop_sequence not found in GTFS data E051 14 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 b43b2498-70a7-4140-a11c-ae64c6e0f2c3 contains stop_sequence 13 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id cc2a5ad5-9315-41e6-b477-d1fc04eb0b9d contains stop_sequence 14 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 6eff4cc7-35ae-4a02-8061-81434c0dfe34 contains stop_sequence 43 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 198cd496-71bb-4c49-a6ad-7ed84e49deb3 contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 22f5f408-6bf2-4de6-a0a5-95c2e5b55854 contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
Warnings
vehicle_id not populated W002 143 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id b43b2498-70a7-4140-a11c-ae64c6e0f2c3 does not have a vehicle_id
- trip_id d81e2ee9-8481-415f-a4dd-430cb745ae0b does not have a vehicle_id
- trip_id de699483-43a6-4e0b-849c-c21da008f2c9 does not have a vehicle_id
- trip_id e36ad08e-03f6-4b1c-92c6-2d15278e3210 does not have a vehicle_id
- trip_id e47399c3-0bb3-4e47-8a4c-d0a72f65424a does not have a vehicle_id
schedule_relationship not populated W009 286 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id b43b2498-70a7-4140-a11c-ae64c6e0f2c3 stop_sequence 8 (and potentially more for this trip) does not have a schedule_relationship
- trip_id b43b2498-70a7-4140-a11c-ae64c6e0f2c3 does not have a schedule_relationship
- trip_id d81e2ee9-8481-415f-a4dd-430cb745ae0b stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
- trip_id d81e2ee9-8481-415f-a4dd-430cb745ae0b does not have a schedule_relationship
- trip_id de699483-43a6-4e0b-849c-c21da008f2c9 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
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 |
|---|---|---|---|
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 2 131 | 16 times (62 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 4 262 | 16 times (62 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 303 | 15 times (58 % of validations) |
| E036 | Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence | 303 | 15 times (58 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 374 | 15 times (58 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 303 | 15 times (58 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 13 | 13 times (50 % of validations) |
| 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. | 6 | 4 times (15 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1 | 1 times (4 % 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 | 49 | 1 times (4 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-09-21 at 05:47 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
trip_updatesDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-09-21 at 05:47 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1758426441"
}
}