Resource details
Données position des véhicules en temps réel, au format GTFS-RT PROTOBUF, du réseau Corolis (urbain)
This resource file is part of the dataset Réseau urbain Corolis.
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
❌2 errors, 24 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-09-09 at 09:10 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Vehicle position far from trip shape E029 2 errors
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
- vehicle.id TBM29078 trip_id 12030 at (49.40862,2.1190538) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id TBM8827 trip_id 12052 at (49.459892,2.113226) 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
schedule_relationship not populated W009 24 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id 16015 does not have a schedule_relationship
- trip_id 12025 does not have a schedule_relationship
- trip_id 15009 does not have a schedule_relationship
- trip_id 12023 does not have a schedule_relationship
- trip_id 11030 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 |
|---|---|---|---|
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 459 | 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. | 32 | 21 times (91 % of validations) |
| E028 | The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. | 1 | 1 times (4 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-09-10 at 04:35 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 2026-09-10 at 04:35 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "VM:19002",
"vehicle": {
"currentStopSequence": 6,
"position": {
"bearing": 25.0,
"latitude": 49.41866683959961,
"longitude": 2.1140732765197754
},
"stopId": "BBRIS1",
"timestamp": "1789007720",
"trip": {
"directionId": 1,
"routeId": "NA",
"tripId": "19002"
},
"vehicle": {
"id": "TBM29080"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1789007735"
}
}