Resource details

File name: Données en temps réel au format GTFS-RT (VehiclePosition)
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

2026-06-19
100%
2026-06-16
100%
2026-06-15
100%
2026-07-09
100%
2026-06-25
100%
2026-07-05
100%
2026-07-15
100%
2026-06-27
100%
2026-07-06
100%
2026-07-03
100%
2026-07-13
100%
2026-06-20
100%
2026-07-08
100%
2026-07-02
100%
2026-06-18
100%
2026-06-29
100%
2026-06-26
100%
2026-06-28
100%
2026-06-21
100%
2026-07-14
100%
2026-06-23
100%
2026-07-01
100%
2026-07-11
100%
2026-06-17
100%
2026-07-10
100%
2026-06-30
100%
2026-07-07
100%
2026-06-22
100%
2026-07-12
100%
2026-07-04
100%
2026-06-24
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. In case of HTTP 500, the feed will be considered unavailable, unless the body appears to contain SOAP.

Validation details

3 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2026-07-15 at 09:03 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 1 error

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 58 trip_id 1-318963713 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 1 error

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

Sample errors
  • vehicle_id 58 route_id 19 does not exist in the GTFS data routes.txt

trip start_time does not match first GTFS arrival_time E023 1 error

For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip

Sample errors
  • GTFS-rt vehicle_id 243 trip_id 25-50397192 start_time is 08:57:00 and GTFS initial arrival_time is 09:08:00 - times do not match
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
E023 For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip 10 10 times (33 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 10 9 times (30 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 10 9 times (30 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 7 6 times (20 % 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. 5 5 times (17 % 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. 1 1 times (3 % of validations)
W001 Timestamps should be populated for all elements 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-07-15 at 10:51 Europe/Paris.

vehicle_positions (4) 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-07-15 at 10:51 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "186307", "vehicle": { "currentStopSequence": 9, "position": { "bearing": 242.0, "latitude": 48.7800407409668, "longitude": -3.061505079269409, "speed": 0.2777777910232544 }, "stopId": "6635", "timestamp": "1784105406", "trip": { "directionId": 1, "routeId": "19", "scheduleRelationship": "SCHEDULED", "startDate": "20260715", "startTime": "10:35:00", "tripId": "1-318963713" }, "vehicle": { "id": "58", "label": "610", "licensePlate": "GE-394-YD" } } }, { "id": "186232", "vehicle": { "currentStopSequence": 13, "position": { "bearing": 199.0, "latitude": 48.781646728515625, "longitude": -3.049298048019409, "speed": 8.88888931274414 }, "stopId": "17777", "timestamp": "1784105472", "trip": { "directionId": 1, "routeId": "59", "scheduleRelationship": "SCHEDULED", "startDate": "20260715", "startTime": "10:31:00", "tripId": "25-990773252" }, "vehicle": { "id": "209", "label": "611", "licensePlate": "HD-952-HM" } } }, { "id": "186203", "vehicle": { "currentStopSequence": 8, "position": { "bearing": 98.0, "latitude": 48.572444915771484, "longitude": -3.1390159130096436, "speed": 8.88888931274414 }, "stopId": "16242", "timestamp": "1784105474", "trip": { "directionId": 0, "routeId": "2", "scheduleRelationship": "SCHEDULED", "startDate": "20260715", "startTime": "10:40:00", "tripId": "25-33685508" }, "vehicle": { "id": "6", "label": "606", "licensePlate": "ET-254-YG" } } }, { "id": "186202", "vehicle": { "currentStopSequence": 11, "position": { "latitude": 48.56689453125, "longitude": -3.1677980422973633, "speed": 0.0 }, "stopId": "6052", "timestamp": "1784105469", "trip": { "directionId": 0, "routeId": "4", "scheduleRelationship": "SCHEDULED", "startDate": "20260715", "startTime": "10:35:00", "tripId": "25-67239939" }, "vehicle": { "id": "4", "label": "604", "licensePlate": "ET-262-YG" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1784105505" } }