Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain CarSud.
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
❌850 erreurs, 2 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 17/06/2025 à 09h12 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
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 5 stop_sequence 21 arrival_time 11:16:57 (1750144617) is less than previous stop departure_time 11:17:41 (1750144661) - times must increase between two sequential stops
- trip_id 704 stop_sequence 13 arrival_time 11:12:02 (1750144322) is less than previous stop departure_time 11:12:10 (1750144330) - times must increase between two sequential stops
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 845 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 215 stop_sequence 2 has stop_id SJ03935P but GTFS stop_sequence 2 has stop_id SJ03930P - stop_ids should be the same
- GTFS-rt trip_id 215 stop_sequence 3 has stop_id SJ00130P but GTFS stop_sequence 3 has stop_id SJ03935P - stop_ids should be the same
- GTFS-rt trip_id 215 stop_sequence 4 has stop_id SJ04525P but GTFS stop_sequence 4 has stop_id SJ00130P - stop_ids should be the same
- GTFS-rt trip_id 215 stop_sequence 5 has stop_id SJ00150P but GTFS stop_sequence 5 has stop_id SJ04525P - stop_ids should be the same
- GTFS-rt trip_id 215 stop_sequence 6 has stop_id SJ00030P but GTFS stop_sequence 6 has stop_id SJ00150P - stop_ids should be the same
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 815 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 708 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id 438 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
Avertissements
vehicle_id not populated W002 1 erreur
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 39 does not have a vehicle_id
ID in one feed missing from the other W003 1 erreur
a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed
Exemples d'erreurs
- trip_id 39 is in TripUpdates but not in VehiclePositions feed
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 |
---|---|---|---|
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 816 | 29 fois (100 % des validations) |
E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 182 | 29 fois (100 % des validations) |
E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 202 | 24 fois (83 % des validations) |
W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 50 | 20 fois (69 % des validations) |
W003 | a trip_id that is provided in the VehiclePositions feed should be provided in the TripUpdates feed, and a vehicle_id that is provided in the TripUpdates feed should be provided in the VehiclePositions feed | 50 | 20 fois (69 % des validations) |
E029 | The vehicle position should be within a certain distance of the GTFS shapes.txt data for the current trip unless there is a Service Alert with the Effect of DETOUR for this trip_id. | 6 | 6 fois (21 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 17/06/2025 à 20h03 Europe/Paris.
vehicle_positions (2) trip_updates (2) service_alerts (0)Entités présentes dans ce flux lors des 7 derniers jours.
trip_updates vehicle_positionsFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 17/06/2025 à 20h03 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"entity": [
{
"id": "zenbus:Vehicle:342430004:LOC",
"vehicle": {
"currentStatus": "STOPPED_AT",
"currentStopSequence": 70,
"position": {
"latitude": -21.282947540283203,
"longitude": 55.53241729736328
},
"stopId": "TA0465C",
"timestamp": "1750174524",
"trip": {
"directionId": 0,
"routeId": "T01A",
"scheduleRelationship": "SCHEDULED",
"startDate": "20250617",
"startTime": "18:50:00",
"tripId": "807"
},
"vehicle": {
"id": "zenbus:Vehicle:342430004:LOC"
}
}
},
{
"id": "5428424584724480:10",
"tripUpdate": {
"stopTimeUpdate": [
{
"arrival": {
"time": "1750183388"
},
"departure": {
"time": "1750183398"
},
"stopId": "TA5090C",
"stopSequence": 72
},
{
"arrival": {
"time": "1750183427"
},
"departure": {
"time": "1750183437"
},
"stopId": "TA0475C",
"stopSequence": 73
}
],
"timestamp": "1750183317",
"trip": {
"directionId": 0,
"routeId": "T01A",
"scheduleRelationship": "SCHEDULED",
"startDate": "20250617",
"startTime": "18:50:00",
"tripId": "807"
},
"vehicle": {
"id": "zenbus:Vehicle:342430004:LOC"
}
}
},
{
"id": "zenbus:Vehicle:378800009:LOC",
"vehicle": {
"currentStopSequence": 17,
"position": {
"latitude": -21.263572692871094,
"longitude": 55.490806579589844
},
"stopId": "TA0002C",
"timestamp": "1750180491",
"trip": {
"directionId": 0,
"routeId": "T06",
"scheduleRelationship": "SCHEDULED",
"startDate": "20250617",
"startTime": "19:20:00",
"tripId": "37"
},
"vehicle": {
"id": "zenbus:Vehicle:378800009:LOC"
}
}
},
{
"id": "807",
"tripUpdate": {
"stopTimeUpdate": [
{
"scheduleRelationship": "SKIPPED",
"stopId": "TA5840C",
"stopSequence": 6
},
{
"scheduleRelationship": "SKIPPED",
"stopId": "TA4130C",
"stopSequence": 7
},
{
"scheduleRelationship": "SKIPPED",
"stopId": "TA0120C",
"stopSequence": 8
},
{
"scheduleRelationship": "SKIPPED",
"stopId": "TA5740C",
"stopSequence": 9
},
{
"scheduleRelationship": "SKIPPED",
"stopId": "TA9255C",
"stopSequence": 10
},
{
"scheduleRelationship": "SKIPPED",
"stopId": "TA7020P",
"stopSequence": 11
},
{
"scheduleRelationship": "SKIPPED",
"stopId": "TA9405P",
"stopSequence": 12
},
{
"scheduleRelationship": "SKIPPED",
"stopId": "TA4140P",
"stopSequence": 13
},
{
"scheduleRelationship": "SKIPPED",
"stopId": "TA1070P",
"stopSequence": 14
},
{
"scheduleRelationship": "SKIPPED",
"stopId": "TA1085P",
"stopSequence": 15
},
{
"scheduleRelationship": "SKIPPED",
"stopId": "TA0001C",
"stopSequence": 16
},
{
"arrival": {
"time": "1750183518"
},
"departure": {
"time": "1750183528"
},
"stopId": "TA0002C",
"stopSequence": 17
}
],
"timestamp": "1750183365",
"trip": {
"directionId": 0,
"routeId": "T06",
"scheduleRelationship": "SCHEDULED",
"startDate": "20250617",
"startTime": "19:20:00",
"tripId": "37"
},
"vehicle": {
"id": "zenbus:Vehicle:378800009:LOC"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "2.0",
"timestamp": "1750183434"
}
}