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

❌1 error, 68 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2024-12-20 at 08:02 Europe/Paris using the MobilityData GTFS-RT validator.

Errors

stop_time_update departure time is before arrival time E025 1 error

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.

Sample errors

trip_id 99 stop_sequence 30 departure_time 08:23:00 (1734679380) is less than the same stop arrival_time 08:23:13 (1734679393) - departure time must be equal to or greater than arrival time

Warnings

vehicle_id not populated W002 34 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 100 does not have a vehicle_id
trip_id 102 does not have a vehicle_id
trip_id 108 does not have a vehicle_id
trip_id 116 does not have a vehicle_id
trip_id 117 does not have a vehicle_id

schedule_relationship not populated W009 34 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 100 stop_sequence 4 (and potentially more for this trip) does not have a schedule_relationship
trip_id 102 stop_sequence 4 (and potentially more for this trip) does not have a schedule_relationship
trip_id 108 stop_sequence 4 (and potentially more for this trip) does not have a schedule_relationship
trip_id 116 stop_sequence 3 (and potentially more for this trip) does not have a schedule_relationship
trip_id 117 stop_sequence 3 (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	478	18 times (60 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	478	18 times (60 % 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.	16	12 times (40 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	2	2 times (7 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-12-21 at 01:18 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (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 2024-12-21 at 01:18 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "header": {
    "gtfs_realtime_version": "1.0",
    "timestamp": "1734740312"
  }
}