gtfs-rt Transport open dataset - GTFS-RT vehicle-positions moova for Réseau urbain moova

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

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

❌5 errors, 5 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-06-05 at 09:11 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 5 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 1001090511 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id trip_id 1002090012 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id trip_id 1004090511 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id trip_id 1002093511 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id trip_id 1005090512 does not exist in the GTFS data and does not have schedule_relationship of ADDED

Warnings

vehicle_id not populated W002 5 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

entity ID 38 does not have a vehicle_id
entity ID 39 does not have a vehicle_id
entity ID 40 does not have a vehicle_id
entity ID 41 does not have a vehicle_id
entity ID 42 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	85	23 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	136	23 times (100 % 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.	7	5 times (22 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-06-05 at 21:30 Europe/Paris.

vehicle_positions (1) 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-06-05 at 21:30 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "165",
      "vehicle": {
        "position": {
          "bearing": 0.0,
          "latitude": 47.619720458984375,
          "longitude": 6.126483917236328
        },
        "timestamp": "1749144726",
        "trip": {
          "routeId": "L1",
          "scheduleRelationship": "SCHEDULED",
          "tripId": "1001185511"
        },
        "vehicle": {
          "label": "129137"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "2.0",
    "timestamp": "1749151854"
  }
}