Resource details
Les messages suivants du format GTFS-RT sont disponibles dans ce flux :
- VehiclePosition
This resource file is part of the dataset Réseau urbain et scolaire Guingamp-Paimpol Mobilité.
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
Validation carried out using the current GTFS file and the GTFS-RT the 2025-09-16 at 09:00 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 1 error
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 157 trip_id 1-486604801 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 1 error
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 157 route_id 29 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 1 error
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 157 stop_id 16621 does not exist in GTFS data stops.txt
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 | 3 | 3 times (11 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 3 | 3 times (11 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 3 | 3 times (11 % 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. | 3 | 3 times (11 % of validations) |
| W001 | Timestamps should be populated for all elements | 2 | 2 times (7 % 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 2025-09-16 at 09:39 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-09-16 at 09:39 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "159161",
"vehicle": {
"currentStopSequence": 7,
"position": {
"bearing": 70.0,
"latitude": 48.777225494384766,
"longitude": -3.0467140674591064,
"speed": 3.8888888359069824
},
"stopId": "6639",
"timestamp": "1758008176",
"trip": {
"directionId": 1,
"routeId": "3",
"scheduleRelationship": "SCHEDULED",
"startDate": "20250916",
"startTime": "09:23:00",
"tripId": "25-50462725"
},
"vehicle": {
"id": "31",
"label": "22743",
"licensePlate": "DH-767-EY"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1758008372"
}
}