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

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

2 errors, 6 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-04-04 at 09:14 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 2 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 trip_id 18371_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id trip_id 18139_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED

Warnings

vehicle_id not populated W002 6 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • entity ID 42 does not have a vehicle_id
  • entity ID 44 does not have a vehicle_id
  • entity ID 45 does not have a vehicle_id
  • entity ID 46 does not have a vehicle_id
  • entity ID 47 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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 68 26 times (93 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 168 26 times (93 % 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. 3 3 times (11 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-04-04 at 21:05 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 2025-04-04 at 21:05 Europe/Paris. You can look at the GTFS-RT documentation.

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