Détails de la ressource

Nom du fichier : Données en temps réel au format GTFS-RT (TripUpdate)
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

22/10/2024
100%
23/10/2024
100%
24/10/2024
100%
25/10/2024
100%
26/10/2024
100%
27/10/2024
100%
28/10/2024
100%
29/10/2024
100%
30/10/2024
100%
31/10/2024
99.5%
01/11/2024
100%
02/11/2024
100%
03/11/2024
100%
04/11/2024
100%
05/11/2024
100%
06/11/2024
100%
07/11/2024
100%
08/11/2024
100%
09/11/2024
100%
10/11/2024
100%
11/11/2024
100%
12/11/2024
100%
13/11/2024
100%
14/11/2024
100%
15/11/2024
100%
16/11/2024
100%
17/11/2024
100%
18/11/2024
100%
19/11/2024
99.5%
20/11/2024
99.5%
21/11/2024
99.5%
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. En cas d'erreur 500, nous considèrerons que le flux est indisponible, sauf si il semble contenir du SOAP.

Rapport de validation

304 erreurs, 105 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 21/11/2024 à 08h02 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 28 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-923074561 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1-587530241 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1-739049473 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1-755367937 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1-604766209 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 28 erreurs

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

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

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

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

Exemples d'erreurs
  • trip_id 1-923074561 stop_id 17924 does not exist in GTFS data stops.txt
  • trip_id 1-923074561 stop_id 11058 does not exist in GTFS data stops.txt
  • trip_id 1-923074561 stop_id 8362 does not exist in GTFS data stops.txt
  • trip_id 1-923074561 stop_id 11061 does not exist in GTFS data stops.txt
  • trip_id 1-923074561 stop_id 11060 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 4 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-604766209 stop_sequence 11 arrival_time 07:21:00 (1732170060) is less than previous stop arrival_time 08:11:43 (1732173103) - times must increase between two sequential stops
  • trip_id 1-604766209 stop_sequence 11 arrival_time 07:21:00 (1732170060) is less than previous stop departure_time 08:11:43 (1732173103) - times must increase between two sequential stops
  • trip_id 1-604766209 stop_sequence 11 departure_time 07:21:10 (1732170070) is less than previous stop departure_time 08:11:43 (1732173103) - times must increase between two sequential stops
  • trip_id 1-604766209 stop_sequence 11 departure_time 07:21:10 (1732170070) is less than previous stop arrival_time 08:11:43 (1732173103) - 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-655097857 stop_sequence 2 departure_time 08:02:03 (1732172523) is less than the same stop arrival_time 08:02:07 (1732172527) - departure time must be equal to or greater than arrival time

Avertissements

timestamp not populated W001 59 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id 1-923074561 does not have a timestamp
  • trip_id 1-587530241 does not have a timestamp
  • trip_id 25-16908302 does not have a timestamp
  • trip_id 1-739049473 does not have a timestamp
  • trip_id 1-755367937 does not have a timestamp

vehicle_id not populated W002 46 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id 1-587595778 does not have a vehicle_id
  • trip_id 25-16908308 does not have a vehicle_id
  • trip_id 25-16908317 does not have a vehicle_id
  • trip_id 25-16908291 does not have a vehicle_id
  • trip_id 25-16908292 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 811 20 fois (69 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 640 19 fois (66 % des validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 278 11 fois (38 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 278 11 fois (38 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 2 229 11 fois (38 % 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)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 14 3 fois (10 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 21/11/2024 à 21h53 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 21/11/2024 à 21h53 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

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