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
❌30 errors, 35 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-02 at 09:15 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 7 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 21725828 stop_id outmds does not exist in GTFS data stops.txt
- trip_id 21725996 stop_id wimmair4 does not exist in GTFS data stops.txt
- trip_id 21725992 stop_id wimmair4 does not exist in GTFS data stops.txt
- trip_id 21725994 stop_id wimmair3 does not exist in GTFS data stops.txt
- trip_id 21725974 stop_id wimmair3 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 10 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 21725828 stop_sequence 1 departure_time 09:45:00 (1775115900) is less than previous stop departure_time 10:01:09 (1775116869) - times must increase between two sequential stops
- trip_id 21725828 stop_sequence 1 departure_time 09:45:00 (1775115900) is less than previous stop arrival_time 10:01:09 (1775116869) - times must increase between two sequential stops
- trip_id 21725828 stop_sequence 2 arrival_time 09:46:35 (1775115995) is less than previous stop arrival_time 10:01:09 (1775116869) - times must increase between two sequential stops
- trip_id 21725828 stop_sequence 2 departure_time 09:46:35 (1775115995) is less than previous stop arrival_time 10:01:09 (1775116869) - times must increase between two sequential stops
- trip_id 21725828 stop_sequence 16 arrival_time 10:01:48 (1775116908) is less than previous stop arrival_time 10:03:11 (1775116991) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 13 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 21323584 stop_sequence 11 has stop_id smbheli but GTFS stop_sequence 11 has stop_id smbheli2 - stop_ids should be the same
- GTFS-rt trip_id 21725941 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 21725936 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 21725938 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 21725931 stop_sequence 13 has stop_id smbecol but GTFS stop_sequence 13 has stop_id smbecol3 - stop_ids should be the same
Warnings
vehicle_id not populated W002 35 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 21323593 does not have a vehicle_id
- trip_id 21323585 does not have a vehicle_id
- trip_id 21725857 does not have a vehicle_id
- trip_id 21725866 does not have a vehicle_id
- trip_id 21725828 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 | 256 | 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 | 377 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1,071 | 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. | 908 | 26 times (87 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 43 | 25 times (83 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 11 | 11 times (37 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 11 | 11 times (37 % 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) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-03 at 00:39 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-04-03 at 00:39 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1775169594"
}
}