Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain Kicéo.
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
❌46 erreurs, 5 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 31/03/2025 à 09h13 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 168 trip_id TRIPID-12069 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 232 trip_id 0807 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 229 trip_id 0804 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 244 trip_id ANVAN.19421 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 347 trip_id 404 does not exist in the GTFS data and does not have schedule_relationship of ADDED
GTFS-rt route_id does not exist in GTFS data E004 14 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- vehicle_id 168 route_id MOBICEO does not exist in the GTFS data routes.txt
- vehicle_id 232 route_id SAEIV.26 does not exist in the GTFS data routes.txt
- vehicle_id 229 route_id SAEIV.26 does not exist in the GTFS data routes.txt
- vehicle_id 244 route_id bre_vannes_2024_2025.1612195510832 does not exist in the GTFS data routes.txt
- vehicle_id 347 route_id SAEIVTEO.47 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 14 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- vehicle_id 168 stop_id STP-ARRIVEE does not exist in GTFS data stops.txt
- vehicle_id 232 stop_id SAEIV.50 does not exist in GTFS data stops.txt
- vehicle_id 229 stop_id SP199031 does not exist in GTFS data stops.txt
- vehicle_id 244 stop_id bre_vannes_2024_2025.19437 does not exist in GTFS data stops.txt
- vehicle_id 347 stop_id SP291499 does not exist in GTFS data stops.txt
Vehicle position outside agency coverage area E028 4 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 347 at (47.766853,-2.494977) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 307 at (47.926983,-2.384854) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 248 at (47.846592,-2.700413) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
- vehicle.id 179 at (47.693123,-2.394372) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS shapes.txt coverage area - vehicle should be within area
Avertissements
timestamp not populated W001 5 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- vehicle_id 50 does not have a timestamp
- vehicle_id 42 does not have a timestamp
- vehicle_id 21 does not have a timestamp
- vehicle_id 63 does not have a timestamp
- vehicle_id 25 does not have a timestamp
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 | 1 215 | 20 fois (83 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 1 168 | 20 fois (83 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 1 127 | 20 fois (83 % des validations) |
| W001 | Timestamps should be populated for all elements | 156 | 20 fois (83 % 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. | 95 | 19 fois (79 % des validations) |
| E015 | All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt | 34 | 13 fois (54 % des validations) |
| W004 | vehicle.position.speed has an unrealistic speed that may be incorrect | 13 | 10 fois (42 % 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. | 11 | 7 fois (29 % des validations) |
| E052 | Each vehicle should have a unique ID | 4 | 4 fois (17 % des validations) |
| E023 | For normal scheduled trips (i.e., not defined in frequencies.txt), the GTFS-realtime trip start_time must match the first GTFS arrival_time in stop_times.txt for this trip | 5 | 1 fois (4 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 01/04/2025 à 01h57 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (0)Entités présentes dans ce flux lors des 7 derniers jours.
vehicle_positionsFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 01/04/2025 à 01h57 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1743465462"
}
}