gtfs-rt Transport open dataset - agglobus-offre-theorique-mobilite-reseau-urbain-de-bourges.csv for Réseau urbain AggloBus

Resource details

File name: agglobus-offre-theorique-mobilite-reseau-urbain-de-bourges.csv

Format: gtfs-rt

Agglobus offre théorique mobilité réseau urbain de Bourges (csv)

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

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

⚠️1 warning

Validation carried out using the current GTFS file and the GTFS-RT the 2025-07-06 at 09:07 Europe/Paris using the MobilityData GTFS-RT validator.

Warnings

Header timestamp is older than 65 seconds W008 1 error

The data in a GTFS-realtime feed should always be less than one minute old

Sample errors

header.timestamp is 257 min 2 sec old which is greater than the recommended age of 65 seconds

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
W008	The data in a GTFS-realtime feed should always be less than one minute old	29	29 times (100 % of validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	2	2 times (7 % of validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	154	2 times (7 % of validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	13	1 times (3 % of validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	13	1 times (3 % of validations)
E012	No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp	1	1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2025-07-06 at 04:50 Europe/Paris.

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

The timestamp field appears to be too old compared to the current time: the delay is 18 842 seconds. Try to update your feed at most every 30 seconds.

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2025-07-06 at 04:50 Europe/Paris. You can look at the GTFS-RT documentation.


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