gtfs-rt Transport open dataset - Données en temps réel au format GTFS-RT (VehiclePosition) for Réseau urbain et scolaire Guingamp-Paimpol Mobilité - CA Guingamp-Paimpol Agglomération de l'Armor à l'Argoat

Resource details

File name: Données en temps réel au format GTFS-RT (VehiclePosition)

Format: gtfs-rt

Download

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

We test this resource download availability every hour by making an HTTP 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

❌36 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-03 at 08:10 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 9 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 155 trip_id 1-671744001 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 74 trip_id 1-689111041 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 22 trip_id 1-638320641 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 153 trip_id 1-621608961 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 9 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors

vehicle_id 155 route_id 40 does not exist in the GTFS data routes.txt
vehicle_id 74 route_id 41 does not exist in the GTFS data routes.txt
vehicle_id 22 route_id 38 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 153 route_id 37 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 9 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors

vehicle_id 155 stop_id 17143 does not exist in GTFS data stops.txt
vehicle_id 74 stop_id 17969 does not exist in GTFS data stops.txt
vehicle_id 22 stop_id 17453 does not exist in GTFS data stops.txt
vehicle_id 71 stop_id 17139 does not exist in GTFS data stops.txt
vehicle_id 153 stop_id 18422 does not exist in GTFS data stops.txt

Vehicle position outside agency coverage area E028 9 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 155 at (48.475883,-3.190938) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
vehicle.id 74 at (48.43653,-3.481191) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
vehicle.id 22 at (48.46182,-3.260955) 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.549194,-3.383423) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
vehicle.id 153 at (48.574116,-3.362506) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area

Validate this GTFS-RT now

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	107	12 times (40 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	107	12 times (40 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	99	12 times (40 % 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.	96	12 times (40 % of validations)
W001	Timestamps should be populated for all elements	2	2 times (7 % 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 (3 % of validations)
E052	Each vehicle should have a unique ID	4	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-04 at 05:02 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-03-04 at 05:02 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1772596928"
  }
}