gtfs-rt Transport open dataset - Données en temps réel au format GTFS-RT (VehiclePosition) 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 (VehiclePosition)

Format: gtfs-rt

Download

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

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

❌32 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2026-02-02 at 08:11 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 8 errors

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 155 trip_id 1-671744001 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 223 trip_id 1-705363969 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 153 trip_id 1-621608961 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 65 trip_id 1-453312513 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id 162 trip_id 1-739311617 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 8 errors

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

Sample errors

vehicle_id 155 route_id 40 does not exist in the GTFS data routes.txt
vehicle_id 223 route_id 42 does not exist in the GTFS data routes.txt
vehicle_id 153 route_id 37 does not exist in the GTFS data routes.txt
vehicle_id 65 route_id 27 does not exist in the GTFS data routes.txt
vehicle_id 162 route_id 44 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 8 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors

vehicle_id 155 stop_id 17143 does not exist in GTFS data stops.txt
vehicle_id 223 stop_id 17971 does not exist in GTFS data stops.txt
vehicle_id 153 stop_id 18422 does not exist in GTFS data stops.txt
vehicle_id 65 stop_id 17453 does not exist in GTFS data stops.txt
vehicle_id 162 stop_id 17570 does not exist in GTFS data stops.txt

Vehicle position outside agency coverage area E028 8 errors

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.

Sample errors

vehicle.id 155 at (48.47396,-3.188156) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
vehicle.id 223 at (48.39171,-3.464974) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
vehicle.id 153 at (48.57473,-3.36606) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
vehicle.id 65 at (48.463078,-3.263439) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
vehicle.id 162 at (48.40095,-3.419371) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area

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	79	12 times (75 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	78	12 times (75 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	79	12 times (75 % 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.	65	8 times (50 % of validations)
W001	Timestamps should be populated for all elements	3	3 times (19 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-02-02 at 16:18 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-02-02 at 16:18 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "entity": [
    {
      "id": "171483",
      "vehicle": {
        "currentStopSequence": 3,
        "position": {
          "bearing": 282.0,
          "latitude": 48.4283332824707,
          "longitude": -3.3330938816070557,
          "speed": 9.44444465637207
        },
        "stopId": "17204",
        "timestamp": "1770045362",
        "trip": {
          "directionId": 1,
          "routeId": "19",
          "scheduleRelationship": "SCHEDULED",
          "startDate": "20260202",
          "startTime": "16:00:00",
          "tripId": "1-318963713"
        },
        "vehicle": {
          "id": "162",
          "label": "614",
          "licensePlate": "EC-758-YY"
        }
      }
    },
    {
      "id": "171477",
      "vehicle": {
        "currentStopSequence": 2,
        "position": {
          "bearing": 0.0,
          "latitude": 48.514766693115234,
          "longitude": -3.297729015350342,
          "speed": 0.0
        },
        "stopId": "17283",
        "timestamp": "1770044940",
        "trip": {
          "directionId": 1,
          "routeId": "28",
          "scheduleRelationship": "SCHEDULED",
          "startDate": "20260202",
          "startTime": "16:15:00",
          "tripId": "1-469893121"
        },
        "vehicle": {
          "id": "65",
          "label": "243",
          "licensePlate": "CZ 576 DR"
        }
      }
    },
    {
      "id": "171555",
      "vehicle": {
        "currentStopSequence": 26,
        "position": {
          "latitude": 48.559383392333984,
          "longitude": -3.1051790714263916,
          "speed": 0.0
        },
        "stopId": "16260",
        "timestamp": "1770045423",
        "trip": {
          "directionId": 0,
          "routeId": "1",
          "scheduleRelationship": "SCHEDULED",
          "startDate": "20260202",
          "startTime": "15:42:00",
          "tripId": "25-17104913"
        },
        "vehicle": {
          "id": "4",
          "label": "604",
          "licensePlate": "ET-262-YG"
        }
      }
    },
    {
      "id": "171499",
      "vehicle": {
        "currentStopSequence": 23,
        "position": {
          "bearing": 327.0,
          "latitude": 48.557716369628906,
          "longitude": -3.186177968978882,
          "speed": 8.333333015441895
        },
        "stopId": "16250",
        "timestamp": "1770045412",
        "trip": {
          "directionId": 0,
          "routeId": "4",
          "scheduleRelationship": "SCHEDULED",
          "startDate": "20260202",
          "startTime": "15:36:00",
          "tripId": "25-67502083"
        },
        "vehicle": {
          "id": "58",
          "label": "610",
          "licensePlate": "GE-394-YD"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1770045516"
  }
}