Détails de la ressource
Ce jeu de données propose les horaires en temps réel du réseau interurbain Car Jaune à La Réunion au format GTFS-RT.
Cette ressource fait partie du jeu de données Réseau interurbain Cars Jaunes.
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
❌23 erreurs, 84 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 27/11/2025 à 08h11 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
Sequential stop_time_update times are not increasing E022 4 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-335872020 stop_sequence 24 arrival_time 09:51:50 (1764222710) is less than previous stop arrival_time 09:52:38 (1764222758) - times must increase between two sequential stops
- trip_id 5-335872020 stop_sequence 24 arrival_time 09:51:50 (1764222710) is less than previous stop departure_time 09:53:21 (1764222801) - times must increase between two sequential stops
- trip_id 5-335872020 stop_sequence 24 departure_time 09:51:50 (1764222710) is less than previous stop departure_time 09:53:21 (1764222801) - times must increase between two sequential stops
- trip_id 5-335872020 stop_sequence 24 departure_time 09:51:50 (1764222710) is less than previous stop arrival_time 09:52:38 (1764222758) - times must increase between two sequential stops
stop_time_update doesn't have arrival or departure E043 16 erreurs
If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided
Exemples d'erreurs
- trip_id 5-218169349 stop_sequence 3 doesn't have arrival or departure
- trip_id 5-335872020 stop_sequence 11 doesn't have arrival or departure
- trip_id 5-218234893 stop_sequence 1 doesn't have arrival or departure
- trip_id 5-369360908 stop_sequence 6 doesn't have arrival or departure
- trip_id 5-100794408 stop_sequence 4 doesn't have arrival or departure
VehiclePosition and TripUpdate ID pairing mismatch E047 3 erreurs
If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds.
Exemples d'erreurs
- trip_id 5-369360940 and vehicle_id 6875ed5a3e85cf2dc5901e99 pairing in VehiclePositions does not match trip_id 5-369164308 and vehicle_id 6875ed5a3e85cf2dc5901e99 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 5-184680516 and vehicle_id 684a670e6838e710a65c06a7 pairing in VehiclePositions does not match trip_id 5-184680461 and vehicle_id 684a670e6838e710a65c06a7 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 5-151126046 and vehicle_id 677d179d4e4a728f3128cfed pairing in VehiclePositions does not match trip_id 5-218234898 and vehicle_id 677d179d4e4a728f3128cfed pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
Avertissements
ID in one feed missing from the other W003 84 erreurs
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 5-100728841 is in TripUpdates but not in VehiclePositions feed
- trip_id 5-184614925 is in TripUpdates but not in VehiclePositions feed
- trip_id 5-218169395 is in TripUpdates but not in VehiclePositions feed
- trip_id 5-218169391 is in TripUpdates but not in VehiclePositions feed
- trip_id 5-100728836 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 |
|---|---|---|---|
| E043 | If a stop_time_update doesn't have a schedule_relationship of SKIPPED or NO_DATA, then either arrival or departure must be provided | 976 | 31 fois (100 % des validations) |
| E047 | If separate `VehiclePositions` and `TripUpdates` feeds are provided, `VehicleDescriptor` or `TripDescriptor` ID value pairing should match between the two feeds. | 137 | 31 fois (100 % 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 | 2 693 | 31 fois (100 % 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. | 44 | 21 fois (68 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 123 | 20 fois (65 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 2 | 1 fois (3 % des validations) |
Contenu du flux GTFS-RT
Impossible de décoder le flux GTFS-RT
Le flux GTFS-RT doit être accessible en HTTP, sans authentification et utiliser le format Protobuf.