Resource details
This resource file is part of the dataset Réseau urbain Marinéo.
Download availability
Learn more
We test this resource download availability every hour by making an HTTPHEAD 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.
Validation details
❌24 errors, 23 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2024-05-19 at 09:01 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
GTFS-rt stop_id does not exist in GTFS data E011 8 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 19132341 stop_id bsmc14r does not exist in GTFS data stops.txt
- trip_id 19132341 stop_id bsmper1 does not exist in GTFS data stops.txt
- trip_id 19132341 stop_id bsmq01 does not exist in GTFS data stops.txt
- trip_id 19132336 stop_id bsmq01 does not exist in GTFS data stops.txt
- trip_id 19132336 stop_id bsmper2 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 14 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 19132341 stop_sequence 1 arrival_time 08:50:00 (1716101400) is less than previous stop arrival_time 09:06:41 (1716102401) - times must increase between two sequential stops
- trip_id 19132341 stop_sequence 1 arrival_time 08:50:00 (1716101400) is less than previous stop departure_time 09:06:41 (1716102401) - times must increase between two sequential stops
- trip_id 19132341 stop_sequence 1 departure_time 08:50:00 (1716101400) is less than previous stop departure_time 09:06:41 (1716102401) - times must increase between two sequential stops
- trip_id 19132341 stop_sequence 1 departure_time 08:50:00 (1716101400) is less than previous stop arrival_time 09:06:41 (1716102401) - times must increase between two sequential stops
- trip_id 19132336 stop_sequence 1 departure_time 09:50:00 (1716105000) is less than previous stop departure_time 10:23:34 (1716107014) - times must increase between two sequential stops
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 19132336 stop_sequence 34 departure_time 10:37:00 (1716107820) is less than the same stop arrival_time 10:37:34 (1716107854) - departure time must be equal to or greater than arrival time
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 error
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 19132379 stop_sequence 16 has stop_id wimcrec but GTFS stop_sequence 16 has stop_id wimcrec2 - stop_ids should be the same
Warnings
timestamp not populated W001 14 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 19132341 does not have a timestamp
- trip_id 19132336 does not have a timestamp
- trip_id 19132328 does not have a timestamp
- trip_id 19132320 does not have a timestamp
- trip_id 19132321 does not have a timestamp
vehicle_id not populated W002 9 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 19132336 does not have a vehicle_id
- trip_id 19132328 does not have a vehicle_id
- trip_id 19132373 does not have a vehicle_id
- trip_id 19132356 does not have a vehicle_id
- trip_id 19132357 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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 1 514 | 29 times (97 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 857 | 29 times (97 % of validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 924 | 26 times (87 % 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 | 42 | 25 times (83 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 67 | 24 times (80 % of validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 41 | 23 times (77 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 24 | 9 times (30 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 18 | 7 times (23 % 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 | 8 | 4 times (13 % 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. | 4 | 4 times (13 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2024-05-20 at 06:37 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (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 2024-05-20 at 06:37 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1716179854"
}
}