Resource details
This resource file is part of the dataset Réseau urbain Marinéo.
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
❌238 errors, 43 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-11-19 at 08:09 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 11 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id 21725990 stop_sequence [22, 1, 2, 3, 4, 5, 6, 7, 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] is not strictly sorted by increasing stop_sequence
- trip_id 21725992 stop_sequence [22, 1, 2, 3, 4, 5, 6, 7, 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] is not strictly sorted by increasing stop_sequence
- trip_id 21323514 stop_sequence [22, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31] is not strictly sorted by increasing stop_sequence
- trip_id 21323512 stop_sequence [22, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31] is not strictly sorted by increasing stop_sequence
- trip_id 21323513 stop_sequence [22, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31] is not strictly sorted by increasing stop_sequence
GTFS-rt stop_sequence isn't provided for trip that visits same stop_id more than once E009 1 error
If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence
Sample errors
- trip_id 21323895 visits stop_id [bsmdal1] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
GTFS-rt stop_id does not exist in GTFS data E011 22 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 21725990 stop_id wimeco does not exist in GTFS data stops.txt
- trip_id 21725992 stop_id wimeco does not exist in GTFS data stops.txt
- trip_id 21323514 stop_id bsmtran2 does not exist in GTFS data stops.txt
- trip_id 21323512 stop_id bsmtran2 does not exist in GTFS data stops.txt
- trip_id 21323513 stop_id bsmtran2 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 202 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id 21725990 stop_sequence 1 departure_time 07:47:21 (1763534841) is less than previous stop departure_time 08:31:27 (1763537487) - times must increase between two sequential stops
- trip_id 21725990 stop_sequence 1 departure_time 07:47:21 (1763534841) is less than previous stop arrival_time 08:31:27 (1763537487) - times must increase between two sequential stops
- trip_id 21725990 stop_sequence 2 arrival_time 07:47:38 (1763534858) is less than previous stop arrival_time 08:31:27 (1763537487) - times must increase between two sequential stops
- trip_id 21725990 stop_sequence 2 departure_time 07:47:50 (1763534870) is less than previous stop arrival_time 08:31:27 (1763537487) - times must increase between two sequential stops
- trip_id 21725990 stop_sequence 23 arrival_time 08:19:38 (1763536778) is less than previous stop arrival_time 08:22:36 (1763536956) - times must increase between two sequential stops
GTFS-rt stop_sequence not found in GTFS data E051 2 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 21323895 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 21323739 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
Warnings
vehicle_id not populated W002 43 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 21323549 does not have a vehicle_id
- trip_id 21725992 does not have a vehicle_id
- trip_id 21725993 does not have a vehicle_id
- trip_id 21725994 does not have a vehicle_id
- trip_id 21323418 does not have a vehicle_id
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 |
|---|---|---|---|
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 524 | 30 times (100 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 4 707 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 981 | 30 times (100 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 246 | 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 | 26 | 21 times (70 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 9 | 9 times (30 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 9 | 9 times (30 % of validations) |
| E009 | If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence | 9 | 8 times (27 % 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. | 1 | 1 times (3 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-11-20 at 01:31 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-11-20 at 01:31 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1763598710"
}
}