gtfs-rt Transport open dataset - GTFS RT du Réseau Orizo for Réseau urbain Orizo

Resource details

File name: GTFS RT du Réseau Orizo

Format: gtfs-rt

Mise à jour du fichier GTFS RT pour le réseau Orizo.

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

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

❌9,822 errors, 549 warnings

Many validation errors indicate that the GTFS-RT identifiers do not match the GTFS identifiers.

Validation carried out using the current GTFS file and the GTFS-RT the 2026-10-16 at 09:16 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

GTFS-rt stop_id does not exist in GTFS data E011 4,911 errors

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Sample errors

trip_id 6234849-26-27-04LaV27-Semaine-00 stop_id 1726 does not exist in GTFS data stops.txt
trip_id 6234849-26-27-04LaV27-Semaine-00 stop_id 1932 does not exist in GTFS data stops.txt
trip_id 6234849-26-27-04LaV27-Semaine-00 stop_id 2044 does not exist in GTFS data stops.txt
trip_id 6234849-26-27-04LaV27-Semaine-00 stop_id 2046 does not exist in GTFS data stops.txt
trip_id 6234849-26-27-04LaV27-Semaine-00 stop_id 2143 does not exist in GTFS data stops.txt

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 4,911 errors

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Sample errors

GTFS-rt trip_id 6234849-26-27-04LaV27-Semaine-00 stop_sequence 1 has stop_id 1726 but GTFS stop_sequence 1 has stop_id 82103 - stop_ids should be the same
GTFS-rt trip_id 6234849-26-27-04LaV27-Semaine-00 stop_sequence 2 has stop_id 1932 but GTFS stop_sequence 2 has stop_id 82177 - stop_ids should be the same
GTFS-rt trip_id 6234849-26-27-04LaV27-Semaine-00 stop_sequence 3 has stop_id 2044 but GTFS stop_sequence 3 has stop_id 82221 - stop_ids should be the same
GTFS-rt trip_id 6234849-26-27-04LaV27-Semaine-00 stop_sequence 4 has stop_id 2046 but GTFS stop_sequence 4 has stop_id 82223 - stop_ids should be the same
GTFS-rt trip_id 6234849-26-27-04LaV27-Semaine-00 stop_sequence 5 has stop_id 2143 but GTFS stop_sequence 5 has stop_id 82290 - stop_ids should be the same

Warnings

vehicle_id not populated W002 102 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 6234849-26-27-04LaV27-Semaine-00 does not have a vehicle_id
trip_id 6234850-26-27-04LaV27-Semaine-00 does not have a vehicle_id
trip_id 6251177-26-27-16LaV27-Semaine-00 does not have a vehicle_id
trip_id 6251178-26-27-16LaV27-Semaine-00 does not have a vehicle_id
trip_id 6251197-26-27-16LaV27-Semaine-00 does not have a vehicle_id

schedule_relationship not populated W009 447 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 6234849-26-27-04LaV27-Semaine-00 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 6234849-26-27-04LaV27-Semaine-00 does not have a schedule_relationship
trip_id 6234850-26-27-04LaV27-Semaine-00 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 6234850-26-27-04LaV27-Semaine-00 does not have a schedule_relationship
trip_id 6251177-26-27-16LaV27-Semaine-00 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship

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	3,011	30 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	12,145	30 times (100 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	88,140	21 times (70 % of validations)
E045	If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt	88,140	21 times (70 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-10-17 at 01:56 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 2026-10-17 at 01:56 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "header": {
    "gtfsRealtimeVersion": "1.0",
    "timestamp": "1792194982"
  }
}