Resource details
GTFS-RT (protobuff) de la position des véhicules.
This resource file is part of the dataset Réseau urbain Néva.
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
❌1 error, 5 warnings
Validation carried out using the current GTFS file and the GTFS-RT the 2025-01-24 at 08:15 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
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
- vehicle.id zenbus:Vehicle:758770006:LOC trip_id ATOUMOD105:ServiceJourney:5119111304577024x2:LOC at (48.84084,-1.549811) 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 5 errors
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Sample errors
- trip_id ATOUMOD105:ServiceJourney:5110781483941888x1:LOC does not have a schedule_relationship
- trip_id ATOUMOD105:ServiceJourney:5119111304577024x1:LOC does not have a schedule_relationship
- trip_id ATOUMOD105:ServiceJourney:5119111304577024x2:LOC does not have a schedule_relationship
- trip_id ATOUMOD105:ServiceJourney:5192777811886080x1:LOC does not have a schedule_relationship
- trip_id ATOUMOD105:ServiceJourney:6253403040645120x0: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 | 41 | 6 times (75 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 41 | 6 times (75 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 41 | 6 times (75 % 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. | 1 | 1 times (13 % of validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 5 | 1 times (13 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2025-01-24 at 23:59 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-01-24 at 23:59 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "VM:ATOUMOD105:ServiceJourney:5110781483941888x24:LOC",
"vehicle": {
"current_status": "IN_TRANSIT_TO",
"current_stop_sequence": 17,
"position": {
"latitude": 48.83803939819336,
"longitude": -1.5943200588226318
},
"stop_id": "FR:50218:ZE:36010105:ATOUMOD105",
"timestamp": "1737743404",
"trip": {
"direction_id": 1,
"route_id": "ATOUMOD105:Line:350210009:LOC",
"trip_id": "ATOUMOD105:ServiceJourney:5110781483941888x24:LOC"
},
"vehicle": {
"id": "zenbus:Vehicle:769100145:LOC"
}
}
}
],
"header": {
"gtfs_realtime_version": "1.0",
"timestamp": "1737759586"
}
}