Détails de la ressource

Nom du fichier : Données GTFS en temps réel du réseau des cars pour la Corse du Sud.
Format : gtfs-rt

Cette ressource fait partie du jeu de données Réseau interurbain - Corse du Sud (2A).

Disponibilité au téléchargement

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

2 530 erreurs, 225 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 04/11/2025 à 08h00 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 219 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 81bacd6d-f6ba-4692-aca0-5abc762f0afe does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1000189-1000434 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1004758-1006540 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1006162-1008176 does not exist in the GTFS data and does not have schedule_relationship of ADDED
  • trip_id 1006160-1008174 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 219 erreurs

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

Exemples d'erreurs
  • route_id M009-01 does not exist in the GTFS data routes.txt
  • route_id 1000066 does not exist in the GTFS data routes.txt
  • route_id 1000365 does not exist in the GTFS data routes.txt
  • route_id 1000067 does not exist in the GTFS data routes.txt
  • route_id 1000067 does not exist in the GTFS data routes.txt

GTFS-rt stop_id does not exist in GTFS data E011 1 904 erreurs

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

Exemples d'erreurs
  • trip_id 81bacd6d-f6ba-4692-aca0-5abc762f0afe stop_id STP-STP-PORM9 does not exist in GTFS data stops.txt
  • trip_id 81bacd6d-f6ba-4692-aca0-5abc762f0afe stop_id STP-VIGM9 does not exist in GTFS data stops.txt
  • trip_id 81bacd6d-f6ba-4692-aca0-5abc762f0afe stop_id STP-GIRM9 does not exist in GTFS data stops.txt
  • trip_id 1000189-1000434 stop_id 1002856 does not exist in GTFS data stops.txt
  • trip_id 1000189-1000434 stop_id 1002852 does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 164 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 1000189-1000434 stop_sequence 6 arrival_time 07:43:39 (1762238619) is less than previous stop departure_time 07:43:51 (1762238631) - times must increase between two sequential stops
  • trip_id 1006162-1008176 stop_sequence 6 arrival_time 07:51:21 (1762239081) is less than previous stop departure_time 07:52:33 (1762239153) - times must increase between two sequential stops
  • trip_id 1006160-1008174 stop_sequence 7 arrival_time 07:54:14 (1762239254) is less than previous stop departure_time 07:54:56 (1762239296) - times must increase between two sequential stops
  • trip_id 1006160-1008174 stop_sequence 8 arrival_time 07:54:15 (1762239255) is less than previous stop departure_time 07:54:57 (1762239297) - times must increase between two sequential stops
  • trip_id 1000290-1000536 stop_sequence 11 arrival_time 07:47:50 (1762238870) is less than previous stop departure_time 07:47:59 (1762238879) - times must increase between two sequential stops

stop_time_update departure time is before arrival time E025 24 erreurs

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 1000269-1000515 stop_sequence 4 departure_time 07:50:00 (1762239000) is less than the same stop arrival_time 07:57:23 (1762239443) - departure time must be equal to or greater than arrival time
  • trip_id 1005376-1007253 stop_sequence 6 departure_time 07:51:00 (1762239060) is less than the same stop arrival_time 07:58:23 (1762239503) - departure time must be equal to or greater than arrival time
  • trip_id 1005444-1007346 stop_sequence 16 departure_time 07:58:12 (1762239492) is less than the same stop arrival_time 08:00:16 (1762239616) - departure time must be equal to or greater than arrival time
  • trip_id 1005444-1007346 stop_sequence 17 departure_time 07:58:13 (1762239493) is less than the same stop arrival_time 08:00:17 (1762239617) - departure time must be equal to or greater than arrival time
  • trip_id 1003560-1005013 stop_sequence 6 departure_time 07:58:54 (1762239534) is less than the same stop arrival_time 08:00:19 (1762239619) - departure time must be equal to or greater than arrival time

Avertissements

timestamp not populated W001 225 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs
  • trip_id 5e18d9dd-1160-45a7-80e0-5ca093f87550 does not have a timestamp
  • trip_id 1433719e-307e-4463-99dd-08199accca7a does not have a timestamp
  • trip_id bc81c4bd-baf7-4f09-92fc-c6b34e1ef74b does not have a timestamp
  • trip_id 8d5d5f4d-7644-46f0-aef6-c5bb00f11d28 does not have a timestamp
  • trip_id 49802e9a-ba0c-487d-b927-70d99038fe06 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
W001 Timestamps should be populated for all elements 604 25 fois (83 % des validations)
E003 All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED 465 18 fois (60 % des validations)
E004 All route_ids provided in the GTFS-rt feed must exist in the GTFS data 465 18 fois (60 % des validations)
E011 All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt 3 875 18 fois (60 % des validations)
E022 stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. 298 6 fois (20 % 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 27 3 fois (10 % 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. 33 2 fois (7 % des validations)
E051 All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip 1 1 fois (3 % des validations)

Contenu du flux GTFS-RT

Entités

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

{ "entity": [ { "id": "175545", "tripUpdate": { "stopTimeUpdate": [ { "departure": { "delay": -302, "time": "1762253698" }, "stopId": "STP-GIRM9", "stopSequence": 1 }, { "arrival": { "delay": -564, "time": "1762254336" }, "departure": { "delay": -508, "time": "1762254392" }, "stopId": "STP-VIGM9", "stopSequence": 2 }, { "arrival": { "delay": -508, "time": "1762255292" }, "stopId": "STP-GIRM9", "stopSequence": 3 } ], "trip": { "directionId": 0, "routeId": "VIGGIRM9", "scheduleRelationship": "SCHEDULED", "startDate": "20251104", "startTime": "12:00:00", "tripId": "VIGGIRM9-A-M009S2" }, "vehicle": { "id": "311", "label": "SAN GHJASEPPU", "licensePlate": "AJ 935090" } } } ], "header": { "gtfsRealtimeVersion": "2.0", "timestamp": "1762254552" } }