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

2024-10-22
82.9%
2024-10-23
83%
2024-10-24
100%
2024-10-25
100%
2024-10-26
100%
2024-10-27
100%
2024-10-28
99.5%
2024-10-29
100%
2024-10-30
100%
2024-10-31
100%
2024-11-01
100%
2024-11-02
100%
2024-11-03
100%
2024-11-04
100%
2024-11-05
99.5%
2024-11-06
100%
2024-11-07
100%
2024-11-08
100%
2024-11-09
100%
2024-11-10
100%
2024-11-11
99.4%
2024-11-12
100%
2024-11-13
100%
2024-11-14
100%
2024-11-15
100%
2024-11-16
100%
2024-11-17
100%
2024-11-18
100%
2024-11-19
100%
2024-11-20
100%
2024-11-21
100%
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 2024-11-21 at 08:00 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 190 min 55 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 30 30 times (100 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 62 29 times (97 % of validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 3 496 29 times (97 % of validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 11 1 times (3 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 11 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2024-11-21 at 04:49 Europe/Paris.

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

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

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 2024-11-21 at 04:49 Europe/Paris. You can look at the GTFS-RT documentation.

{ "header": { "gtfs_realtime_version": "2.0", "timestamp": "1732160980" } }