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
❌50 erreurs, 13 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 03/06/2025 à 09h13 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 7 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 050d0fb3-f72b-4bec-8fcf-3f21a0efb1ac does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 159b0c79-d8f8-4298-8580-c46ba45060f4 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 159b0c79-d8f8-4298-8580-c46ba45060f4 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1006013-1007995 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 1000231-1000476 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 7 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 C13 does not exist in the GTFS data routes.txt
- route_id C13 does not exist in the GTFS data routes.txt
- route_id 1000276 does not exist in the GTFS data routes.txt
- route_id 1000108 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 33 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 050d0fb3-f72b-4bec-8fcf-3f21a0efb1ac stop_id STP-GIRM9 does not exist in GTFS data stops.txt
- trip_id 050d0fb3-f72b-4bec-8fcf-3f21a0efb1ac stop_id STP-VIGM9 does not exist in GTFS data stops.txt
- trip_id 050d0fb3-f72b-4bec-8fcf-3f21a0efb1ac stop_id STP-STP-PORM9 does not exist in GTFS data stops.txt
- trip_id 159b0c79-d8f8-4298-8580-c46ba45060f4 stop_id STP-FRASSETA does not exist in GTFS data stops.txt
- trip_id 159b0c79-d8f8-4298-8580-c46ba45060f4 stop_id STP-RIVISECCU-R does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 2 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 1006013-1007995 stop_sequence 5 arrival_time 07:52:03 (1748929923) is less than previous stop departure_time 07:52:19 (1748929939) - times must increase between two sequential stops
- trip_id 1004126-1005660 stop_sequence 4 arrival_time 08:37:39 (1748932659) is less than previous stop departure_time 08:39:29 (1748932769) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 1 erreur
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 9 has stop_id STP-TR00009 but GTFS stop_sequence 9 has stop_id STP-TR00009-R - stop_ids should be the same
Avertissements
timestamp not populated W001 13 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 050d0fb3-f72b-4bec-8fcf-3f21a0efb1ac does not have a timestamp
- trip_id bc81c4bd-baf7-4f09-92fc-c6b34e1ef74b does not have a timestamp
- trip_id 49802e9a-ba0c-487d-b927-70d99038fe06 does not have a timestamp
- trip_id 7b028b99-002f-4b40-b2c9-ec71905b709c 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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 145 | 30 fois (100 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 145 | 30 fois (100 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 823 | 30 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 311 | 30 fois (100 % 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 | 19 | 19 fois (63 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 25 | 9 fois (30 % 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 | 6 | 6 fois (20 % 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. | 2 | 2 fois (7 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 03/06/2025 à 22h40 Europe/Paris.
trip_updates (1) vehicle_positions (0) service_alerts (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 03/06/2025 à 22h40 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"entity": [
{
"id": "848811",
"tripUpdate": {
"stopTimeUpdate": [
{
"scheduleRelationship": "SKIPPED",
"stopId": "1007892",
"stopSequence": 1
},
{
"arrival": {
"delay": 50,
"time": "1748959490"
},
"departure": {
"delay": 65,
"time": "1748959505"
},
"stopId": "1006426",
"stopSequence": 2
},
{
"arrival": {
"time": "1748959920"
},
"departure": {
"time": "1748959920"
},
"stopId": "1006419",
"stopSequence": 3
},
{
"arrival": {
"time": "1748960400"
},
"stopId": "1005593",
"stopSequence": 4
}
],
"trip": {
"directionId": 1,
"routeId": "1000400",
"scheduleRelationship": "SCHEDULED",
"startDate": "20250603",
"startTime": "16:00:00",
"tripId": "1005474-1007403"
},
"vehicle": {
"id": "700",
"label": "TS2B028",
"licensePlate": "FW-888-RN"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1748983221"
}
}