Resource details

Format: gtfs-rt

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

2024-08-09
100%
2024-08-10
100%
2024-08-11
100%
2024-08-12
100%
2024-08-13
100%
2024-08-14
100%
2024-08-15
100%
2024-08-16
100%
2024-08-17
100%
2024-08-18
100%
2024-08-19
100%
2024-08-20
100%
2024-08-21
100%
2024-08-22
99.4%
2024-08-23
100%
2024-08-24
100%
2024-08-25
100%
2024-08-26
100%
2024-08-27
100%
2024-08-28
100%
2024-08-29
100%
2024-08-30
100%
2024-08-31
100%
2024-09-01
100%
2024-09-02
100%
2024-09-03
100%
2024-09-04
100%
2024-09-05
100%
2024-09-06
100%
2024-09-07
100%
2024-09-08
100%
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.

Validation details

No error detected

Validation carried out using the current GTFS file and the GTFS-RT the 2024-09-07 at 09:00 Europe/Paris using the MobilityData GTFS-RT validator.

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 733 29 times (97 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 654 29 times (97 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 9 6 times (20 % 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. 6 4 times (13 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 2 1 times (3 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 2 1 times (3 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 29 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-09-08 at 02:14 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (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 2024-09-08 at 02:14 Europe/Paris. You can look at the GTFS-RT documentation.

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