Resource details
This resource file is part of the dataset Réseau urbain moova.
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
❌3 errors, 7 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-05-07 at 09:49 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 2 errors
All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED
Sample errors
- vehicle_id trip_id 18139_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id trip_id 18245_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Vehicle position far from trip shape E029 1 error
The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id.
Sample errors
- entity ID 26 trip_id 18228_0 at (47.619637,6.126814) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
Warnings
vehicle_id not populated W002 7 errors
vehicle_id should be populated for TripUpdates and VehiclePositions
Sample errors
- entity ID 26 does not have a vehicle_id
- entity ID 46 does not have a vehicle_id
- entity ID 48 does not have a vehicle_id
- entity ID 49 does not have a vehicle_id
- entity ID 50 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 |
---|---|---|---|
E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 33 | 23 times (100 % of validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 128 | 23 times (100 % of validations) |
E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 10 | 9 times (39 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-05-09 at 06:52 Europe/Paris.
vehicle_positions (3) service_alerts (0) trip_updates (0)Entities seen in the last 7 days.
vehicle_positionsDecoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-05-09 at 06:52 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "2",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 47.64059829711914,
"longitude": 6.144543170928955
},
"timestamp": "1746766369",
"trip": {
"route_id": "L2",
"schedule_relationship": "SCHEDULED",
"trip_id": "18202_0"
},
"vehicle": {
"label": "239186"
}
}
},
{
"id": "4",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 47.635528564453125,
"longitude": 6.168667793273926
},
"timestamp": "1746766369",
"trip": {
"route_id": "L1",
"schedule_relationship": "SCHEDULED",
"trip_id": "18343_0"
},
"vehicle": {
"label": "199098"
}
}
},
{
"id": "5",
"vehicle": {
"position": {
"bearing": 0.0,
"latitude": 47.643768310546875,
"longitude": 6.167969226837158
},
"timestamp": "1746766369",
"trip": {
"route_id": "L4",
"schedule_relationship": "SCHEDULED",
"trip_id": "18627_0"
},
"vehicle": {
"label": "189026"
}
}
}
],
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1746766374"
}
}