gtfs-rt Transport open dataset - Horaires temps réel des lignes du réseau TIS for Réseau urbain TIS

Resource details

File name: Horaires temps réel des lignes du réseau TIS

Format: gtfs-rt

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

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

⚠️12 warnings

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

Warnings

vehicle_id not populated W002 4 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 150-0838 does not have a vehicle_id
trip_id 153-0820 does not have a vehicle_id
trip_id 153-0738 does not have a vehicle_id
trip_id 152-0743 does not have a vehicle_id

schedule_relationship not populated W009 8 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 150-0838 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 150-0838 does not have a schedule_relationship
trip_id 153-0820 stop_sequence 2 (and potentially more for this trip) does not have a schedule_relationship
trip_id 153-0820 does not have a schedule_relationship
trip_id 153-0738 stop_sequence 16 (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	252	30 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	502	30 times (100 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	24	24 times (80 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	10	4 times (13 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-11-23 at 19:01 Europe/Paris.

trip_updates (1) service_alerts (0) vehicle_positions (0)

The timestamp field appears to be too old compared to the current time: the delay is 29 214 seconds. Try to update your feed at most every 30 seconds.

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-11-23 at 19:01 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "SM:153-1820",
      "trip_update": {
        "stop_time_update": [
          {
            "arrival": {
              "delay": -49,
              "time": "1732384871"
            },
            "stop_id": "EBERSHEIM-Gare",
            "stop_sequence": 22
          }
        ],
        "timestamp": "1732384661",
        "trip": {
          "direction_id": 1,
          "route_id": "A",
          "trip_id": "153-1820"
        }
      }
    }
  ],
  "header": {
    "gtfs_realtime_version": "1.0",
    "timestamp": "1732384883"
  }
}