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

Détails de la ressource

Nom du fichier : Horaires temps réel des lignes du réseau FORBUS
Format : gtfs-rt
Télécharger

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

Disponibilité au téléchargement

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

Rapport de validation

❌913 erreurs, 227 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 22/02/2025 à 08h01 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 55f8d499-d24f-41b1-87f8-2ded0a995d6a does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 52604673-4412-4050-a10e-091279ee3aad does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id c4f94833-d02b-47a1-a13d-c379e81fbf76 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 2 erreurs

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

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

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

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

Exemples d'erreurs
  • trip_id 2cd05589-79eb-42cf-82bd-7d24b8426a4a stop_id STP- does not exist in GTFS data stops.txt
  • trip_id 2cd05589-79eb-42cf-82bd-7d24b8426a4a stop_id STP-STP-SAINT-THEODORE-2 does not exist in GTFS data stops.txt
  • trip_id 58696285 stop_id STP-RUE-DE-LA-PFISTERQUELLE does not exist in GTFS data stops.txt
  • trip_id 58696285 stop_id STP-RUE-DE-BOURGOGNE does not exist in GTFS data stops.txt
  • trip_id 58695882 stop_id STP-POLE-EMPLOI does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 289 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 58696116 stop_sequence 12 arrival_time 08:20:57 (1740208857) is equal to previous stop arrival_time 08:20:57 (1740208857) - times must increase between two sequential stops
  • trip_id 58696116 stop_sequence 12 arrival_time 08:20:57 (1740208857) is equal to previous stop departure_time 08:20:57 (1740208857) - times must increase between two sequential stops
  • trip_id 58696116 stop_sequence 12 departure_time 08:20:57 (1740208857) is equal to previous stop departure_time 08:20:57 (1740208857) - times must increase between two sequential stops
  • trip_id 58696116 stop_sequence 12 departure_time 08:20:57 (1740208857) is equal to previous stop arrival_time 08:20:57 (1740208857) - times must increase between two sequential stops
  • trip_id 58696116 stop_sequence 14 arrival_time 08:21:57 (1740208917) is equal to previous stop arrival_time 08:21:57 (1740208917) - 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 58696123 stop_sequence 8 departure_time 11:20:00 (1740219600) is less than the same stop arrival_time 11:21:00 (1740219660) - departure time must be equal to or greater than arrival time

GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 457 erreurs

If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt

Exemples d'erreurs
  • GTFS-rt trip_id 2cd05589-79eb-42cf-82bd-7d24b8426a4a stop_sequence 4 has stop_id STP- but GTFS stop_sequence 4 has stop_id stp- - stop_ids should be the same
  • GTFS-rt trip_id 2cd05589-79eb-42cf-82bd-7d24b8426a4a stop_sequence 9 has stop_id STP-STP-SAINT-THEODORE-2 but GTFS stop_sequence 9 has stop_id stp-stp-saint-theodore-2 - stop_ids should be the same
  • GTFS-rt trip_id 2cd05589-79eb-42cf-82bd-7d24b8426a4a stop_sequence 34 has stop_id 160990 but GTFS stop_sequence 34 has stop_id 160991 - stop_ids should be the same
  • GTFS-rt trip_id 2cd05589-79eb-42cf-82bd-7d24b8426a4a stop_sequence 35 has stop_id 161001 but GTFS stop_sequence 35 has stop_id 160990 - stop_ids should be the same
  • GTFS-rt trip_id 2cd05589-79eb-42cf-82bd-7d24b8426a4a stop_sequence 36 has stop_id 160938 but GTFS stop_sequence 36 has stop_id 161001 - stop_ids should be the same

GTFS-rt stop_sequence not found in GTFS data E051 21 erreurs

All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip

Exemples d'erreurs
  • GTFS-rt trip_id 58695882 contains stop_sequence 22 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 58695854 contains stop_sequence 24 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 9dcea6e3-3966-46d3-ab25-85d87540fab8 contains stop_sequence 24 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 57e7f6d9-e032-4fab-98bd-2178c8ad068f contains stop_sequence 24 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id fc71a1d2-c6d5-4a34-8cf4-cfd2afdb0768 contains stop_sequence 24 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 119 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id 2cd05589-79eb-42cf-82bd-7d24b8426a4a does not have a timestamp
  • trip_id 58695794 does not have a timestamp
  • trip_id 58696285 does not have a timestamp
  • trip_id 58695882 does not have a timestamp
  • trip_id 58696116 does not have a timestamp

vehicle_id not populated W002 108 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id 58695914 does not have a vehicle_id
  • trip_id 58695911 does not have a vehicle_id
  • trip_id 58695910 does not have a vehicle_id
  • trip_id 58695894 does not have a vehicle_id
  • trip_id 58695893 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
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 115 26 fois (87 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 3 892 26 fois (87 % des validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 7 646 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. 45 26 fois (87 % des validations)
E045 If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt 11 778 26 fois (87 % des validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 563 26 fois (87 % des validations)
W001 Timestamps should be populated for all elements 3 323 26 fois (87 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 2 934 26 fois (87 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 48 24 fois (80 % des validations)
E043 If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided 16 15 fois (50 % des validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 8 8 fois (27 % des validations)
E023 For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip 3 3 fois (10 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 23/02/2025 à 05h09 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 23/02/2025 à 05h09 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

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