Resource details
Flux temps réel Gratibus
This resource file is part of the dataset Réseau urbain Gratibus.
Download availability
Learn more
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
❌7 errors, 1 warning
Validation carried out using the current GTFS file and the GTFS-RT the 2025-08-31 at 09:10 Europe/Paris using the MobilityData GTFS-RT validator.
Errors
Sequential stop_time_update times are not increasing E022 4 errors
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Sample errors
- trip_id B_01 stop_sequence 18 arrival_time 09:20:30 (1756624830) is equal to previous stop arrival_time 09:20:30 (1756624830) - times must increase between two sequential stops
- trip_id B_01 stop_sequence 18 arrival_time 09:20:30 (1756624830) is equal to previous stop departure_time 09:20:30 (1756624830) - times must increase between two sequential stops
- trip_id B_01 stop_sequence 18 departure_time 09:20:30 (1756624830) is equal to previous stop departure_time 09:20:30 (1756624830) - times must increase between two sequential stops
- trip_id B_01 stop_sequence 18 departure_time 09:20:30 (1756624830) is equal to previous stop arrival_time 09:20:30 (1756624830) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 2 errors
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Sample errors
- trip_id Z_R_01 stop_sequence 0 doesn't have arrival or departure
- trip_id Z_R_01 stop_sequence 19 doesn't have arrival or departure
VehiclePosition and TripUpdate ID pairing mismatch E047 1 error
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Sample errors
- trip_id Z_A_02 and vehicle_id 68989efa5cfc5d5cd08d6d65 pairing in VehiclePositions does not match trip_id Z_R_01 and vehicle_id 68989efa5cfc5d5cd08d6d65 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
Warnings
ID in one feed missing from the other W003 1 error
a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed
Sample errors
- trip_id Z_R_01 is in TripUpdates but not in VehiclePositions feed
GTFS-RT feed content
Entities
Entities present in this feed at 2025-11-05 at 12:52 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Decoded GTFS-RT feed
See full payload
Here is the decoded GTFS-RT feed Protobuf at 2025-11-05 at 12:52 Europe/Paris. You can look at the GTFS-RT documentation.
{
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1762343577"
}
}