Détails de la ressource

Format : gtfs-rt

Horaires temps-réel du réseau Envia

Cette ressource fait partie du jeu de données Réseau urbain Envia.

Disponibilité au téléchargement

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

125 erreurs, 19 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 26/07/2024 à 09h05 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 3 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 5-857866245 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 5-857866242 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 5-1006698508 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 3 erreurs

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

Exemples d'erreurs
  • route_id 51 does not exist in the GTFS data routes.txt
  • route_id 51 does not exist in the GTFS data routes.txt
  • route_id 60 does not exist in the GTFS data routes.txt

Sequential stop_time_update times are not increasing E022 116 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 5-671285260 stop_sequence 17 arrival_time 09:05:22 (1721977522) is equal to previous stop departure_time 09:05:22 (1721977522) - times must increase between two sequential stops
  • trip_id 5-671285260 stop_sequence 17 departure_time 09:05:22 (1721977522) is equal to previous stop departure_time 09:05:22 (1721977522) - times must increase between two sequential stops
  • trip_id 5-594149408 stop_sequence 22 arrival_time 09:11:23 (1721977883) is equal to previous stop arrival_time 09:11:23 (1721977883) - times must increase between two sequential stops
  • trip_id 5-594149408 stop_sequence 22 arrival_time 09:11:23 (1721977883) is equal to previous stop departure_time 09:11:23 (1721977883) - times must increase between two sequential stops
  • trip_id 5-594149408 stop_sequence 22 departure_time 09:11:23 (1721977883) is equal to previous stop departure_time 09:11:23 (1721977883) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_id E037 3 erreurs

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Exemples d'erreurs
  • trip_id 5-857866245 has repeating stop_id 812 at stop_sequence 2 - sequential stop_ids should be different
  • trip_id 5-857866242 has repeating stop_id 812 at stop_sequence 2 - sequential stop_ids should be different
  • trip_id 5-1006698508 has repeating stop_id 421 at stop_sequence 2 - sequential stop_ids should be different

Avertissements

timestamp not populated W001 19 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id 5-857866245 does not have a timestamp
  • trip_id 5-538574850 does not have a timestamp
  • trip_id 5-671285260 does not have a timestamp
  • trip_id 5-594149408 does not have a timestamp
  • trip_id 5-638189580 does not have a timestamp
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
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 3 435 30 fois (100 % des validations)
W001 Timestamps should be populated for all elements 464 30 fois (100 % des validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 52 26 fois (87 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 50 26 fois (87 % des validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 50 26 fois (87 % 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. 20 16 fois (53 % des validations)

Contenu du flux GTFS-RT

Entités

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

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