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
❌600 erreurs, 7 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 31/01/2025 à 11h27 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 fe0cafba8bb5489af06e1e80b73083d4 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 dbf158a6b0f3d1525a49396261c7d6d0 does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id 016df8984625253eca2df987e44a407b does not exist in the GTFS data and does not have schedule_relationship of ADDED
- trip_id a58a4aa1903940c217fc076ff92a0328 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 7 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 219 does not exist in the GTFS data routes.txt
- route_id 219 does not exist in the GTFS data routes.txt
- route_id 221 does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 422 erreurs
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id fe0cafba8bb5489af06e1e80b73083d4 stop_id 2529 does not exist in GTFS data stops.txt
- trip_id fe0cafba8bb5489af06e1e80b73083d4 stop_id 2804 does not exist in GTFS data stops.txt
- trip_id fe0cafba8bb5489af06e1e80b73083d4 stop_id 2518 does not exist in GTFS data stops.txt
- trip_id fe0cafba8bb5489af06e1e80b73083d4 stop_id 2686 does not exist in GTFS data stops.txt
- trip_id fe0cafba8bb5489af06e1e80b73083d4 stop_id 2609 does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 164 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 fe0cafba8bb5489af06e1e80b73083d4 stop_sequence 26 arrival_time 09:09:01 (1738310941) is less than previous stop arrival_time 09:33:43 (1738312423) - times must increase between two sequential stops
- trip_id fe0cafba8bb5489af06e1e80b73083d4 stop_sequence 26 arrival_time 09:09:01 (1738310941) is less than previous stop departure_time 09:33:49 (1738312429) - times must increase between two sequential stops
- trip_id fe0cafba8bb5489af06e1e80b73083d4 stop_sequence 26 departure_time 09:10:09 (1738311009) is less than previous stop departure_time 09:33:49 (1738312429) - times must increase between two sequential stops
- trip_id fe0cafba8bb5489af06e1e80b73083d4 stop_sequence 26 departure_time 09:10:09 (1738311009) is less than previous stop arrival_time 09:33:43 (1738312423) - times must increase between two sequential stops
- trip_id fe0cafba8bb5489af06e1e80b73083d4 stop_sequence 60 arrival_time 08:16:18 (1738307778) is less than previous stop arrival_time 09:09:01 (1738310941) - 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 fe0cafba8bb5489af06e1e80b73083d4 does not have a timestamp
- trip_id fe0cafba8bb5489af06e1e80b73083d4 does not have a timestamp
- trip_id dbf158a6b0f3d1525a49396261c7d6d0 does not have a timestamp
- trip_id 016df8984625253eca2df987e44a407b does not have a timestamp
- trip_id a58a4aa1903940c217fc076ff92a0328 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 | 611 | 24 fois (89 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 611 | 24 fois (89 % des validations) |
| W001 | Timestamps should be populated for all elements | 611 | 24 fois (89 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 15 820 | 23 fois (85 % des validations) |
| E022 | stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease. | 27 522 | 23 fois (85 % des validations) |
| E025 | Within the same stop_time_update, arrival and departures times can be the same, or the departure time can be later than the arrival time - the departure time should never come before the arrival time. | 9 | 8 fois (30 % 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.