Détails de la ressource
Cette ressource fait partie du jeu de données Réseau interurbain de Corse du Sud.
Disponibilité au téléchargement
En savoir plus
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
❌107 erreurs, 12 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 03/04/2025 à 09h00 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 9 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 49802e9a-ba0c-487d-b927-70d99038fe06 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 4ea69cc5-5004-4469-80ab-b38edfb05462 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1003299-1004673 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1000337-1000583 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1005271-1007129 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 8 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id VIGGIRM9 does not exist in the GTFS data routes.txt
- route_id 1000231 does not exist in the GTFS data routes.txt
- route_id 1000210 does not exist in the GTFS data routes.txt
- route_id 1000377 does not exist in the GTFS data routes.txt
- route_id 1000219 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 54 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 4ea69cc5-5004-4469-80ab-b38edfb05462 stop_id STP-GIRM9 does not exist in GTFS data stops.txt
- trip_id 4ea69cc5-5004-4469-80ab-b38edfb05462 stop_id STP-VIGM9 does not exist in GTFS data stops.txt
- trip_id 4ea69cc5-5004-4469-80ab-b38edfb05462 stop_id STP-GIRM9 does not exist in GTFS data stops.txt
- trip_id 1003299-1004673 stop_id 1002680 does not exist in GTFS data stops.txt
- trip_id 1003299-1004673 stop_id 1010960 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 3 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 1003299-1004673 stop_sequence 8 arrival_time 08:21:27 (1743661287) is less than previous stop arrival_time 08:39:59 (1743662399) - times must increase between two sequential stops
- trip_id 1003299-1004673 stop_sequence 8 arrival_time 08:21:27 (1743661287) is less than previous stop departure_time 08:40:22 (1743662422) - times must increase between two sequential stops
- trip_id 1005271-1007129 stop_sequence 8 arrival_time 08:49:00 (1743662940) is less than previous stop departure_time 08:53:41 (1743663221) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 33 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 1433719e-307e-4463-99dd-08199accca7a stop_sequence 5 has stop_id STP-TR00013-R but GTFS stop_sequence 5 has stop_id STP-TR00012-R - stop_ids should be the same
- GTFS-rt trip_id 1433719e-307e-4463-99dd-08199accca7a stop_sequence 6 has stop_id STP-TR00012-R but GTFS stop_sequence 6 has stop_id STP-TR00011-R - stop_ids should be the same
- GTFS-rt trip_id 1433719e-307e-4463-99dd-08199accca7a stop_sequence 7 has stop_id STP-TR00011-R but GTFS stop_sequence 7 has stop_id STP-TR00010-R - stop_ids should be the same
- GTFS-rt trip_id 1433719e-307e-4463-99dd-08199accca7a stop_sequence 8 has stop_id STP-TR00010-R but GTFS stop_sequence 8 has stop_id STP-TR00009-R - stop_ids should be the same
- GTFS-rt trip_id 1433719e-307e-4463-99dd-08199accca7a stop_sequence 9 has stop_id STP-TR00009-R but GTFS stop_sequence 9 has stop_id STP-TR00008 - stop_ids should be the same
Avertissements
timestamp not populated W001 12 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 1433719e-307e-4463-99dd-08199accca7a 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
- trip_id 597c6cdb-9581-41d2-b234-632e7655c19a does not have a timestamp
- trip_id 4ea69cc5-5004-4469-80ab-b38edfb05462 does not have a timestamp
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 959 | 27 fois (90 % 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 | 1 525 | 26 fois (87 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 2 821 | 24 fois (80 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 2 810 | 24 fois (80 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 24 163 | 24 fois (80 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 1 666 | 21 fois (70 % 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 | 21 | 18 fois (60 % 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. | 163 | 17 fois (57 % 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/04/2025 à 04h01 Europe/Paris.
vehicle_positions (0) service_alerts (0) trip_updates (0)Entités présentes dans ce flux lors des 7 derniers jours.
trip_updatesFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 04/04/2025 à 04h01 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1743732089"
}
}