Resource details

Format: gtfs-rt

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

2024-02-01
100%
2024-02-02
100%
2024-02-03
100%
2024-02-04
100%
2024-02-05
99.5%
2024-02-06
100%
2024-02-07
99.5%
2024-02-08
100%
2024-02-09
100%
2024-02-10
100%
2024-02-11
100%
2024-02-12
100%
2024-02-13
100%
2024-02-14
99.6%
2024-02-15
99.5%
2024-02-16
100%
2024-02-17
100%
2024-02-18
100%
2024-02-19
99.5%
2024-02-20
100%
2024-02-21
100%
2024-02-22
100%
2024-02-23
99.6%
2024-02-24
99.5%
2024-02-25
100%
2024-02-26
100%
2024-02-27
99.6%
2024-02-28
100%
2024-02-29
100%
2024-03-01
99.6%
2024-03-02
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-03-02 at 08:02 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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 118 16 times (53 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 118 16 times (53 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 116 16 times (53 % 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. 100 16 times (53 % of validations)
W001 Timestamps should be populated for all elements 3 3 times (10 % 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. 2 2 times (7 % of validations)
E052 Each vehicle should have a unique ID 4 2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-03-02 at 10:18 Europe/Paris.

vehicle_positions (2) 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 2024-03-02 at 10:18 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "111765", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 14, "position": { "bearing": 180.0, "latitude": 48.77012634277344, "longitude": -3.03985595703125, "speed": 10.55555534362793 }, "stop_id": "16870", "timestamp": "1709371111", "trip": { "route_id": "59", "start_date": "20240302", "start_time": "09:54:00", "trip_id": "25-990707715" }, "vehicle": { "id": "98", "label": "75570", "license_plate": "FZ-256-TS" } } }, { "id": "111764", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 23, "position": { "bearing": 355.0, "latitude": 48.55176544189453, "longitude": -3.1014890670776367, "speed": 12.222222328186035 }, "stop_id": "16265", "timestamp": "1709371073", "trip": { "route_id": "1", "start_date": "20240302", "start_time": "09:46:00", "trip_id": "25-16908294" }, "vehicle": { "id": "5", "label": "D19005", "license_plate": "ET-258-YG" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1709371122" } }