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

⚠️66 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-18 at 09:14 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

timestamp not populated W001 35 errors

Timestamps should be populated for all elements

Sample errors

trip_id 15-67239937 does not have a timestamp
trip_id 15-33685506 does not have a timestamp
trip_id 15-16908295 does not have a timestamp
trip_id 25-50397192 does not have a timestamp
trip_id 15-16908304 does not have a timestamp

vehicle_id not populated W002 31 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 15-16908304 does not have a vehicle_id
trip_id 15-16908305 does not have a vehicle_id
trip_id 15-16908291 does not have a vehicle_id
trip_id 15-16908292 does not have a vehicle_id
trip_id 15-16908293 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	930	23 times (77 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	768	23 times (77 % of validations)
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	229	11 times (37 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	229	11 times (37 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	1 834	11 times (37 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	14	3 times (10 % 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.	5	3 times (10 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-18 at 23:36 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 2025-04-18 at 23:36 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfs_realtime_version": "2.0",
    "timestamp": "1745012187"
  }
}