Détails de la ressource

Nom du fichier : Mises à jour des trajets en temps réel
Format : gtfs-rt

Cette ressource fait partie du jeu de données Réseau urbain Sète Agglopole Mobilité.

Disponibilité au téléchargement

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

15 erreurs, 242 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 16/01/2026 à 08h08 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

Sequential stop_time_update times are not increasing E022 12 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 96528_260110-5459 stop_sequence 1 arrival_time 08:10:00 (1768547400) is less than previous stop arrival_time 08:34:36 (1768548876) - times must increase between two sequential stops
  • trip_id 96528_260110-5459 stop_sequence 1 arrival_time 08:10:00 (1768547400) is less than previous stop departure_time 08:34:36 (1768548876) - times must increase between two sequential stops
  • trip_id 96528_260110-5459 stop_sequence 1 departure_time 08:10:00 (1768547400) is less than previous stop departure_time 08:34:36 (1768548876) - times must increase between two sequential stops
  • trip_id 96528_260110-5459 stop_sequence 1 departure_time 08:10:00 (1768547400) is less than previous stop arrival_time 08:34:36 (1768548876) - times must increase between two sequential stops
  • trip_id 96526_260110-5459 stop_sequence 1 arrival_time 09:15:00 (1768551300) is less than previous stop arrival_time 09:38:36 (1768552716) - times must increase between two sequential stops

GTFS-rt stop_sequence not found in GTFS data E051 3 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 96528_260110-5459 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 96526_260110-5459 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
  • GTFS-rt trip_id 96527_260110-5460 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 121 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id 96067_260110-5410 does not have a timestamp
  • trip_id 96026_260110-5410 does not have a timestamp
  • trip_id 96068_260110-5410 does not have a timestamp
  • trip_id 96027_260110-5410 does not have a timestamp
  • trip_id 96069_260110-5410 does not have a timestamp

schedule_relationship not populated W009 121 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs
  • trip_id 96067_260110-5410 stop_sequence 4 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 96026_260110-5410 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 96068_260110-5410 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 96027_260110-5410 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
  • trip_id 96069_260110-5410 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
W001 Timestamps should be populated for all elements 2 623 27 fois (90 % des validations)
W009 trip.schedule_relationship and stop_time_update.schedule_relationship should be populated 2 623 27 fois (90 % des validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 1 024 11 fois (37 % des validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 112 6 fois (20 % des validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 15 4 fois (13 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 16/01/2026 à 21h21 Europe/Paris.

trip_updates (1) vehicle_positions (0) service_alerts (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 16/01/2026 à 21h21 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.

{ "entity": [ { "id": "ENTITY-TRIP-5413-11996-11-0-0", "tripUpdate": { "stopTimeUpdate": [ { "arrival": { "delay": -52, "time": "1768594888" }, "departure": { "delay": -52, "time": "1768594888" }, "stopId": "SETPART1", "stopSequence": 12 }, { "arrival": { "delay": 0, "time": "1768594980" }, "departure": { "delay": 0, "time": "1768594980" }, "stopId": "SETCRI1", "stopSequence": 13 }, { "arrival": { "delay": 0, "time": "1768595063" }, "departure": { "delay": 0, "time": "1768595063" }, "stopId": "SETGMAR1", "stopSequence": 14 }, { "arrival": { "delay": 0, "time": "1768595155" }, "departure": { "delay": 0, "time": "1768595155" }, "stopId": "SETMCOU2", "stopSequence": 15 }, { "arrival": { "delay": 0, "time": "1768595211" }, "departure": { "delay": 0, "time": "1768595211" }, "stopId": "SETESCL1", "stopSequence": 16 }, { "arrival": { "delay": 0, "time": "1768595340" }, "departure": { "delay": 0, "time": "1768595340" }, "stopId": "SETSNCG", "stopSequence": 17 } ], "trip": { "routeId": "8", "scheduleRelationship": "SCHEDULED", "tripId": "95721_260110-5413" }, "vehicle": { "id": "9", "label": "21" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1768594875" } }