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
❌14 erreurs, 5 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 23/11/2024 à 08h03 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 6 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 267 trip_id 2-234946563 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 247 trip_id 1102 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 179 trip_id 0903 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 268 trip_id 2-235012102 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id 164 trip_id TRIPID-2794 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 3 erreurs
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- vehicle_id 247 route_id SAEIVGESTC.259 does not exist in the GTFS data routes.txt
- vehicle_id 179 route_id SAEIVGESTC.335 does not exist in the GTFS data routes.txt
- vehicle_id 164 route_id TAD does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 3 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- vehicle_id 247 stop_id SAEIVGESTC.251 does not exist in GTFS data stops.txt
- vehicle_id 179 stop_id SAEIVGESTC.462 does not exist in GTFS data stops.txt
- vehicle_id 164 stop_id STP-DEPART does not exist in GTFS data stops.txt
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 247 at (47.844715,-2.71136) 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.68882,-2.533131) 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 55 does not have a timestamp
- vehicle_id 40 does not have a timestamp
- vehicle_id 83 does not have a timestamp
- vehicle_id 52 does not have a timestamp
- vehicle_id 81 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 | 129 | 2 fois (100 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 98 | 2 fois (100 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 96 | 2 fois (100 % 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. | 6 | 2 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 8 | 2 fois (100 % des validations) |
| E015 | All stop_ids referenced in GTFS-rt TripUpdates and VehiclePositions feeds must have the location_type = 0 in GTFS stops.txt | 2 | 1 fois (50 % 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. | 3 | 1 fois (50 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 23/11/2024 à 22h10 Europe/Paris.
vehicle_positions (1) service_alerts (0) trip_updates (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 23/11/2024 à 22h10 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"entity": [
{
"id": "185928",
"vehicle": {
"current_status": "IN_TRANSIT_TO",
"current_stop_sequence": 2,
"position": {
"bearing": 290.0,
"latitude": 47.74091720581055,
"longitude": -2.6792449951171875,
"speed": 1.9444444179534912
},
"stop_id": "STP-ARRIVEE",
"timestamp": "1732365537",
"trip": {
"route_id": "TAD",
"schedule_relationship": "UNSCHEDULED",
"start_date": "20241123",
"start_time": "10:00:00",
"trip_id": "TRIPID-2794"
},
"vehicle": {
"id": "367",
"label": "GX-680-NR",
"license_plate": "GX-680-NR"
}
}
}
],
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1732396234"
}
}