Resource details

File name: GTFS-RT Trip-updates moova
Format: gtfs-rt

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

Download availability

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

6 errors, 25 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-05-13 at 09:13 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 6 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • trip_id 18371_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 18245_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 18139_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 18127_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 18219_0 does not exist in the GTFS data and does not have schedule_relationship of ADDED

Warnings

vehicle_id not populated W002 25 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 18104_0 does not have a vehicle_id
  • trip_id 18221_0 does not have a vehicle_id
  • trip_id 18047_0 does not have a vehicle_id
  • trip_id 18369_0 does not have a vehicle_id
  • trip_id 18371_0 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 119 23 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 424 23 times (100 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-05-13 at 20:49 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

trip_updates

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-05-13 at 20:49 Europe/Paris. You can look at the GTFS-RT documentation.

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