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
❌1 error
Validation carried out using the current GTFS file and the GTFS-RT the 2026-07-10 at 09:04 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
trip start_time does not match first GTFS arrival_time E023 1 error
For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip
Sample errors
- GTFS-rt vehicle_id 243 trip_id 25-50397192 start_time is 08:57:00 and GTFS initial arrival_time is 09:08:00 - times do not match
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 | 9 | 8 times (27 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 9 | 8 times (27 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 7 | 6 times (20 % of validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 5 | 5 times (17 % 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. | 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. | 1 | 1 times (3 % of validations) |
| W001 | Timestamps should be populated for all elements | 1 | 1 times (3 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-07-10 at 12:29 Europe/Paris.
vehicle_positions (2) 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-07-10 at 12:29 Europe/Paris. You can look at the GTFS-RT documentation.
{
"entity": [
{
"id": "185882",
"vehicle": {
"currentStopSequence": 12,
"position": {
"bearing": 227.0,
"latitude": 48.7785530090332,
"longitude": -3.0436720848083496,
"speed": 0.5555555820465088
},
"stopId": "17943",
"timestamp": "1783679322",
"trip": {
"directionId": 1,
"routeId": "59",
"scheduleRelationship": "SCHEDULED",
"startDate": "20260710",
"startTime": "12:10:00",
"tripId": "25-990773259"
},
"vehicle": {
"id": "209",
"label": "611",
"licensePlate": "HD-952-HM"
}
}
},
{
"id": "185922",
"vehicle": {
"currentStopSequence": 23,
"position": {
"bearing": 101.0,
"latitude": 48.55310821533203,
"longitude": -3.1113550662994385,
"speed": 14.166666984558105
},
"stopId": "16265",
"timestamp": "1783679300",
"trip": {
"directionId": 0,
"routeId": "1",
"scheduleRelationship": "SCHEDULED",
"startDate": "20260710",
"startTime": "11:51:00",
"tripId": "25-17104900"
},
"vehicle": {
"id": "5",
"label": "605",
"licensePlate": "ET-258-YG"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1783679357"
}
}