transport.data.gouv.fr transport.data.gouv.fr

Resource details

Format: gtfs-rt

Les messages suivants du format GTFS-RT sont disponibles dans ce flux :

  • TripUpdate

This resource file is part of the dataset Réseau urbain et scolaire Guingamp-Paimpol Mobilité.

Download availability

2023-10-30
98.7%
2023-10-31
100%
2023-11-01
95.3%
2023-11-02
96.6%
2023-11-03
100%
2023-11-04
99.3%
2023-11-05
96%
2023-11-06
100%
2023-11-07
100%
2023-11-08
100%
2023-11-09
100%
2023-11-10
98%
2023-11-11
99.3%
2023-11-12
100%
2023-11-13
99.3%
2023-11-14
100%
2023-11-15
100%
2023-11-16
97.9%
2023-11-17
100%
2023-11-18
100%
2023-11-19
100%
2023-11-20
100%
2023-11-21
100%
2023-11-22
100%
2023-11-23
100%
2023-11-24
100%
2023-11-25
100%
2023-11-26
100%
2023-11-27
100%
2023-11-28
100%
2023-11-29
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

❌147 errors, 87 warnings

Validation carried out using the current GTFS file and the GTFS-RT the 2023-11-29 at 08:10 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
  • trip_id 1-688521217 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1-755236866 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1-604504065 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1-721616897 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1-705232897 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
  • route_id 41 does not exist in the GTFS data routes.txt
  • route_id 45 does not exist in the GTFS data routes.txt
  • route_id 36 does not exist in the GTFS data routes.txt
  • route_id 43 does not exist in the GTFS data routes.txt
  • route_id 42 does not exist in the GTFS data routes.txt

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

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

Sample errors
  • trip_id 1-688521217 stop_id 17852 does not exist in GTFS data stops.txt
  • trip_id 1-688521217 stop_id 17858 does not exist in GTFS data stops.txt
  • trip_id 1-688521217 stop_id 17653 does not exist in GTFS data stops.txt
  • trip_id 1-688521217 stop_id 17855 does not exist in GTFS data stops.txt
  • trip_id 1-688521217 stop_id 17338 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 1 error

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

Sample errors
  • trip_id 1-688521217 stop_sequence 3 arrival_time 07:29:40 (1701239380) is less than previous stop departure_time 07:30:28 (1701239428) - times must increase between two sequential stops

Warnings

timestamp not populated W001 48 errors

Timestamps should be populated for all elements

Sample errors
  • trip_id 1-688521217 does not have a timestamp
  • trip_id 1-755236866 does not have a timestamp
  • trip_id 1-604504065 does not have a timestamp
  • trip_id 1-721616897 does not have a timestamp
  • trip_id 1-705232897 does not have a timestamp

vehicle_id not populated W002 39 errors

vehicle_id should be populated for TripUpdates and VehiclePositions

Sample errors
  • trip_id 1-688586753 does not have a vehicle_id
  • trip_id 1-721682433 does not have a vehicle_id
  • trip_id 1-705298433 does not have a vehicle_id
  • trip_id 1-755302401 does not have a vehicle_id
  • trip_id 1-604569601 does not have a vehicle_id
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
W001 Timestamps should be populated for all elements 1 105 20 times (69 % of validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 891 20 times (69 % of validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 382 18 times (62 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 382 18 times (62 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 3 462 18 times (62 % of validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 114 18 times (62 % of validations)
E025 Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. 4 4 times (14 % of validations)

GTFS-RT feed content

Could not decode the GTFS-RT feed.

The GTFS-RT feed should be accessible over HTTP, without authentication and use the Protobuf format.