Resource details
GTFS-RT (protobuff) de la position des véhicules.
This resource file is part of the dataset Réseau urbain SNgo!.
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
❌10 errors, 6 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2026-05-06 at 09:09 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 5 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 0200001002FD075E trip_id ATOUMOD007:ServiceJourney:639:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 0200001002FD0751 trip_id ATOUMOD007:ServiceJourney:615:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 0200001002FD0734 trip_id ATOUMOD007:ServiceJourney:621:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 0200001002FD0748 trip_id ATOUMOD007:ServiceJourney:633:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 0200001002FD0758 trip_id ATOUMOD007:ServiceJourney:627:LOC 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 5 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 0200001002FD075E route_id ATOUMOD007:Line:24:LOC does not exist in the GTFS data routes.txt
- vehicle_id 0200001002FD0751 route_id ATOUMOD007:Line:26:LOC does not exist in the GTFS data routes.txt
- vehicle_id 0200001002FD0734 route_id ATOUMOD007:Line:23:LOC does not exist in the GTFS data routes.txt
- vehicle_id 0200001002FD0748 route_id ATOUMOD007:Line:25:LOC does not exist in the GTFS data routes.txt
- vehicle_id 0200001002FD0758 route_id ATOUMOD007:Line:22:LOC does not exist in the GTFS data routes.txt
Warnings
Header timestamp is older than 65 seconds W008 1 error
The data in a GTFS-realtime feed should always be less than one minute old
Sample errors
- header.timestamp is 4 min 27 sec old which is greater than the recommended age of 65 seconds
schedule_relationship not populated W009 5 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id ATOUMOD007:ServiceJourney:639:LOC does not have a schedule_relationship
- trip_id ATOUMOD007:ServiceJourney:615:LOC does not have a schedule_relationship
- trip_id ATOUMOD007:ServiceJourney:621:LOC does not have a schedule_relationship
- trip_id ATOUMOD007:ServiceJourney:633:LOC does not have a schedule_relationship
- trip_id ATOUMOD007:ServiceJourney:627:LOC 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 | 108 | 25 times (83 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 108 | 25 times (83 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 108 | 25 times (83 % of validations) |
| W008 | The data in a GTFS-realtime feed should always be less than one minute old | 5 | 5 times (17 % 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. | 2 | 2 times (7 % of validations) |
| E050 | All timestamps must be less than the current time | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-05-07 at 06:58 Europe/Paris.
vehicle_positions (4) 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-05-07 at 06:58 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "VM:ATOUMOD007:ServiceJourney:147:LOC",
"vehicle": {
"position": {
"bearing": 336.0,
"latitude": 49.0978889465332,
"longitude": 1.4477310180664062
},
"timestamp": "1778129748",
"trip": {
"routeId": "ATOUMOD007:Line:25:LOC",
"tripId": "ATOUMOD007:ServiceJourney:147:LOC"
},
"vehicle": {
"id": "0200001002FD0748"
}
}
},
{
"id": "VM:ATOUMOD007:ServiceJourney:153:LOC",
"vehicle": {
"position": {
"bearing": 133.0,
"latitude": 49.098968505859375,
"longitude": 1.4499390125274658
},
"timestamp": "1778129816",
"trip": {
"routeId": "ATOUMOD007:Line:26:LOC",
"tripId": "ATOUMOD007:ServiceJourney:153:LOC"
},
"vehicle": {
"id": "0200001002FD0751"
}
}
},
{
"id": "VM:ATOUMOD007:ServiceJourney:141:LOC",
"vehicle": {
"position": {
"bearing": 301.0,
"latitude": 49.07963943481445,
"longitude": 1.491178035736084
},
"timestamp": "1778129780",
"trip": {
"routeId": "ATOUMOD007:Line:22:LOC",
"tripId": "ATOUMOD007:ServiceJourney:141:LOC"
},
"vehicle": {
"id": "0200001002FD075E"
}
}
},
{
"id": "VM:ATOUMOD007:ServiceJourney:159:LOC",
"vehicle": {
"position": {
"bearing": 34.0,
"latitude": 49.10823059082031,
"longitude": 1.5001059770584106
},
"timestamp": "1778129823",
"trip": {
"routeId": "ATOUMOD007:Line:24:LOC",
"tripId": "ATOUMOD007:ServiceJourney:159:LOC"
},
"vehicle": {
"id": "0200001002FD0758"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1778129912"
}
}