Détails de la ressource
Cette ressource fait partie du jeu de données Réseau urbain Mariné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
❌92 erreurs, 126 avertissements
Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 30/01/2025 à 08h11 Europe/Paris avec le validateur GTFS-RT de MobilityData.
Erreurs
stop_times_updates not strictly sorted E002 4 erreurs
stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence
Exemples d'erreurs
- trip_id 20473212 stop_sequence [2, 1] is not strictly sorted by increasing stop_sequence
- trip_id 20473140 stop_sequence [4, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11] is not strictly sorted by increasing stop_sequence
- trip_id 20472718 stop_sequence [7, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25] is not strictly sorted by increasing stop_sequence
- trip_id 20472720 stop_sequence [7, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25] is not strictly sorted by increasing stop_sequence
GTFS-rt trip_id does not exist in GTFS data and does not have schedule_relationship of ADDED E003 1 erreur
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 20473026 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
- route_id SC does not exist in the GTFS data routes.txt
GTFS-rt stop_id does not exist in GTFS data E011 1 erreur
All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt
Exemples d'erreurs
- trip_id 20473026 stop_id smbsand does not exist in GTFS data stops.txt
Sequential stop_time_update times are not increasing E022 78 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 20472866 stop_sequence 1 departure_time 08:07:00 (1738220820) is less than previous stop departure_time 08:12:16 (1738221136) - times must increase between two sequential stops
- trip_id 20472866 stop_sequence 1 departure_time 08:07:00 (1738220820) is less than previous stop arrival_time 08:12:16 (1738221136) - times must increase between two sequential stops
- trip_id 20472866 stop_sequence 2 arrival_time 08:08:32 (1738220912) is less than previous stop arrival_time 08:12:16 (1738221136) - times must increase between two sequential stops
- trip_id 20472866 stop_sequence 2 departure_time 08:08:32 (1738220912) is less than previous stop arrival_time 08:12:16 (1738221136) - times must increase between two sequential stops
- trip_id 20472865 stop_sequence 1 departure_time 07:26:00 (1738218360) is less than previous stop departure_time 07:31:39 (1738218699) - times must increase between two sequential stops
Sequential stop_time_updates have the same stop_id E037 6 erreurs
Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id
Exemples d'erreurs
- trip_id 20472874 has repeating stop_id wimmair2 - sequential stop_ids should be different
- trip_id 20472886 has repeating stop_id wimsncf - sequential stop_ids should be different
- trip_id 20472889 has repeating stop_id wimsncf - sequential stop_ids should be different
- trip_id 20472888 has repeating stop_id wimsncf - sequential stop_ids should be different
- trip_id 20472718 has repeating stop_id outlep2 - sequential stop_ids should be different
GTFS-rt stop_sequence not found in GTFS data E051 1 erreur
All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip
Exemples d'erreurs
- GTFS-rt trip_id 20473212 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
Avertissements
timestamp not populated W001 83 erreurs
Timestamps should be populated for all elements
Exemples d'erreurs
- trip_id 20472834 does not have a timestamp
- trip_id 20472833 does not have a timestamp
- trip_id 20472832 does not have a timestamp
- trip_id 20472853 does not have a timestamp
- trip_id 20472852 does not have a timestamp
vehicle_id not populated W002 43 erreurs
vehicle_id should be populated for TripUpdates and VehiclePositions
Exemples d'erreurs
- trip_id 20472834 does not have a vehicle_id
- trip_id 20472833 does not have a vehicle_id
- trip_id 20472853 does not have a vehicle_id
- trip_id 20472874 does not have a vehicle_id
- trip_id 20472887 does not have a vehicle_id
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 |
|---|---|---|---|
| W001 | Timestamps should be populated for all elements | 1 907 | 30 fois (100 % des validations) |
| W002 | vehicle_id should be populated for TripUpdates and VehiclePositions | 1 061 | 30 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. | 1 598 | 27 fois (90 % des validations) |
| E002 | stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence | 99 | 25 fois (83 % des validations) |
| E037 | Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id | 96 | 25 fois (83 % des validations) |
| E051 | All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip | 18 | 18 fois (60 % des validations) |
| E045 | If GTFS-rt stop_time_update contains both stop_sequence and stop_id, the values must match the GTFS data in stop_times.txt | 28 | 15 fois (50 % des validations) |
| E003 | All trip_ids provided in the GTFS-rt feed must exist in the GTFS data, unless the schedule_relationship is ADDED | 13 | 13 fois (43 % des validations) |
| E004 | All route_ids provided in the GTFS-rt feed must exist in the GTFS data | 13 | 13 fois (43 % des validations) |
| E009 | If a GTFS trip contains multiple references to the same stop_id (i.e., the vehicle visits the same stop_id more than once in the same trip), then GTFS-rt stop_time_updates for this trip must include stop_sequence | 9 | 9 fois (30 % des validations) |
| E011 | All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt | 8 | 8 fois (27 % des validations) |
Contenu du flux GTFS-RT
Entités
Entités présentes dans ce flux le 31/01/2025 à 00h25 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 31/01/2025 à 00h25 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.
{
"header": {
"gtfs_realtime_version": "2.0",
"timestamp": "1738279503"
}
}