gtfs-rt Transport open dataset - Données en temps réel au format GTFS-RT (TripUpdate) 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 (TripUpdate)

Format: gtfs-rt

Download

Les messages suivants du format GTFS-RT sont disponibles dans ce flux :

TripUpdate

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

❌299 errors, 115 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-01-23 at 08:09 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 28 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors

trip_id 1-890372097 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 1-739311617 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 1-671744001 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 1-755564545 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id 1-604897281 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 28 errors

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

Sample errors

route_id 53 does not exist in the GTFS data routes.txt
route_id 44 does not exist in the GTFS data routes.txt
route_id 40 does not exist in the GTFS data routes.txt
route_id 45 does not exist in the GTFS data routes.txt
route_id 36 does not exist in the GTFS data routes.txt

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

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

Sample errors

trip_id 1-890372097 stop_id 17587 does not exist in GTFS data stops.txt
trip_id 1-890372097 stop_id 17590 does not exist in GTFS data stops.txt
trip_id 1-890372097 stop_id 17911 does not exist in GTFS data stops.txt
trip_id 1-890372097 stop_id 17276 does not exist in GTFS data stops.txt
trip_id 1-890372097 stop_id 18217 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 1 error

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Sample errors

trip_id 1-890372097 stop_sequence 20 arrival_time 08:04:09 (1769151849) is less than previous stop departure_time 08:04:31 (1769151871) - times must increase between two sequential stops

Warnings

timestamp not populated W001 64 errors

Timestamps should be populated for all elements

Sample errors

trip_id 1-890372097 does not have a timestamp
trip_id 1-739311617 does not have a timestamp
trip_id 1-671744001 does not have a timestamp
trip_id 1-755564545 does not have a timestamp
trip_id 1-604897281 does not have a timestamp

vehicle_id not populated W002 51 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 1-621674499 does not have a vehicle_id
trip_id 25-33685514 does not have a vehicle_id
trip_id 25-33816583 does not have a vehicle_id
trip_id 25-33816586 does not have a vehicle_id
trip_id 25-33685510 does not have a vehicle_id

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
W001	Timestamps should be populated for all elements	293	11 times (79 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	76	9 times (64 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	59	9 times (64 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	920	9 times (64 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	244	8 times (57 % of validations)
E025	Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time.	3	3 times (21 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	1	1 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-01-23 at 09:42 Europe/Paris.

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

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2026-01-23 at 09:42 Europe/Paris. You can look at the GTFS-RT documentation.


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