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-06-13
100%
2026-07-05
100%
2026-06-27
100%
2026-07-06
100%
2026-07-03
100%
2026-06-14
100%
2026-06-20
100%
2026-07-08
100%
2026-07-02
100%
2026-06-18
100%
2026-06-29
100%
2026-06-12
100%
2026-06-26
100%
2026-06-28
100%
2026-06-21
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

1 error

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

Errors

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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 9 8 times (27 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 9 8 times (27 % of validations)
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 7 7 times (23 % 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-12 at 13:08 Europe/Paris.

vehicle_positions (0) 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-12 at 13:08 Europe/Paris. You can look at the GTFS-RT documentation.

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