Détails de la ressource

Format : gtfs-rt

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

  • TripUpdate

Cette ressource fait partie du jeu de données Réseau urbain et scolaire Guingamp-Paimpol Mobilité.

Disponibilité au téléchargement

28/02/2024
99.3%
29/02/2024
100%
01/03/2024
100%
02/03/2024
100%
03/03/2024
100%
04/03/2024
99.3%
05/03/2024
100%
06/03/2024
99.4%
07/03/2024
99.4%
08/03/2024
100%
09/03/2024
100%
10/03/2024
100%
11/03/2024
100%
12/03/2024
100%
13/03/2024
100%
14/03/2024
99.3%
15/03/2024
100%
16/03/2024
100%
17/03/2024
100%
18/03/2024
100%
19/03/2024
100%
20/03/2024
100%
21/03/2024
100%
22/03/2024
100%
23/03/2024
100%
24/03/2024
100%
25/03/2024
100%
26/03/2024
100%
27/03/2024
99.3%
28/03/2024
99.4%
29/03/2024
97.2%
En savoir plus Nous testons la disponibilité de cette ressource au téléchargement toutes les heures, en effectuant une requête HTTP de type HEAD dont le temps de réponse doit être inférieur à 5 secondes. Si nous détectons une indisponibilité, nous effectuons un nouveau test toutes les 10 minutes, jusqu'à ce que la ressource soit à nouveau disponible.

Pour les flux SIRI et SIRI Lite, nous effectuons une requête HTTP de type GET : nous considérons une réponse avec un code 401 ou 405 comme étant disponible.

Rapport de validation

146 erreurs, 90 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 28/03/2024 à 08h00 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 13 erreurs

All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED

Exemples d'erreurs
  • trip_id 1-587399169 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • 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-705232897 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1-402718721 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 13 erreurs

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

Exemples d'erreurs
  • route_id 35 does not exist in the GTFS data routes.txt
  • 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 42 does not exist in the GTFS data routes.txt
  • route_id 24 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 113 erreurs

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

Exemples d'erreurs
  • trip_id 1-587399169 stop_id 17165 does not exist in GTFS data stops.txt
  • trip_id 1-587399169 stop_id 16678 does not exist in GTFS data stops.txt
  • trip_id 1-587399169 stop_id 17340 does not exist in GTFS data stops.txt
  • trip_id 1-587399169 stop_id 17334 does not exist in GTFS data stops.txt
  • trip_id 1-587399169 stop_id 17331 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 6 erreurs

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

Exemples d'erreurs
  • trip_id 1-688521217 stop_sequence 3 arrival_time 07:30:17 (1711607417) is less than previous stop departure_time 07:30:56 (1711607456) - times must increase between two sequential stops
  • trip_id 1-688521217 stop_sequence 10 arrival_time 07:53:14 (1711608794) is less than previous stop departure_time 07:53:19 (1711608799) - times must increase between two sequential stops
  • trip_id 1-705232897 stop_sequence 6 arrival_time 07:42:34 (1711608154) is less than previous stop arrival_time 08:12:52 (1711609972) - times must increase between two sequential stops
  • trip_id 1-705232897 stop_sequence 6 arrival_time 07:42:34 (1711608154) is less than previous stop departure_time 08:12:52 (1711609972) - times must increase between two sequential stops
  • trip_id 1-705232897 stop_sequence 6 departure_time 07:42:42 (1711608162) is less than previous stop departure_time 08:12:52 (1711609972) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 1 erreur

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.

Exemples d'erreurs
  • trip_id 1-755236866 stop_sequence 6 departure_time 07:59:17 (1711609157) is less than the same stop arrival_time 07:59:40 (1711609180) - departure time must be equal to or greater than arrival time

Avertissements

timestamp not populated W001 49 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id 1-587399169 does not have a timestamp
  • trip_id 1-688521217 does not have a timestamp
  • trip_id 1-755236866 does not have a timestamp
  • trip_id 1-705232897 does not have a timestamp
  • trip_id 25-67371017 does not have a timestamp

vehicle_id not populated W002 41 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id 1-872742914 does not have a vehicle_id
  • trip_id 25-67633163 does not have a vehicle_id
  • trip_id 25-17039387 does not have a vehicle_id
  • trip_id 25-67371020 does not have a vehicle_id
  • trip_id 1-318963713 does not have a vehicle_id
Valider ce GTFS-RT maintenant

Validations précédentes

Voici un récapitulatif des différents types d'erreurs constatés au cours des 30 derniers jours.

Identifiant d'erreur Description Nombre d'erreurs Nombre d'occurences
W001 Timestamps should be populated for all elements 960 21 fois (72 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 804 20 fois (69 % des validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 234 14 fois (48 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 234 14 fois (48 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 2 009 14 fois (48 % des validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 61 13 fois (45 % des 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. 5 5 fois (17 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 29/03/2024 à 06h13 Europe/Paris.

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

Entités présentes dans ce flux lors des 7 derniers jours.

trip_updates

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 29/03/2024 à 06h13 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

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