Resource details
GTFS-RT (protobuff) de la position des véhicules.
This resource file is part of the dataset Réseaux urbain MOCA.
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
❌6 errors, 2 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-19 at 09:05 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 65c9ff526c306f8b5192db41 trip_id 10 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 67d29b626045b634aa4efebd trip_id 9 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 2 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 65c9ff526c306f8b5192db41 route_id 2 does not exist in the GTFS data routes.txt
- vehicle_id 67d29b626045b634aa4efebd route_id 1 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 2 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 65c9ff526c306f8b5192db41 stop_id 30024 does not exist in GTFS data stops.txt
- vehicle_id 67d29b626045b634aa4efebd stop_id 30044 does not exist in GTFS data stops.txt
Warnings
schedule_relationship not populated W009 2 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 10 does not have a schedule_relationship
- trip_id 9 does not have a schedule_relationship
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 | 50 | 25 times (86 % of validations) |
E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 50 | 25 times (86 % of validations) |
E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 50 | 25 times (86 % of validations) |
W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 50 | 25 times (86 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-04-19 at 15:25 Europe/Paris.
vehicle_positions (1) 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-04-19 at 15:25 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "vehicle:65c9ff526c306f8b5192db41",
"vehicle": {
"current_status": "STOPPED_AT",
"current_stop_sequence": 12,
"position": {
"latitude": 49.527435302734375,
"longitude": 0.9305920004844666
},
"stop_id": "30049",
"timestamp": "1745069101",
"trip": {
"route_id": "2",
"trip_id": "34"
},
"vehicle": {
"id": "65c9ff526c306f8b5192db41",
"label": "42310",
"license_plate": "GT-400-BM"
}
}
}
],
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1745069102"
}
}