Resource details

File name: GTFS-RT vehicle-positions moova
Format: gtfs-rt

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

Download availability

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

Validation carried out using the current GTFS file and the GTFS-RT the 2024-12-20 at 08:00 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

Vehicle position far from trip shape E029 1 error

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.

Sample errors
  • entity ID 360255 trip_id 18739_0 at (47.63601,6.102097) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR

Warnings

vehicle_id not populated W002 6 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • entity ID 359777 does not have a vehicle_id
  • entity ID 359802 does not have a vehicle_id
  • entity ID 359807 does not have a vehicle_id
  • entity ID 359876 does not have a vehicle_id
  • entity ID 360255 does not have a vehicle_id
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
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 119 24 times (83 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 2 1 times (3 % 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. 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-12-22 at 04:00 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-12-22 at 04:00 Europe/Paris. You can look at the GTFS-RT documentation.

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