Détails de la ressource

Nom du fichier : Données en temps réel des horaires aux arrêts du réseau Transurbain
Format : gtfs-rt

GTFS-RT (protobuff) des horaires aux arrêts.

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

Disponibilité au téléchargement

09/06/2025
100%
10/06/2025
99.1%
11/06/2025
100%
12/06/2025
100%
13/06/2025
100%
14/06/2025
100%
15/06/2025
97%
16/06/2025
100%
17/06/2025
100%
18/06/2025
100%
19/06/2025
100%
20/06/2025
100%
21/06/2025
97.7%
22/06/2025
92.9%
23/06/2025
96.2%
24/06/2025
89.5%
25/06/2025
98.9%
26/06/2025
100%
27/06/2025
98.3%
28/06/2025
97.6%
29/06/2025
88.5%
30/06/2025
96.2%
01/07/2025
95%
02/07/2025
96.1%
03/07/2025
95.1%
04/07/2025
96%
05/07/2025
91.3%
06/07/2025
88.7%
07/07/2025
93.6%
08/07/2025
96.6%
09/07/2025
94.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. En cas d'erreur 500, nous considèrerons que le flux est indisponible, sauf si il semble contenir du SOAP.

Rapport de validation

69 erreurs, 151 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 09/07/2025 à 09h05 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

stop_times_updates not strictly sorted E002 17 erreurs

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Exemples d'erreurs
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC490870:LOC stop_sequence [1, 2, 3, 3] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC490907:LOC stop_sequence [1, 2, 3, 3] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC491155:LOC stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 21] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC491213:LOC stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 14] is not strictly sorted by increasing stop_sequence
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC491649:LOC stop_sequence [1, 2, 3, 3] is not strictly sorted by increasing stop_sequence

Sequential stop_time_updates have the same stop_sequence E036 17 erreurs

Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence

Exemples d'erreurs
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC490870:LOC has repeating stop_sequence 3 - stop_sequence must increase for each stop_time_update
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC490907:LOC has repeating stop_sequence 3 - stop_sequence must increase for each stop_time_update
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC491155:LOC has repeating stop_sequence 21 - stop_sequence must increase for each stop_time_update
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC491213:LOC has repeating stop_sequence 14 - stop_sequence must increase for each stop_time_update
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC491649:LOC has repeating stop_sequence 3 - stop_sequence must increase for each stop_time_update

Sequential stop_time_updates have the same stop_id E037 17 erreurs

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

Exemples d'erreurs
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC490870:LOC has repeating stop_id FR:27229:ZE:0xHAP01:ATOUMOD004 at stop_sequence 3 - sequential stop_ids should be different
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC490907:LOC has repeating stop_id FR:27229:ZE:0xHAP01:ATOUMOD004 at stop_sequence 3 - sequential stop_ids should be different
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC491155:LOC has repeating stop_id FR:27229:ZE:0xHON02:ATOUMOD004 at stop_sequence 21 - sequential stop_ids should be different
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC491213:LOC has repeating stop_id FR:27229:ZE:0xHON02:ATOUMOD004 at stop_sequence 14 - sequential stop_ids should be different
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC491649:LOC has repeating stop_id FR:27229:ZE:0xHAP01:ATOUMOD004 at stop_sequence 3 - sequential stop_ids should be different

timestamp is in the future E050 1 erreur

All timestamps must be less than the current time

Exemples d'erreurs
  • header.timestamp 09:06:44 (1752044804) is 1 min 5 sec greater than 09:05:38 (1752044738409) - the current time in milliseconds

GTFS-rt stop_sequence not found in GTFS data E051 17 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 ATOUMOD004:ServiceJourney:SemainexETEC490870:LOC contains stop_sequence 3 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD004:ServiceJourney:SemainexETEC490907:LOC contains stop_sequence 3 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD004:ServiceJourney:SemainexETEC491155:LOC contains stop_sequence 21 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD004:ServiceJourney:SemainexETEC491213:LOC contains stop_sequence 14 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id ATOUMOD004:ServiceJourney:SemainexETEC491649:LOC contains stop_sequence 3 that does not exist in GTFS stop_times.txt for this trip

Avertissements

vehicle_id not populated W002 51 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC490870:LOC does not have a vehicle_id
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC490907:LOC does not have a vehicle_id
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC491155:LOC does not have a vehicle_id
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC491213:LOC does not have a vehicle_id
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC394942:LOC does not have a vehicle_id

schedule_relationship not populated W009 100 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC490870:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC490870:LOC does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC490907:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC490907:LOC does not have a schedule_relationship
  • trip_id ATOUMOD004:ServiceJourney:SemainexETEC491155:LOC stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
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
E050 All timestamps must be less than the current time 125 13 fois (45 % des validations)
W002 vehicle_id should be populated for TripUpdates and VehiclePositions 567 12 fois (41 % des validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 1 124 12 fois (41 % des validations)
E002 stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence 83 5 fois (17 % des validations)
E036 Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence 92 5 fois (17 % des validations)
E037 Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id 92 5 fois (17 % 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. 4 4 fois (14 % des validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 164 3 fois (10 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 164 3 fois (10 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 2 123 3 fois (10 % des validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 32 2 fois (7 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 09/07/2025 à 22h26 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (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 09/07/2025 à 22h26 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

{ "header": { "gtfsRealtimeVersion": "1.0", "timestamp": "1752092797" } }