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

2024-10-25
100%
2024-10-26
100%
2024-10-27
100%
2024-10-28
100%
2024-10-29
100%
2024-10-30
99.7%
2024-10-31
100%
2024-11-01
100%
2024-11-02
100%
2024-11-03
100%
2024-11-04
100%
2024-11-05
100%
2024-11-06
100%
2024-11-07
100%
2024-11-08
100%
2024-11-09
100%
2024-11-10
100%
2024-11-11
100%
2024-11-12
100%
2024-11-13
100%
2024-11-14
100%
2024-11-15
100%
2024-11-16
100%
2024-11-17
100%
2024-11-18
100%
2024-11-19
100%
2024-11-20
100%
2024-11-21
100%
2024-11-22
100%
2024-11-23
100%
2024-11-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

No error detected

Validation carried out using the current GTFS file and the GTFS-RT the 2024-11-23 at 08:03 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
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 382 20 times (67 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 40 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. 9 8 times (27 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 110 7 times (23 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 11 5 times (17 % 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)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-11-24 at 01:09 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (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-11-24 at 01:09 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfs_realtime_version": "2.0", "timestamp": "1732406972" } }