Resource details

Format: gtfs-rt

GTS-RT Navette la Crèche

This resource file is part of the dataset Navette La Crèche (CC Haut Val de Sèvre).

Download availability

2024-04-02
100%
2024-04-03
100%
2024-04-04
100%
2024-04-05
100%
2024-04-06
100%
2024-04-07
100%
2024-04-08
100%
2024-04-09
99.5%
2024-04-10
100%
2024-04-11
100%
2024-04-12
100%
2024-04-13
100%
2024-04-14
100%
2024-04-15
100%
2024-04-16
100%
2024-04-17
100%
2024-04-18
100%
2024-04-19
100%
2024-04-20
100%
2024-04-21
100%
2024-04-22
100%
2024-04-23
100%
2024-04-24
100%
2024-04-25
100%
2024-04-26
100%
2024-04-27
100%
2024-04-28
100%
2024-04-29
100%
2024-04-30
99.5%
2024-05-01
100%
2024-05-02
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.

Validation details

9 errors

Validation carried out using the current GTFS file and the GTFS-RT the 2023-10-03 at 09: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 2 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 a759e939db338fc9 trip_id NAV_A2 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id NAV_A2 does not exist in the GTFS data and does not have schedule_relationship of ADDED

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

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

Sample errors
  • vehicle_id a759e939db338fc9 stop_id Chavagné does not exist in GTFS data stops.txt
  • trip_id NAV_A2 stop_id Chavagné does not exist in GTFS data stops.txt
  • trip_id NAV_A2 stop_id PARPIN does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 4 errors

stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.

Sample errors
  • trip_id NAV_A2 stop_sequence 9 arrival_time 08:59:37 (1696316377) is less than previous stop arrival_time 09:00:33 (1696316433) - times must increase between two sequential stops
  • trip_id NAV_A2 stop_sequence 9 arrival_time 08:59:37 (1696316377) is less than previous stop departure_time 09:00:40 (1696316440) - times must increase between two sequential stops
  • trip_id NAV_A2 stop_sequence 9 departure_time 08:59:49 (1696316389) is less than previous stop departure_time 09:00:40 (1696316440) - times must increase between two sequential stops
  • trip_id NAV_A2 stop_sequence 9 departure_time 08:59:49 (1696316389) is less than previous stop arrival_time 09:00:33 (1696316433) - times must increase between two sequential stops
Validate this GTFS-RT now

GTFS-RT feed content

Entities

Entities present in this feed at 2024-05-02 at 11:53 Europe/Paris.

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

Decoded GTFS-RT feed

See full payload

Here is the decoded GTFS-RT feed Protobuf at 2024-05-02 at 11:53 Europe/Paris. You can look at the GTFS-RT documentation.

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