Détails de la ressource
La base de données multimodale présente de manière agrégée la position des véhicules des réseaux de transport public normands en temps réel.
Cette ressource fait partie du jeu de données Agrégat de réseaux urbains et interurbains de Normandie.
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
❌461 erreurs, 384 avertissements
Les shapes présentes dans le GTFS ont été ignorées, certaines règles de validation n'ont pas été vérifiées.
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 06/06/2025 à 09h09 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 3 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 zenbus:Vehicle:6336428100288512:LOC trip_id ATOUMOD036:ServiceJourney:6675665957945344x0:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:5087464869855232:LOC trip_id ATOUMOD036:ServiceJourney:4800034672476160x5:LOC does not exist in the GTFS data and does not have schedule_relationship of ADDED
- vehicle_id zenbus:Vehicle:5136714551001088:LOC trip_id ATOUMOD036:ServiceJourney:4800034672476160x4:LOC 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 1 erreur
All route_ids provided in the GTFS-rt feed must exist in the GTFS data
Exemples d'erreurs
- vehicle_id zenbus:Vehicle:6336428100288512:LOC route_id ATOUMOD036:Line:5425385643704320:LOC does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 30 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- vehicle_id 16 stop_id HOT01 does not exist in GTFS data stops.txt
- vehicle_id 26 stop_id BEL01 does not exist in GTFS data stops.txt
- vehicle_id 20 stop_id CHA01 does not exist in GTFS data stops.txt
- vehicle_id 6285181aee1b082d060d3f47 stop_id 15442 does not exist in GTFS data stops.txt
- vehicle_id 26 stop_id HOT01 does not exist in GTFS data stops.txt
trip direction_id does not match GTFS data E024 381 erreurs
GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt
Exemples d'erreurs
- GTFS-rt vehicle_id zenbus:Vehicle:756460055:LOC trip_id ATOUMOD105:ServiceJourney:5192777811886080x3:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
- GTFS-rt vehicle_id 424 trip_id ATOUMOD001:ServiceJourney:23840:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
- GTFS-rt vehicle_id 3138 trip_id ATOUMOD001:ServiceJourney:21137:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
- GTFS-rt vehicle_id 5512 trip_id ATOUMOD001:ServiceJourney:13580:LOC trip.direction_id is 2 but GTFS trip.direction_id is 1 - direction_id does not match
- GTFS-rt vehicle_id 5505 trip_id ATOUMOD001:ServiceJourney:13306:LOC trip.direction_id is 1 but GTFS trip.direction_id is 0 - direction_id does not match
Vehicle position outside agency coverage area E028 1 erreur
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 724 at (31.19826,-2.794428) is more than 1609.0 meters (1.00 mile(s)) outside entire GTFS stops.txt coverage area - vehicle should be within area
vehicle.id is not unique E052 45 erreurs
Each vehicle should have a unique ID
Exemples d'erreurs
- entity ID VM:ATOUMOD004:ServiceJourney:489412:LOC has vehicle.id 26 which is used by more than one vehicle in the feed
- entity ID VM:ATOUMOD001:ServiceJourney:1525:LOC has vehicle.id 6135 which is used by more than one vehicle in the feed
- entity ID VM:ATOUMOD001:ServiceJourney:7704:LOC has vehicle.id 6124 which is used by more than one vehicle in the feed
- entity ID VM:ATOUMOD001:ServiceJourney:2187:LOC has vehicle.id 7234 which is used by more than one vehicle in the feed
- entity ID VM:ATOUMOD019:ServiceJourney:13:LOC has vehicle.id 6285181aee1b082d060d3f47 which is used by more than one vehicle in the feed
Avertissements
schedule_relationship not populated W009 384 erreurs
trip.schedule_relationship and stop_time_update.schedule_relationship should be populated
Exemples d'erreurs
- trip_id ATOUMOD105:ServiceJourney:5192777811886080x3:LOC does not have a schedule_relationship
- trip_id ATOUMOD001:ServiceJourney:23840:LOC does not have a schedule_relationship
- trip_id ATOUMOD001:ServiceJourney:21137:LOC does not have a schedule_relationship
- trip_id ATOUMOD001:ServiceJourney:13580:LOC does not have a schedule_relationship
- trip_id ATOUMOD001:ServiceJourney:13306:LOC 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 |
|---|---|---|---|
| E024 | GTFS-rt trip direction_id must match the direction_id in GTFS trips.txt | 4 200 | 30 fois (100 % des validations) |
| W009 | trip.schedule_relationship and stop_time_update.schedule_relationship should be populated | 4 294 | 30 fois (100 % des validations) |
| E052 | Each vehicle should have a unique ID | 487 | 27 fois (90 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 532 | 20 fois (67 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 404 | 19 fois (63 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 91 | 15 fois (50 % des validations) |
| E035 | The GTFS-rt trip.trip_id should belong to the specified trip.route_id in GTFS trips.txt | 45 | 11 fois (37 % 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. | 3 | 3 fois (10 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 07/06/2025 à 02h31 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 07/06/2025 à 02h31 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"entity": [
{
"id": "VM:ATOUMOD007:ServiceJourney:3253:LOC",
"vehicle": {
"position": {
"latitude": 49.07865905761719,
"longitude": 1.5007940530776978
},
"timestamp": "1749240966",
"trip": {
"directionId": 2,
"routeId": "ATOUMOD007:Line:23:LOC",
"tripId": "ATOUMOD007:ServiceJourney:3253:LOC"
},
"vehicle": {
"id": "0200001002FD0748"
}
}
}
],
"header": {
"gtfsRealtimeVersion": "1.0",
"timestamp": "1749256307"
}
}