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

Resource details

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

Format: gtfs-rt

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

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

❌6 errors, 9 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

GTFS-rt stop_id does not exist in GTFS data E011 3 errors

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

Sample errors

trip_id 5109341881368576:0 stop_id AVOGR1 does not exist in GTFS data stops.txt
trip_id 6193678114619392:2 stop_id VLOSR1 does not exist in GTFS data stops.txt
trip_id 6331473214832640:2 stop_id AVOMI2 does not exist in GTFS data stops.txt

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 3 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 5109341881368576:0 stop_sequence 1 has stop_id AVOGR1 but GTFS stop_sequence 1 has stop_id 170379 - stop_ids should be the same
GTFS-rt trip_id 6193678114619392:2 stop_sequence 17 has stop_id VLOSR1 but GTFS stop_sequence 17 has stop_id 170253 - stop_ids should be the same
GTFS-rt trip_id 6331473214832640:2 stop_sequence 16 has stop_id AVOMI2 but GTFS stop_sequence 16 has stop_id 170192 - stop_ids should be the same

Warnings

vehicle_id not populated W002 3 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id 5109341881368576:0 does not have a vehicle_id
trip_id 6193678114619392:2 does not have a vehicle_id
trip_id 6331473214832640:2 does not have a vehicle_id

schedule_relationship not populated W009 6 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 5109341881368576:0 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 5109341881368576:0 does not have a schedule_relationship
trip_id 6193678114619392:2 stop_sequence 17 (and potentially more for this trip) does not have a schedule_relationship
trip_id 6193678114619392:2 does not have a schedule_relationship
trip_id 6331473214832640:2 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
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	248	11 times (100 % 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	248	11 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	31	11 times (100 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	62	11 times (100 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	5	5 times (45 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-12-21 at 20:58 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 44 432 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-12-21 at 20:58 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "SM:5179553756479488:10",
      "trip_update": {
        "stop_time_update": [
          {
            "arrival": {
              "delay": 1,
              "time": "1734811083"
            },
            "departure": {
              "delay": 1,
              "time": "1734811093"
            },
            "stop_id": "AVOMI2",
            "stop_sequence": 6
          }
        ],
        "timestamp": "1734810787",
        "trip": {
          "route_id": "zenbus:Line:567330001:LOC",
          "trip_id": "5179553756479488:10"
        }
      }
    }
  ],
  "header": {
    "gtfs_realtime_version": "1.0",
    "timestamp": "1734811086"
  }
}