Détails de la ressource
Données en temps réel du réseau interurbain Région Centre Val de Loire REMI - trip-updates
Cette ressource fait partie du jeu de données Réseau interurbain Rémi.
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
❌175 erreurs, 114 avertissements
De nombreuses erreurs de validation indiquent que les identifiants du GTFS-RT ne correspondent pas aux identifiants du GTFS.
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 03/09/2026 à 09h07 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
GTFS-rt route_id does not exist in GTFS data E004 74 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- route_id REMI41:FlexibleLine:5 does not exist in the GTFS data routes.txt
- route_id REMI41:FlexibleLine:3 does not exist in the GTFS data routes.txt
- route_id REMI41:FlexibleLine:3 does not exist in the GTFS data routes.txt
- route_id REMI41:FlexibleLine:16 does not exist in the GTFS data routes.txt
- route_id REMI41:FlexibleLine:5 does not exist in the GTFS data routes.txt
stop_time_update doesn't have arrival or departure E043 26 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 REMI41:VehicleJourney:1-81854465 stop_sequence 9 doesn't have arrival or departure
- trip_id REMI41:VehicleJourney:1-54984705 stop_sequence 0 doesn't have arrival or departure
- trip_id REMI41:VehicleJourney:1-50855937 stop_sequence 12 doesn't have arrival or departure
- trip_id REMI41:VehicleJourney:1-23855105 stop_sequence 16 doesn't have arrival or departure
- trip_id REMI41:VehicleJourney:1-7232028676 stop_sequence 17 doesn't have arrival or departure
GTFS-rt stop_time_update stop_sequence and stop_id do not match GTFS E045 17 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 REMI37:VehicleJourney:5-5088018434 stop_sequence 2 has stop_id REMI37:Quay:4103 but GTFS stop_sequence 2 has stop_id REMI37:Quay:4104 - stop_ids should be the same
- GTFS-rt trip_id REMI37:VehicleJourney:5-5088018434 stop_sequence 3 has stop_id REMI37:Quay:4104 but GTFS stop_sequence 3 has stop_id REMI37:Quay:3801 - stop_ids should be the same
- GTFS-rt trip_id REMI37:VehicleJourney:5-5088018434 stop_sequence 4 has stop_id REMI37:Quay:3801 but GTFS stop_sequence 4 has stop_id REMI37:Quay:3731 - stop_ids should be the same
- GTFS-rt trip_id REMI37:VehicleJourney:5-5088018434 stop_sequence 5 has stop_id REMI37:Quay:3731 but GTFS stop_sequence 5 has stop_id REMI37:Quay:3705 - stop_ids should be the same
- GTFS-rt trip_id REMI37:VehicleJourney:5-5088018434 stop_sequence 6 has stop_id REMI37:Quay:3705 but GTFS stop_sequence 6 has stop_id REMI37:Quay:3710 - stop_ids should be the same
GTFS-rt stop_sequence not found in GTFS data E051 58 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 REMI41:VehicleJourney:1-81854465 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id REMI41:VehicleJourney:1-7232159745 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id REMI41:VehicleJourney:1-7232028676 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id REMI41:VehicleJourney:1-50855937 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
- GTFS-rt trip_id REMI41:VehicleJourney:1-54984705 contains stop_sequence 0 that does not exist in GTFS stop_times.txt for this trip
Avertissements
timestamp not populated W001 57 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id REMI41:VehicleJourney:1-81854465 does not have a timestamp
- trip_id REMI41:VehicleJourney:1-7232159745 does not have a timestamp
- trip_id REMI41:VehicleJourney:1-7232028676 does not have a timestamp
- trip_id REMI41:VehicleJourney:1-50855937 does not have a timestamp
- trip_id REMI41:VehicleJourney:1-54984705 does not have a timestamp
schedule_relationship not populated W009 57 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id REMI41:VehicleJourney:1-81854465 does not have a schedule_relationship
- trip_id REMI41:VehicleJourney:1-7232159745 does not have a schedule_relationship
- trip_id REMI41:VehicleJourney:1-7232028676 does not have a schedule_relationship
- trip_id REMI41:VehicleJourney:1-50855937 does not have a schedule_relationship
- trip_id REMI41:VehicleJourney:1-54984705 does not have a schedule_relationship
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 |
|---|---|---|---|
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 74 | 1 fois (100 % des validations) |
| 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 | 26 | 1 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 | 17 | 1 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 | 58 | 1 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 57 | 1 fois (100 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 57 | 1 fois (100 % 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.