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
❌65 erreurs, 93 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 04/12/2025 à 08h10 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
Sequential stop_time_update times are not increasing E022 16 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-369164310 stop_sequence 36 arrival_time 10:36:00 (1764830160) is less than previous stop arrival_time 10:44:58 (1764830698) - times must increase between two sequential stops
- trip_id 5-369164310 stop_sequence 36 arrival_time 10:36:00 (1764830160) is less than previous stop departure_time 10:44:58 (1764830698) - times must increase between two sequential stops
- trip_id 5-369164310 stop_sequence 36 departure_time 10:36:00 (1764830160) is less than previous stop departure_time 10:44:58 (1764830698) - times must increase between two sequential stops
- trip_id 5-369164310 stop_sequence 36 departure_time 10:36:00 (1764830160) is less than previous stop arrival_time 10:44:58 (1764830698) - times must increase between two sequential stops
- trip_id 5-369164304 stop_sequence 36 arrival_time 09:05:20 (1764824720) is less than previous stop arrival_time 09:08:13 (1764824893) - times must increase between two sequential stops
stop_time_update departure time is before arrival time E025 1 erreur
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 5-151060506 stop_sequence 1 departure_time 08:03:53 (1764821033) is less than the same stop arrival_time 08:06:04 (1764821164) - departure time must be equal to or greater than arrival time
stop_time_update doesn't have arrival or departure E043 46 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-369164310 stop_sequence 8 doesn't have arrival or departure
- trip_id 5-369164310 stop_sequence 31 doesn't have arrival or departure
- trip_id 5-470155285 stop_sequence 17 doesn't have arrival or departure
- trip_id 5-100794522 stop_sequence 4 doesn't have arrival or departure
- trip_id 5-100794522 stop_sequence 5 doesn't have arrival or departure
VehiclePosition and TripUpdate ID pairing mismatch E047 2 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-67240061 and vehicle_id 68c7c5c9724d514365e2a657 pairing in VehiclePositions does not match trip_id 5-67240041 and vehicle_id 68c7c5c9724d514365e2a657 pairing in TripUpdates feed and trip block_ids aren't the same - ID pairing between feeds should match
- trip_id 5-369360928 and vehicle_id 684a66a46edaa08f7ff91a7d pairing in VehiclePositions does not match trip_id 5-369164293 and vehicle_id 684a66a46edaa08f7ff91a7d 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 93 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-151060506 is in TripUpdates but not in VehiclePositions feed
- trip_id 5-470155294 is in TripUpdates but not in VehiclePositions feed
- trip_id 5-151060508 is in TripUpdates but not in VehiclePositions feed
- trip_id 5-336003130 is in TripUpdates but not in VehiclePositions feed
- trip_id 5-67240054 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 | 1 121 | 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. | 131 | 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 799 | 31 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. | 169 | 22 fois (71 % 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) |
| 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.