gtfs-rt Transport open dataset - Position des véhicules en temps réel pour les lignes du réseau Astuce exploitées par Transdev Rouen for Réseau urbain Astuce

Resource details

File name: Position des véhicules en temps réel pour les lignes du réseau Astuce exploitées par Transdev Rouen

Format: gtfs-rt

Ce fichier au format GTFS-RT contient la position des véhicules en temps réel (vehicle position) pour les lignes exploitées par Transdev Rouen.

La fréquence de rafraîchissement de ces données est de 30 secondes.

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

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

❌657 errors, 219 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2025-12-15 at 08:03 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 219 errors

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

Sample errors

vehicle_id TCAR:Vehicle::427:LOC trip_id 22430 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id TCAR:Vehicle::6223:LOC trip_id 49 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id TCAR:Vehicle::5410:LOC trip_id 15012 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id TCAR:Vehicle::7202:LOC trip_id 12705 does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id TCAR:Vehicle::5403:LOC trip_id 9701 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 219 errors

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

Sample errors

vehicle_id TCAR:Vehicle::427:LOC route_id 27 does not exist in the GTFS data routes.txt
vehicle_id TCAR:Vehicle::6223:LOC route_id 92 does not exist in the GTFS data routes.txt
vehicle_id TCAR:Vehicle::5410:LOC route_id 04 does not exist in the GTFS data routes.txt
vehicle_id TCAR:Vehicle::7202:LOC route_id 02 does not exist in the GTFS data routes.txt
vehicle_id TCAR:Vehicle::5403:LOC route_id 94 does not exist in the GTFS data routes.txt

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

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

Sample errors

vehicle_id TCAR:Vehicle::427:LOC stop_id LOUIS0 does not exist in GTFS data stops.txt
vehicle_id TCAR:Vehicle::6223:LOC stop_id TAMAR does not exist in GTFS data stops.txt
vehicle_id TCAR:Vehicle::5410:LOC stop_id HMAIR0 does not exist in GTFS data stops.txt
vehicle_id TCAR:Vehicle::7202:LOC stop_id VAREN0 does not exist in GTFS data stops.txt
vehicle_id TCAR:Vehicle::5403:LOC stop_id SANTE1 does not exist in GTFS data stops.txt

Warnings

schedule_relationship not populated W009 219 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id 22430 does not have a schedule_relationship
trip_id 49 does not have a schedule_relationship
trip_id 15012 does not have a schedule_relationship
trip_id 12705 does not have a schedule_relationship
trip_id 9701 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
E003	All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED	4 712	28 times (90 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	4 712	28 times (90 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	4 712	28 times (90 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	4 712	28 times (90 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-12-16 at 04:31 Europe/Paris.

vehicle_positions (2) service_alerts (0) trip_updates (0)

Entities seen in the last 7 days.

vehicle_positions

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-12-16 at 04:31 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "VM:544",
      "vehicle": {
        "currentStopSequence": 2,
        "position": {
          "bearing": 201.0,
          "latitude": 49.48139953613281,
          "longitude": 1.0482124090194702
        },
        "stopId": "MOULI1",
        "timestamp": "1765855881",
        "trip": {
          "routeId": "92",
          "tripId": "544"
        },
        "vehicle": {
          "id": "TCAR:Vehicle::6205:LOC"
        }
      }
    },
    {
      "id": "VM:4899",
      "vehicle": {
        "currentStatus": "STOPPED_AT",
        "currentStopSequence": 14,
        "position": {
          "bearing": 143.0,
          "latitude": 49.400421142578125,
          "longitude": 1.042414665222168
        },
        "stopId": "BRAQU1",
        "timestamp": "1765855872",
        "trip": {
          "directionId": 1,
          "routeId": "90",
          "tripId": "4899"
        },
        "vehicle": {
          "id": "TCAR:Vehicle::839:LOC"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "1.0",
    "timestamp": "1765855895"
  }
}