gtfs-rt Transport open dataset - GTFS-RT réseau de transport en commun DiviaMobilités de Dijon Métropole - Position des véhicules for Réseau urbain DiviaMobilités

Resource details

File name: GTFS-RT réseau de transport en commun DiviaMobilités de Dijon Métropole - Position des véhicules

Format: gtfs-rt

Offre théorique et temps-réel du réseau DiviaMobilités, Dijon Métropole - Position des véhicules

This resource file is part of the dataset Réseau urbain DiviaMobilités.

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

❌2 errors, 26 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-13 at 08:01 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

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

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

Sample errors

vehicle_id 2440 stop_id 4-53 does not exist in GTFS data stops.txt
vehicle_id 2603 stop_id 4-434 does not exist in GTFS data stops.txt

Warnings

vehicle speed is unrealistic W004 26 errors

vehicle.position.speed has an unrealistic speed that may be incorrect

Sample errors

vehicle.id 1008 speed of 27.0 m/s (60.40 mph) is unrealistic
vehicle.id 1021 speed of 42.0 m/s (93.95 mph) is unrealistic
vehicle.id 1023 speed of 41.0 m/s (91.71 mph) is unrealistic
vehicle.id 1025 speed of 29.0 m/s (64.87 mph) is unrealistic
vehicle.id 1026 speed of 33.0 m/s (73.82 mph) is unrealistic

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
W004	vehicle.position.speed has an unrealistic speed that may be incorrect	717	30 times (100 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	32	21 times (70 % of validations)

GTFS-RT feed content

Entities

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


        {
  "entity": [
    {
      "id": "3314",
      "vehicle": {
        "position": {
          "bearing": 335.0,
          "latitude": 47.33863067626953,
          "longitude": 5.070682525634766,
          "speed": 76.0
        },
        "stopId": "4-1077",
        "timestamp": "1773456617",
        "vehicle": {
          "id": "3314",
          "label": "3314"
        }
      }
    },
    {
      "id": "4707",
      "vehicle": {
        "currentStatus": "STOPPED_AT",
        "position": {
          "bearing": 286.0,
          "latitude": 47.32683181762695,
          "longitude": 5.045313358306885,
          "speed": 0.0
        },
        "stopId": "4-1605",
        "timestamp": "1773456477",
        "trip": {
          "directionId": 0,
          "routeId": "4-PL",
          "scheduleRelationship": "SCHEDULED",
          "tripId": "15-PL-1-A-035000"
        },
        "vehicle": {
          "id": "4707",
          "label": "4707"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1773456621"
  }
}