gtfs-rt Transport open dataset - https://proxy.transport.data.gouv.fr/resource/rtca-carcassonne-gtfs-rt-trip-update for Réseau urbain RTCA

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

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

❌667 errors, 21 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-09-18 at 09:14 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 40 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 V1C211822 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id LMJV SCO RENTREE 2026 V1C211819 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id LMJV SCO RENTREE 2026 V1C211807 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id LMJV SCO RENTREE 2026 V1C211798 does not exist in the GTFS data and does not have schedule_relationship of ADDED
trip_id LMJV SCO RENTREE 2026 V1C211783 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 40 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 5 does not exist in the GTFS data routes.txt
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

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

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

Sample errors

trip_id LMJV SCO RENTREE 2026 V1C211822 stop_id 0:GAM01 does not exist in GTFS data stops.txt
trip_id LMJV SCO RENTREE 2026 V1C211819 stop_id 0:BLE01 does not exist in GTFS data stops.txt
trip_id LMJV SCO RENTREE 2026 V1C211819 stop_id 0:MRE01 does not exist in GTFS data stops.txt
trip_id LMJV SCO RENTREE 2026 V1C211819 stop_id 0:EPR01 does not exist in GTFS data stops.txt
trip_id LMJV SCO RENTREE 2026 V1C211819 stop_id 0:MDR01 does not exist in GTFS data stops.txt

Warnings

vehicle_id not populated W002 21 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors

trip_id LMJV SCO RENTREE 2026 V1C211822 does not have a vehicle_id
trip_id LMJV SCO RENTREE 2026 V1C211807 does not have a vehicle_id
trip_id LMJV SCO RENTREE 2026 V1C211798 does not have a vehicle_id
trip_id LMJV SCO RENTREE 2026 V1C211783 does not have a vehicle_id
trip_id LMJV SCO RENTREE 2026 V1C211660 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	402	11 times (100 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	402	11 times (100 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	6,648	11 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	225	11 times (100 % of validations)
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	2	1 times (9 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-09-19 at 03:20 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-09-19 at 03:20 Europe/Paris. You can look at the GTFS-RT documentation.


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