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
❌11 errors, 7 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-04-05 at 09:12 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 4 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 21328424 stop_id wimmair3 does not exist in GTFS data stops.txt
- trip_id 21328425 stop_id wimmair4 does not exist in GTFS data stops.txt
- trip_id 21328401 stop_id wimmair4 does not exist in GTFS data stops.txt
- trip_id 21328407 stop_id wimmair3 does not exist in GTFS data stops.txt
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 7 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 21328424 stop_sequence 1 has stop_id wimmair3 but GTFS stop_sequence 1 has stop_id wimmair - stop_ids should be the same
- GTFS-rt trip_id 21328425 stop_sequence 43 has stop_id wimmair4 but GTFS stop_sequence 43 has stop_id wimmair2 - stop_ids should be the same
- GTFS-rt trip_id 21328401 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 21328407 stop_sequence 11 has stop_id wimmair3 but GTFS stop_sequence 11 has stop_id wimmair - stop_ids should be the same
- GTFS-rt trip_id 21328407 stop_sequence 16 has stop_id wimcrec but GTFS stop_sequence 16 has stop_id wimcrec2 - stop_ids should be the same
Warnings
vehicle_id not populated W002 7 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 21328425 does not have a vehicle_id
- trip_id 21328401 does not have a vehicle_id
- trip_id 21328385 does not have a vehicle_id
- trip_id 21328382 does not have a vehicle_id
- trip_id 21328364 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 | 245 | 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 | 371 | 30 times (100 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1,021 | 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. | 844 | 25 times (83 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 37 | 22 times (73 % 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) |
| 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. | 2 | 2 times (7 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-04-05 at 21:35 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-05 at 21:35 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1775417759"
}
}