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
❌61 errors, 120 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-01-14 at 08:01 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
stop_times_updates not strictly sorted E002 4 errors
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Sample errors
- trip_id 20473140 stop_sequence [4, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11] is not strictly sorted by increasing stop_sequence
- trip_id 20472718 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 20472720 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 20473212 stop_sequence [2, 1] is not strictly sorted by increasing stop_sequence
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 20473026 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 1 error
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- trip_id 20473026 stop_id smbsand does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 50 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 20473140 stop_sequence 1 departure_time 07:49:01 (1736837341) is less than previous stop departure_time 08:21:49 (1736839309) - times must increase between two sequential stops
- trip_id 20473140 stop_sequence 1 departure_time 07:49:01 (1736837341) is less than previous stop arrival_time 08:21:49 (1736839309) - times must increase between two sequential stops
- trip_id 20473140 stop_sequence 2 arrival_time 07:51:51 (1736837511) is less than previous stop arrival_time 08:21:49 (1736839309) - times must increase between two sequential stops
- trip_id 20473140 stop_sequence 2 departure_time 07:52:31 (1736837551) is less than previous stop arrival_time 08:21:49 (1736839309) - times must increase between two sequential stops
- trip_id 20472719 stop_sequence 1 departure_time 08:01:32 (1736838092) is less than previous stop departure_time 08:17:46 (1736839066) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_id E037 2 errors
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Sample errors
- trip_id 20472718 has repeating stop_id outlep2 - sequential stop_ids should be different
- trip_id 20472720 has repeating stop_id outlep2 - sequential stop_ids should be different
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 20472886 stop_sequence 16 has stop_id wimcrec but GTFS stop_sequence 16 has stop_id wimcrec2 - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 1 error
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 20473212 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
Warnings
timestamp not populated W001 77 errors
Timestamps should be populated for all elements
Sample errors
- trip_id 20473143 does not have a timestamp
- trip_id 20473140 does not have a timestamp
- trip_id 20756804 does not have a timestamp
- trip_id 20473146 does not have a timestamp
- trip_id 20756813 does not have a timestamp
vehicle_id not populated W002 43 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- trip_id 20756804 does not have a vehicle_id
- trip_id 20756813 does not have a vehicle_id
- trip_id 20756835 does not have a vehicle_id
- trip_id 20756834 does not have a vehicle_id
- trip_id 20756833 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 823 | 29 times (97 % of validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 050 | 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. | 1 195 | 26 times (87 % of validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 103 | 25 times (83 % 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 | 37 | 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 | 39 | 21 times (70 % of validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 20 | 11 times (37 % of validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 10 | 10 times (33 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 10 | 10 times (33 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 8 | 8 times (27 % 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 | 6 | 6 times (20 % 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 2025-01-15 at 04:45 Europe/Paris.
trip_updates (7) service_alerts (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 2025-01-15 at 04:45 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "20756823",
"trip_update": {
"stop_time_update": [
{
"departure": {
"time": "1736913600",
"uncertainty": 120
},
"stop_id": "bsmcca7",
"stop_sequence": 1
}
],
"trip": {
"direction_id": 1,
"route_id": "B2",
"trip_id": "20756823"
}
}
},
{
"id": "20756824",
"trip_update": {
"stop_time_update": [
{
"departure": {
"time": "1736915400",
"uncertainty": 120
},
"stop_id": "bsmcca7",
"stop_sequence": 1
}
],
"trip": {
"direction_id": 1,
"route_id": "B2",
"trip_id": "20756824"
}
}
},
{
"id": "20472924",
"trip_update": {
"stop_time_update": [
{
"departure": {
"time": "1736915280",
"uncertainty": 120
},
"stop_id": "bsmcca2",
"stop_sequence": 1
}
],
"trip": {
"route_id": "CCAB",
"trip_id": "20472924"
}
}
},
{
"id": "20472880",
"trip_update": {
"stop_time_update": [
{
"departure": {
"time": "1736915100",
"uncertainty": 120
},
"stop_id": "wimbast5",
"stop_sequence": 1
}
],
"trip": {
"direction_id": 1,
"route_id": "F",
"trip_id": "20472880"
}
}
},
{
"id": "20472811",
"trip_update": {
"stop_time_update": [
{
"departure": {
"time": "1736915400",
"uncertainty": 120
},
"stop_id": "lpoalpr2",
"stop_sequence": 1
}
],
"trip": {
"route_id": "C",
"trip_id": "20472811"
}
}
},
{
"id": "20472810",
"trip_update": {
"stop_time_update": [
{
"departure": {
"time": "1736914200",
"uncertainty": 120
},
"stop_id": "lpoalpr2",
"stop_sequence": 1
}
],
"trip": {
"route_id": "C",
"trip_id": "20472810"
}
}
},
{
"id": "20575225",
"trip_update": {
"stop_time_update": [
{
"departure": {
"time": "1736915880",
"uncertainty": 120
},
"stop_id": "bsmcca3",
"stop_sequence": 1
}
],
"trip": {
"direction_id": 1,
"route_id": "M1",
"trip_id": "20575225"
}
}
}
],
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1736912740"
}
}