Détails de la ressource
Données en temps réel du réseau interurbain Région Centre Val de Loire REMI - vehicule-positions
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
❌24 erreurs, 51 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 23/10/2026 à 09h06 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 14 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
- vehicle_id GF 878 XR trip_id REMI45:VehicleJouney:2-537198614 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id HB 615 SQ trip_id REMI45:VehicleJouney:2-1728839847 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id EF-483-ZZ trip_id REMI45:VehicleJouney:2-621019197 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id FR 172 RX trip_id REMI45:VehicleJouney:2-538116104 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id DF-554-CK trip_id REMI45:VehicleJouney:2-9730850841 does not exist in the GTFS data and does not have schedule_relationship of ADDED
Not in POSIX time E001 2 erreurs
All timestamps must be in POSIX time (i.e., number of seconds since January 1st 1970 00:00:00 UTC)
Exemples d'erreurs
- vehicle_id HB 615 SQ timestamp 1792738551882 is not POSIX time
- vehicle_id HE-394-XD timestamp 1792739089792 is not POSIX time
Header timestamp should be greater than or equal to all other timestamps E012 2 erreurs
No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp
Exemples d'erreurs
- vehicle_id HB 615 SQ timestamp 1792738551882 is greater than the header
- vehicle_id HE-394-XD timestamp 1792739089792 is greater than the header
Vehicle position outside agency coverage area E028 2 erreurs
The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt.
Exemples d'erreurs
- vehicle.id HB 615 SQ at (0.0,0.0) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id HE-394-XD at (0.0,0.0) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
Vehicle position far from trip shape E029 2 erreurs
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.
Exemples d'erreurs
- vehicle.id GH-890-RV trip_id REMI28:VehicleJourney:3-238092289 at (48.44971,1.4813783) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
- vehicle.id HE-694-NJ trip_id REMI36:VehicleJourney:berry_sti_16000066 at (46.941093,1.973925) is more than 200.0 meters (0.12 mile(s)) from the GTFS trip shape - vehicle should be near trip shape or on DETOUR
GTFS-rt trip.trip_id does not belong to GTFS-rt trip.route_id in GTFS trips.txt E035 2 erreurs
The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt
Exemples d'erreurs
- GTFS-rt entity ID FC-353-GG trip_id REMI_18:VehicleJourney:berry_sti_16000381 has route_id REMI_18:Line:110 but belongs to GTFS route_id REMI_18:Line:150 in GTFS trips.txt
- GTFS-rt entity ID HE-694-NJ trip_id REMI36:VehicleJourney:berry_sti_16000066 has route_id REMI36:Line:V but belongs to GTFS route_id REMI36:Line:A in GTFS trips.txt
Avertissements
schedule_relationship not populated W009 51 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id REMI28:VehicleJourney:3-238092289 does not have a schedule_relationship
- trip_id REMI28:VehicleJourney:3-723189762 does not have a schedule_relationship
- trip_id REMI28:VehicleJourney:3-1494745090 does not have a schedule_relationship
- trip_id REMI28:VehicleJourney:3-1495007236 does not have a schedule_relationship
- trip_id REMI28:VehicleJourney:3-3527802882 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 |
|---|---|---|---|
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 485 | 30 fois (100 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 1 790 | 30 fois (100 % 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. | 90 | 26 fois (87 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 321 | 13 fois (43 % des validations) |
| E027 | Vehicle bearing must be between 0 and 360 degrees (inclusive) | 191 | 10 fois (33 % des validations) |
| E035 | The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt | 15 | 7 fois (23 % des validations) |
| E001 | All timestamps must be in POSIX time (i.e., number of seconds since January 1st 1970 00:00:00 UTC) | 4 | 3 fois (10 % des validations) |
| E012 | No timestamps for individual entities (TripUpdate, VehiclePosition) in the feeds should be greater than the header timestamp | 4 | 3 fois (10 % des validations) |
| E028 | The vehicle position should be inside the agency coverage area. This is defined as within roughly 1/8 of a mile (200 meters) of the GTFS shapes.txt data, or stops.txt locations if the GTFS feed doesn't include shapes.txt. | 4 | 3 fois (10 % 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.