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 :

  • VehiclePosition

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

Download availability

2023-10-30
98.5%
2023-10-31
100%
2023-11-01
95.5%
2023-11-02
94.7%
2023-11-03
100%
2023-11-04
99%
2023-11-05
95.7%
2023-11-06
99%
2023-11-07
100%
2023-11-08
100%
2023-11-09
100%
2023-11-10
100%
2023-11-11
100%
2023-11-12
100%
2023-11-13
100%
2023-11-14
100%
2023-11-15
100%
2023-11-16
100%
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
99.5%
2023-11-24
100%
2023-11-25
100%
2023-11-26
100%
2023-11-27
99.5%
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

❌24 errors

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 6 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 62 trip_id 1-755236866 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 63 trip_id 1-721616897 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 59 trip_id 1-688521217 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 12 trip_id 1-621215745 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • vehicle_id 51 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 6 errors

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

Sample errors
  • vehicle_id 62 route_id 45 does not exist in the GTFS data routes.txt
  • vehicle_id 63 route_id 43 does not exist in the GTFS data routes.txt
  • vehicle_id 59 route_id 41 does not exist in the GTFS data routes.txt
  • vehicle_id 12 route_id 37 does not exist in the GTFS data routes.txt
  • vehicle_id 51 route_id 42 does not exist in the GTFS data routes.txt

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

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

Sample errors
  • vehicle_id 62 stop_id 17205 does not exist in GTFS data stops.txt
  • vehicle_id 63 stop_id 17205 does not exist in GTFS data stops.txt
  • vehicle_id 59 stop_id 17711 does not exist in GTFS data stops.txt
  • vehicle_id 12 stop_id 17515 does not exist in GTFS data stops.txt
  • vehicle_id 51 stop_id 17659 does not exist in GTFS data stops.txt

Vehicle position outside agency coverage area E028 6 errors

The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt.

Sample errors
  • vehicle.id 62 at (48.388454,-3.444386) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 63 at (48.40912,-3.410567) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 59 at (48.44083,-3.473334) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 12 at (48.57417,-3.362573) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
  • vehicle.id 51 at (48.379124,-3.471893) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
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 145 18 times (62 % of validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 145 18 times (62 % of validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 140 18 times (62 % of validations)
E028 The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. 135 18 times (62 % of validations)
W001 Timestamps should be populated for all elements 3 3 times (10 % of validations)
E029 The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. 2 2 times (7 % of validations)
E052 Each vehicle should have a unique ID 5 2 times (7 % of validations)
W004 vehicle.position.speed has an unrealistic speed that may be incorrect 1 1 times (3 % of validations)

GTFS-RT feed content

Entities

Entities present in this feed at 2023-11-29 at 12:32 Europe/Paris.

vehicle_positions (5) 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 2023-11-29 at 12:32 Europe/Paris. You can look at the GTFS-RT documentation.

{ "entity": [ { "id": "103032", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 1, "stop_id": "16218", "trip": { "direction_id": 1, "route_id": "4", "start_date": "20231129", "start_time": "12:42:00", "trip_id": "25-67633165" }, "vehicle": { "id": "6", "label": "D19006", "license_plate": "ET-254-YG" } } }, { "id": "103074", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 19, "position": { "bearing": 62.0, "latitude": 48.77504348754883, "longitude": -3.052053928375244, "speed": 12.222222328186035 }, "stop_id": "6620", "timestamp": "1701257517", "trip": { "direction_id": 1, "route_id": "59", "start_date": "20231129", "start_time": "12:05:00", "trip_id": "25-990576651" }, "vehicle": { "id": "98", "label": "75570", "license_plate": "FZ-256-TS" } } }, { "id": "103030", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 1, "stop_id": "17113", "trip": { "direction_id": 1, "route_id": "1", "start_date": "20231129", "start_time": "12:35:00", "trip_id": "25-17039382" }, "vehicle": { "id": "5", "label": "D19005", "license_plate": "ET-258-YG" } } }, { "id": "103012", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 2, "position": { "latitude": 48.781341552734375, "longitude": -3.0452029705047607 }, "stop_id": "7563", "timestamp": "1701257525", "trip": { "direction_id": 1, "route_id": "56", "start_date": "20231129", "start_time": "12:30:00", "trip_id": "1-939786241" }, "vehicle": { "id": "104", "label": "322", "license_plate": "CJ-675-XP" } } }, { "id": "103078", "vehicle": { "current_status": "IN_TRANSIT_TO", "current_stop_sequence": 2, "position": { "bearing": 273.0, "latitude": 48.78261947631836, "longitude": -3.0473101139068604, "speed": 8.88888931274414 }, "stop_id": "7563", "timestamp": "1701257502", "trip": { "direction_id": 1, "route_id": "57", "start_date": "20231129", "start_time": "12:40:00", "trip_id": "1-956760065" }, "vehicle": { "id": "73", "label": "323", "license_plate": "DK 137 ZN" } } } ], "header": { "gtfs_realtime_version": "2.0", "timestamp": "1701257541" } }