Resource details

File name: GTFS-RT
Format: gtfs-rt
Size: 15 B

horaires en temps réel du réseau Tedbus

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

Download availability

2024-10-24
100%
2024-10-25
100%
2024-10-26
100%
2024-10-27
100%
2024-10-28
100%
2024-10-29
100%
2024-10-30
100%
2024-10-31
100%
2024-11-01
100%
2024-11-02
100%
2024-11-03
100%
2024-11-04
100%
2024-11-05
100%
2024-11-06
100%
2024-11-07
100%
2024-11-08
100%
2024-11-09
100%
2024-11-10
100%
2024-11-11
100%
2024-11-12
100%
2024-11-13
100%
2024-11-14
100%
2024-11-15
100%
2024-11-16
100%
2024-11-17
100%
2024-11-18
100%
2024-11-19
100%
2024-11-20
100%
2024-11-21
99.3%
2024-11-22
100%
2024-11-23
100%
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

95 errors, 1 warning

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

Errors

Sequential stop_time_update times are not increasing E022 60 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 trip:3:89 stop_sequence 12 arrival_time 08:18:00 (1732346280) is equal to previous stop arrival_time 08:18:00 (1732346280) - times must increase between two sequential stops
  • trip_id trip:3:89 stop_sequence 12 arrival_time 08:18:00 (1732346280) is equal to previous stop departure_time 08:18:00 (1732346280) - times must increase between two sequential stops
  • trip_id trip:3:89 stop_sequence 12 departure_time 08:18:00 (1732346280) is equal to previous stop departure_time 08:18:00 (1732346280) - times must increase between two sequential stops
  • trip_id trip:3:89 stop_sequence 12 departure_time 08:18:00 (1732346280) is equal to previous stop arrival_time 08:18:00 (1732346280) - times must increase between two sequential stops
  • trip_id trip:3:89 stop_sequence 13 arrival_time 08:18:00 (1732346280) is equal to previous stop arrival_time 08:18:00 (1732346280) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_id E037 1 error

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Sample errors
  • trip_id trip:3:39 has repeating stop_id DRAGUIGNAN - Salamandrier at stop_sequence 5 - sequential stop_ids should be different

stop_time_update doesn't have arrival or departure E043 34 errors

If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided

Sample errors
  • trip_id trip:10:6 stop_sequence 0 doesn't have arrival or departure
  • trip_id trip:10:6 stop_sequence 1 doesn't have arrival or departure
  • trip_id trip:10:6 stop_sequence 2 doesn't have arrival or departure
  • trip_id trip:10:6 stop_sequence 3 doesn't have arrival or departure
  • trip_id trip:10:6 stop_sequence 4 doesn't have arrival or departure

Warnings

ID in one feed missing from the other W003 1 error

a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed

Sample errors
  • trip_id trip:10:0 is in TripUpdates but not in VehiclePositions feed
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
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 1 322 24 times (80 % of validations)
W003 a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed 55 22 times (73 % of validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 44 20 times (67 % of validations)
E043 If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided 151 9 times (30 % 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. 3 3 times (10 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-11-23 at 22:14 Europe/Paris.

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

Entities seen in the last 7 days.

service_alerts trip_updates vehicle_positions

Service alerts

Here is a display of service alerts contained in this feed at 2024-11-23 at 22:14 Europe/Paris.

L5 Centre ville de Trans non desservi Modified service

En raison de travaux le centre ville de Trans-en-Provence n'est plus desservi. Se reporter aux arrêts de La Gare ou St Bernard.

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2024-11-23 at 22:14 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "alert": { "cause": "CONSTRUCTION", "description_text": { "translation": [ { "text": "En raison de travaux le centre ville de Trans-en-Provence n'est plus desservi. Se reporter aux arrêts de La Gare ou St Bernard." } ] }, "effect": "MODIFIED_SERVICE", "header_text": { "translation": [ { "text": "L5 Centre ville de Trans non desservi" } ] }, "informed_entity": [ { "route_id": "5" } ], "severity_level": "UNKNOWN_SEVERITY" }, "id": "alert:672a409d6d0515a8bf801338" } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1732396474" } }