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

Resource details

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

Format: gtfs-rt

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

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

❌2 errors, 1 warning

Validation carried out using the current GTFS file and the GTFS-RT the 2026-03-09 at 08:09 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 1 error

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 49,758470,393526 trip_id ATOUMOD008:ServiceJourney:9880x0: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 1 error

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

Sample errors

vehicle_id 49,758470,393526 route_id ATOUMOD008:Line:L3:LOC does not exist in the GTFS data routes.txt

Warnings

schedule_relationship not populated W009 1 error

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Sample errors

trip_id ATOUMOD008:ServiceJourney:9880x0: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	19	19 times (68 % of validations)
E004	All route_ids provided in the GTFS-rt feed must exist in the GTFS data	19	19 times (68 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	19	19 times (68 % of validations)
W008	The data in a GTFS-realtime feed should always be less than one minute old	3	3 times (11 % of validations)
E050	All timestamps must be less than the current time	1	1 times (4 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2026-03-09 at 17:17 Europe/Paris.

vehicle_positions (1) 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 2026-03-09 at 17:17 Europe/Paris. You can look at the GTFS-RT documentation.


        {
  "entity": [
    {
      "id": "VM:ATOUMOD008:ServiceJourney:9781x0:LOC",
      "vehicle": {
        "position": {
          "latitude": 49.75450897216797,
          "longitude": 0.3733769953250885
        },
        "timestamp": "1773072959",
        "trip": {
          "routeId": "ATOUMOD008:Line:L01:LOC",
          "tripId": "ATOUMOD008:ServiceJourney:9781x0:LOC"
        },
        "vehicle": {
          "id": "49,754510,373377"
        }
      }
    }
  ],
  "header": {
    "gtfsRealtimeVersion": "1.0",
    "timestamp": "1773073045"
  }
}