Resource details

File name: https://proxy.transport.data.gouv.fr/resource/rtca-carcassonne-gtfs-rt-trip-update
Format: gtfs-rt

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

Download availability

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

❌913 errors, 24 warnings

Many validation errors indicate that the GTFS-RT identifiers do not match the GTFS identifiers.

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

Errors

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 45 errors

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Sample errors
  • trip_id LMJV SCO RENTREE 2026 V1C211815 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id LMJV SCO RENTREE 2026 V1C211781 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id LMJV SCO RENTREE 2026 V1C211776 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id LMJV SCO RENTREE 2026 V1C211678 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id LMJV SCO RENTREE 2026 V1C211674 does not exist in the GTFS data and does not have schedule_relationship of ADDED

GTFS-rt route_id does not exist in GTFS data E004 45 errors

All route_ids provided in the GTFS-rt feed must exist in the GTFS data

Sample errors
  • route_id 5 does not exist in the GTFS data routes.txt
  • route_id 3 does not exist in the GTFS data routes.txt
  • route_id 3 does not exist in the GTFS data routes.txt
  • route_id 1 does not exist in the GTFS data routes.txt
  • route_id 1 does not exist in the GTFS data routes.txt

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

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

Sample errors
  • trip_id LMJV SCO RENTREE 2026 V1C211815 stop_id 0:BLE01 does not exist in GTFS data stops.txt
  • trip_id LMJV SCO RENTREE 2026 V1C211815 stop_id 0:MRE01 does not exist in GTFS data stops.txt
  • trip_id LMJV SCO RENTREE 2026 V1C211815 stop_id 0:EPR01 does not exist in GTFS data stops.txt
  • trip_id LMJV SCO RENTREE 2026 V1C211815 stop_id 0:MDR01 does not exist in GTFS data stops.txt
  • trip_id LMJV SCO RENTREE 2026 V1C211815 stop_id 0:BTE01 does not exist in GTFS data stops.txt

Warnings

vehicle_id not populated W002 24 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id LMJV SCO RENTREE 2026 V1C211781 does not have a vehicle_id
  • trip_id LMJV SCO RENTREE 2026 V1C211668 does not have a vehicle_id
  • trip_id LMJV SCO RENTREE 2026 V1C211665 does not have a vehicle_id
  • trip_id LMJV SCO RENTREE 2026 V1C211662 does not have a vehicle_id
  • trip_id LMJV SCO RENTREE 2026 V1C211633 does not have a vehicle_id
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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 927 27 times (90 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 927 27 times (90 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 14,188 27 times (90 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 550 27 times (90 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 30 5 times (17 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-11-12 at 23:35 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (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 2026-11-12 at 23:35 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1794522931" } }