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
❌70 errors, 39 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-17 at 08:09 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 1 error
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- trip_id 21323855 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 1 error
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- route_id SC does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 11 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 21725824 stop_id outmds does not exist in GTFS data stops.txt
- trip_id 21725826 stop_id outmds does not exist in GTFS data stops.txt
- trip_id 21323855 stop_id smbsand does not exist in GTFS data stops.txt
- trip_id 21725990 stop_id wimmair4 does not exist in GTFS data stops.txt
- trip_id 21725991 stop_id wimmair3 does not exist in GTFS data stops.txt
stop_times_updates not strictly sorted E002 2 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id 21725825 stop_sequence [7, 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] is not strictly sorted by increasing stop_sequence
- trip_id 21725823 stop_sequence [7, 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] is not strictly sorted by increasing stop_sequence
Sequential stop_time_update times are not increasing E022 40 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 21725824 stop_sequence 1 departure_time 08:01:01 (1773730861) is less than previous stop departure_time 08:17:26 (1773731846) - times must increase between two sequential stops
- trip_id 21725824 stop_sequence 1 departure_time 08:01:01 (1773730861) is less than previous stop arrival_time 08:17:26 (1773731846) - times must increase between two sequential stops
- trip_id 21725824 stop_sequence 2 arrival_time 08:02:20 (1773730940) is less than previous stop arrival_time 08:17:26 (1773731846) - times must increase between two sequential stops
- trip_id 21725824 stop_sequence 2 departure_time 08:02:31 (1773730951) is less than previous stop arrival_time 08:17:26 (1773731846) - times must increase between two sequential stops
- trip_id 21725824 stop_sequence 16 arrival_time 08:18:05 (1773731885) is less than previous stop arrival_time 08:18:11 (1773731891) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 15 errors
If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt
Sample errors
- GTFS-rt trip_id 21725937 stop_sequence 6 has stop_id smbecol but GTFS stop_sequence 6 has stop_id smbecol3 - stop_ids should be the same
- GTFS-rt trip_id 21725926 stop_sequence 13 has stop_id smbecol but GTFS stop_sequence 13 has stop_id smbecol3 - stop_ids should be the same
- GTFS-rt trip_id 21725929 stop_sequence 4 has stop_id smbecol but GTFS stop_sequence 4 has stop_id smbecol3 - stop_ids should be the same
- GTFS-rt trip_id 21725990 stop_sequence 25 has stop_id wimmair4 but GTFS stop_sequence 25 has stop_id wimmair2 - stop_ids should be the same
- GTFS-rt trip_id 21725991 stop_sequence 11 has stop_id wimmair3 but GTFS stop_sequence 11 has stop_id wimmair - stop_ids should be the same
Warnings
vehicle_id not populated W002 39 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 21323825 does not have a vehicle_id
- trip_id 21725825 does not have a vehicle_id
- trip_id 21725826 does not have a vehicle_id
- trip_id 21725936 does not have a vehicle_id
- trip_id 21725938 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 | 332 | 30 times (100 % 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 | 382 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1,061 | 30 times (100 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 83 | 26 times (87 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1,553 | 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 | 7 | 7 times (23 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 7 | 7 times (23 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-03-18 at 02:56 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 2026-03-18 at 02:56 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1773799001"
}
}