Resource details

File name: GTFS-RT vehicle-positions grandole mobilités
Format: gtfs-rt

This resource file is part of the dataset Réseau urbain Grandole Mobilités.

Download availability

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

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-16 at 08:17 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 1 error

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 71111 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 1 error

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors
  • vehicle_id route_id J11B does not exist in the GTFS data routes.txt

Warnings

vehicle_id not populated W002 14 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • entity ID 30 does not have a vehicle_id
  • entity ID 31 does not have a vehicle_id
  • entity ID 32 does not have a vehicle_id
  • entity ID 33 does not have a vehicle_id
  • entity ID 34 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 301 26 times (87 % 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. 12 9 times (30 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 3 3 times (10 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 3 3 times (10 % of validations)

GTFS-RT feed content

Entities

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

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1765940803" } }