Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain Nemus.
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
❌2 083 erreurs, 7 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 21/11/2024 à 08h13 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 7 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
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 985a852ef3d4e461d72c3334528f962c does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id fe0cafba8bb5489af06e1e80b73083d4 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id f1bf7b75e8ac90ed19ea49dfc5199011 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id dbaa522c1c45abd762e8f7048af34a81 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
- route_id 248 does not exist in the GTFS data routes.txt
- route_id 248 does not exist in the GTFS data routes.txt
- route_id 248 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 633 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_id 2529 does not exist in GTFS data stops.txt
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_id 2804 does not exist in GTFS data stops.txt
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_id 2518 does not exist in GTFS data stops.txt
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_id 2686 does not exist in GTFS data stops.txt
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_id 2609 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 1 440 erreurs
stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.
Exemples d'erreurs
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_sequence 95 arrival_time 07:24:42 (1732170282) is less than previous stop arrival_time 07:52:19 (1732171939) - times must increase between two sequential stops
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_sequence 95 arrival_time 07:24:42 (1732170282) is less than previous stop departure_time 07:52:43 (1732171963) - times must increase between two sequential stops
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_sequence 95 departure_time 07:24:51 (1732170291) is less than previous stop departure_time 07:52:43 (1732171963) - times must increase between two sequential stops
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_sequence 95 departure_time 07:24:51 (1732170291) is less than previous stop arrival_time 07:52:19 (1732171939) - times must increase between two sequential stops
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 stop_sequence 167 arrival_time 07:56:08 (1732172168) is less than previous stop arrival_time 08:07:46 (1732172866) - times must increase between two sequential stops
Avertissements
timestamp not populated W001 7 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 4e637fdf2204bad094066faa2c3c0cc7 does not have a timestamp
- trip_id 985a852ef3d4e461d72c3334528f962c does not have a timestamp
- trip_id fe0cafba8bb5489af06e1e80b73083d4 does not have a timestamp
- trip_id f1bf7b75e8ac90ed19ea49dfc5199011 does not have a timestamp
- trip_id dbaa522c1c45abd762e8f7048af34a81 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 | 21 | 3 fois (100 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 7 | 3 fois (100 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 1 477 | 3 fois (100 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 2 576 | 3 fois (100 % des validations) |
| W001 | Timestamps should be populated for all elements | 21 | 3 fois (100 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 21/11/2024 à 17h41 Europe/Paris.
service_alerts (0) trip_updates (0) vehicle_positions (0)Entités présentes dans ce flux lors des 7 derniers jours.
trip_updatesFlux GTFS-RT décodé
Voir le contenu du flux
Voici le flux GTFS-RT décodé au format Protobuf le 21/11/2024 à 17h41 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1732207315"
}
}