gtfs-rt Transport open dataset - Données en temps réel de la position des véhicules du réseau Astrobus for Réseau urbain Astrobus

Resource details

File name: Données en temps réel de la position des véhicules du réseau Astrobus

Format: gtfs-rt

GTFS-RT (protobuff) de la position des véhicules

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

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

❌38 errors, 12 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2024-11-21 at 08:05 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 12 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 zenbus:Vehicle:5166415361343488:LOC trip_id ATOUMOD036:ServiceJourney:6584075897798656x5:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id zenbus:Vehicle:5166415361343488:LOC trip_id ATOUMOD036:ServiceJourney:6556412902637568x2:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id zenbus:Vehicle:741670006:LOC trip_id ATOUMOD036:ServiceJourney:5060085219852288x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id zenbus:Vehicle:5149698287468544:LOC trip_id ATOUMOD036:ServiceJourney:4644982938927104x2:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
vehicle_id zenbus:Vehicle:728310006:LOC trip_id ATOUMOD036:ServiceJourney:6556412902637568x3:LOC 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 12 errors

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

Sample errors

vehicle_id zenbus:Vehicle:5166415361343488:LOC route_id ATOUMOD036:Line:4809340465709056:LOC does not exist in the GTFS data routes.txt
vehicle_id zenbus:Vehicle:5166415361343488:LOC route_id ATOUMOD036:Line:5131776580124672:LOC does not exist in the GTFS data routes.txt
vehicle_id zenbus:Vehicle:741670006:LOC route_id ATOUMOD036:Line:5089804213551104:LOC does not exist in the GTFS data routes.txt
vehicle_id zenbus:Vehicle:5149698287468544:LOC route_id ATOUMOD036:Line:5089173048393728:LOC does not exist in the GTFS data routes.txt
vehicle_id zenbus:Vehicle:728310006:LOC route_id ATOUMOD036:Line:5131776580124672:LOC does not exist in the GTFS data routes.txt

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

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

Sample errors

vehicle_id zenbus:Vehicle:5166415361343488:LOC stop_id FR:14366:ZE:5207259147665408:ATOUMOD036 does not exist in GTFS data stops.txt
vehicle_id zenbus:Vehicle:5166415361343488:LOC stop_id FR:14303:ZE:19280004:ATOUMOD036 does not exist in GTFS data stops.txt
vehicle_id zenbus:Vehicle:741670006:LOC stop_id FR:14366:ZE:615450039:ATOUMOD036 does not exist in GTFS data stops.txt
vehicle_id zenbus:Vehicle:5149698287468544:LOC stop_id FR:14366:ZE:1190003:ATOUMOD036 does not exist in GTFS data stops.txt
vehicle_id zenbus:Vehicle:728310006:LOC stop_id FR:14366:ZE:1190003:ATOUMOD036 does not exist in GTFS data stops.txt

vehicle.id is not unique E052 2 errors

Each vehicle should have a unique ID

Sample errors

entity ID VM:ATOUMOD036:ServiceJourney:6556412902637568x2:LOC has vehicle.id zenbus:Vehicle:5166415361343488:LOC which is used by more than one vehicle in the feed
entity ID VM:ATOUMOD036:ServiceJourney:5858591379554304x1:LOC has vehicle.id zenbus:Vehicle:5149698287468544:LOC which is used by more than one vehicle in the feed

Warnings

schedule_relationship not populated W009 12 errors

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id ATOUMOD036:ServiceJourney:6584075897798656x5:LOC does not have a schedule_relationship
trip_id ATOUMOD036:ServiceJourney:6556412902637568x2:LOC does not have a schedule_relationship
trip_id ATOUMOD036:ServiceJourney:5060085219852288x0:LOC does not have a schedule_relationship
trip_id ATOUMOD036:ServiceJourney:4644982938927104x2:LOC does not have a schedule_relationship
trip_id ATOUMOD036:ServiceJourney:6556412902637568x3:LOC 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	161	14 times (48 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	161	14 times (48 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	161	14 times (48 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	161	14 times (48 % of validations)
E052	Each vehicle should have a unique ID	16	9 times (31 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-11-21 at 17:29 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 2024-11-21 at 17:29 Europe/Paris. You can look at the GTFS-RT documentation.


{
  "entity": [
    {
      "id": "VM:ATOUMOD036:ServiceJourney:5477981779656704x7:LOC",
      "vehicle": {
        "current_status": "IN_TRANSIT_TO",
        "current_stop_sequence": 6,
        "position": {
          "latitude": 49.02027130126953,
          "longitude": 0.4011479914188385
        },
        "stop_id": "FR:14478:ZE:6193709836140544:ATOUMOD036",
        "timestamp": "1732206536",
        "trip": {
          "direction_id": 1,
          "route_id": "ATOUMOD036:Line:5118765622624256:LOC",
          "trip_id": "ATOUMOD036:ServiceJourney:5477981779656704x7:LOC"
        },
        "vehicle": {
          "id": "zenbus:Vehicle:5073941951414272:LOC"
        }
      }
    },
    {
      "id": "VM:ATOUMOD036:ServiceJourney:5477981779656704x3:LOC",
      "vehicle": {
        "current_status": "IN_TRANSIT_TO",
        "current_stop_sequence": 28,
        "position": {
          "latitude": 49.15726089477539,
          "longitude": 0.22238899767398834
        },
        "stop_id": "FR:14366:ZE:658330001:ATOUMOD036",
        "timestamp": "1732170940",
        "trip": {
          "direction_id": 1,
          "route_id": "ATOUMOD036:Line:5118765622624256:LOC",
          "trip_id": "ATOUMOD036:ServiceJourney:5477981779656704x3:LOC"
        },
        "vehicle": {
          "id": "zenbus:Vehicle:5181291739742208:LOC"
        }
      }
    }
  ],
  "header": {
    "gtfs_realtime_version": "1.0",
    "timestamp": "1732206542"
  }
}