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
❌70 errors
Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-12 at 08: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 20 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 223 trip_id 1-721747969 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 71 trip_id 1-604897281 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 219 trip_id 1-772210689 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 218 trip_id 1-906297345 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 13 trip_id 1-940310530 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 20 errors
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Sample errors
- vehicle_id 223 route_id 43 does not exist in the GTFS data routes.txt
- vehicle_id 71 route_id 36 does not exist in the GTFS data routes.txt
- vehicle_id 219 route_id 46 does not exist in the GTFS data routes.txt
- vehicle_id 218 route_id 54 does not exist in the GTFS data routes.txt
- vehicle_id 13 route_id 56 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 12 errors
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Sample errors
- vehicle_id 223 stop_id 17872 does not exist in GTFS data stops.txt
- vehicle_id 71 stop_id 17956 does not exist in GTFS data stops.txt
- vehicle_id 157 stop_id 18443 does not exist in GTFS data stops.txt
- vehicle_id 162 stop_id 17878 does not exist in GTFS data stops.txt
- vehicle_id 156 stop_id 17841 does not exist in GTFS data stops.txt
Vehicle position outside agency coverage area E028 13 errors
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.
Sample errors
- vehicle.id 223 at (48.427902,-3.331389) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 71 at (48.566296,-3.335925) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 51 at (48.397655,-3.512738) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 162 at (48.41451,-3.372043) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 156 at (48.508385,-3.170084) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
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 237 trip_id 1-50659329 at (48.775707,-3.047572) 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 is not unique E052 4 errors
Each vehicle should have a unique ID
Sample errors
- entity ID 172571 has vehicle.id 4 which is used by more than one vehicle in the feed
- entity ID 172572 has vehicle.id 6 which is used by more than one vehicle in the feed
- entity ID 172639 has vehicle.id 156 which is used by more than one vehicle in the feed
- entity ID 172621 has vehicle.id 51 which is used by more than one vehicle in the feed
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 | 154 | 19 times (76 % of validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 153 | 19 times (76 % of validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 146 | 19 times (76 % 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. | 130 | 15 times (60 % of validations) |
| W001 | Timestamps should be populated for all elements | 4 | 4 times (16 % 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 (4 % of validations) |
| E052 | Each vehicle should have a unique ID | 4 | 1 times (4 % of validations) |
GTFS-RT feed content
Entities
Entities present in this feed at 2026-02-12 at 21:04 Europe/Paris.
vehicle_positions (0) 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-02-12 at 21:04 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1770926671"
}
}