gtfs-rt Transport open dataset - Offre TC temps réel Colibri for Réseau urbain Colibri

Resource details

File name: Offre TC temps réel Colibri

Format: gtfs-rt

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

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

❌654 errors, 33 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-11 at 08:14 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_times_updates not strictly sorted E002 9 errors

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Sample errors

trip_id COLIBRI:ServiceJourney:LC2x3x0:LOC stop_sequence [28, 11] is not strictly sorted by increasing stop_sequence
trip_id COLIBRI:ServiceJourney:LC3:LOC stop_sequence [8, 17, 14] is not strictly sorted by increasing stop_sequence
trip_id COLIBRI:ServiceJourney:LC5x1:LOC stop_sequence [1, 3, 11, 19, 12] is not strictly sorted by increasing stop_sequence
trip_id COLIBRI:ServiceJourney:LC4:LOC stop_sequence [9, 24, 18] is not strictly sorted by increasing stop_sequence
trip_id COLIBRI:ServiceJourney:LC2:LOC stop_sequence [12, 14, 10] is not strictly sorted by increasing stop_sequence

Sequential stop_time_update times are not increasing E022 612 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 COLIBRI:ServiceJourney:LC1:LOC stop_sequence 32 arrival_time 06:08:46 (1765429726) is less than previous stop arrival_time 06:15:14 (1765430114) - times must increase between two sequential stops
trip_id COLIBRI:ServiceJourney:LC1:LOC stop_sequence 32 departure_time 06:09:12 (1765429752) is less than previous stop arrival_time 06:15:14 (1765430114) - times must increase between two sequential stops
trip_id COLIBRI:ServiceJourney:LC1:LOC stop_sequence 28 arrival_time 06:03:43 (1765429423) is less than previous stop arrival_time 06:08:46 (1765429726) - times must increase between two sequential stops
trip_id COLIBRI:ServiceJourney:LC1:LOC stop_sequence 28 arrival_time 06:03:43 (1765429423) is less than previous stop departure_time 06:09:12 (1765429752) - times must increase between two sequential stops
trip_id COLIBRI:ServiceJourney:LC1:LOC stop_sequence 28 departure_time 06:03:52 (1765429432) is less than previous stop departure_time 06:09:12 (1765429752) - times must increase between two sequential stops

trip direction_id does not match GTFS data E024 11 errors

GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt

Sample errors

GTFS-rt trip_id COLIBRI:ServiceJourney:LC1:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
GTFS-rt trip_id COLIBRI:ServiceJourney:LC2x3x0:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
GTFS-rt trip_id COLIBRI:ServiceJourney:LC3:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
GTFS-rt trip_id COLIBRI:ServiceJourney:LC5x1:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
GTFS-rt trip_id COLIBRI:ServiceJourney:LC4:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 11 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 COLIBRI:ServiceJourney:LC2x3x0:LOC stop_sequence 28 has stop_id FR:01249:ZE:42052:COLIBRI but GTFS stop_sequence 28 has stop_id FR:01249:ZE:64327:COLIBRI - stop_ids should be the same
GTFS-rt trip_id COLIBRI:ServiceJourney:LC3:LOC stop_sequence 8 has stop_id FR:01043:ZE:64324:COLIBRI but GTFS stop_sequence 8 has stop_id FR:01043:ZE:42001:COLIBRI - stop_ids should be the same
GTFS-rt trip_id COLIBRI:ServiceJourney:LC3:LOC stop_sequence 17 has stop_id FR:01376:ZE:41996:COLIBRI but GTFS stop_sequence 17 has stop_id FR:01249:ZE:41992:COLIBRI - stop_ids should be the same
GTFS-rt trip_id COLIBRI:ServiceJourney:LC2:LOC stop_sequence 12 has stop_id FR:01043:ZE:42043:COLIBRI but GTFS stop_sequence 12 has stop_id FR:01043:ZE:64323:COLIBRI - stop_ids should be the same
GTFS-rt trip_id COLIBRI:ServiceJourney:LC2:LOC stop_sequence 14 has stop_id FR:01043:ZE:64323:COLIBRI but GTFS stop_sequence 14 has stop_id FR:01043:ZE:42000:COLIBRI - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 11 errors

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Sample errors

GTFS-rt trip_id COLIBRI:ServiceJourney:LC1:LOC contains stop_sequence 35 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id COLIBRI:ServiceJourney:LC2x3x0:LOC contains stop_sequence 11 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id COLIBRI:ServiceJourney:LC3:LOC contains stop_sequence 14 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id COLIBRI:ServiceJourney:LC5x1:LOC contains stop_sequence 12 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id COLIBRI:ServiceJourney:LC4:LOC contains stop_sequence 18 that does not exist in GTFS stop_times.txt for this trip

Warnings

vehicle_id not populated W002 11 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id COLIBRI:ServiceJourney:LC1:LOC does not have a vehicle_id
trip_id COLIBRI:ServiceJourney:LC2x3x0:LOC does not have a vehicle_id
trip_id COLIBRI:ServiceJourney:LC3:LOC does not have a vehicle_id
trip_id COLIBRI:ServiceJourney:LC5x1:LOC does not have a vehicle_id
trip_id COLIBRI:ServiceJourney:LC4:LOC does not have a vehicle_id

schedule_relationship not populated W009 22 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id COLIBRI:ServiceJourney:LC1:LOC stop_sequence 35 (and potentially more for this trip) does not have a schedule_relationship
trip_id COLIBRI:ServiceJourney:LC1:LOC does not have a schedule_relationship
trip_id COLIBRI:ServiceJourney:LC2x3x0:LOC stop_sequence 28 (and potentially more for this trip) does not have a schedule_relationship
trip_id COLIBRI:ServiceJourney:LC2x3x0:LOC does not have a schedule_relationship
trip_id COLIBRI:ServiceJourney:LC3:LOC stop_sequence 8 (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
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	199	24 times (77 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	12 844	24 times (77 % of validations)
E024	GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt	252	24 times (77 % 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	185	24 times (77 % of validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	216	24 times (77 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	252	24 times (77 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	504	24 times (77 % of validations)
E025	Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time.	94	15 times (48 % of validations)

GTFS-RT feed content

Entities

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


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