Resource details

File name: GTFS - RT Carsud
Format: gtfs-rt

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

Download availability

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

Validation details

505 errors

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

Errors

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 498 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 340 stop_sequence 4 has stop_id ED0195P but GTFS stop_sequence 4 has stop_id ED 0010C - stop_ids should be the same
  • GTFS-rt trip_id 340 stop_sequence 5 has stop_id ED0200P but GTFS stop_sequence 5 has stop_id ED0195P - stop_ids should be the same
  • GTFS-rt trip_id 340 stop_sequence 6 has stop_id ED0205P but GTFS stop_sequence 6 has stop_id ED0200P - stop_ids should be the same
  • GTFS-rt trip_id 340 stop_sequence 7 has stop_id ED0210P but GTFS stop_sequence 7 has stop_id ED0205P - stop_ids should be the same
  • GTFS-rt trip_id 340 stop_sequence 8 has stop_id ED0215P but GTFS stop_sequence 8 has stop_id ED0210P - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 7 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 677 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 678 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 419 contains stop_sequence 76 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 430 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 813 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
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
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 12 494 29 times (100 % of validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 148 27 times (93 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 35 18 times (62 % 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 35 18 times (62 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 51 13 times (45 % of validations)

GTFS-RT feed content

Entities

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

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

Entities seen in the last 7 days.

trip_updates vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2024-09-19 at 01:23 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "zenbus:Vehicle:348780004:LOC", "vehicle": { "current_status": "STOPPED_AT", "current_stop_sequence": 26, "position": { "latitude": -21.378995895385742, "longitude": 55.619102478027344 }, "stop_id": "SJ0050C", "timestamp": "1726672541", "trip": { "route_id": "GECK", "start_date": "20240918", "start_time": "19:00:00", "trip_id": "303" }, "vehicle": { "id": "zenbus:Vehicle:348780004:LOC" } } }, { "id": "5166723059679232:30", "trip_update": { "stop_time_update": [ { "arrival": { "time": "1726701820" }, "departure": { "time": "1726701830" }, "stop_id": "SJ0050C", "stop_sequence": 26 } ], "timestamp": "1726701783", "trip": { "route_id": "GECK", "start_date": "20240918", "start_time": "19:00:00", "trip_id": "303" }, "vehicle": { "id": "zenbus:Vehicle:348780004:LOC" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1726701783" } }