Jeu de données ouvert gtfs-rt - GTFS-RT TripUpdate Marinéo Boulogne pour Réseau urbain Marinéo

Détails de la ressource

Nom du fichier : GTFS-RT TripUpdate Marinéo Boulogne

Format : gtfs-rt

Cette ressource fait partie du jeu de données Réseau urbain Marinéo.

Disponibilité au téléchargement

Nous testons la disponibilité de cette ressource au téléchargement toutes les heures, en effectuant une requête HTTP de type 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.

Rapport de validation

❌257 erreurs, 103 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 07/09/2024 à 09h02 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

stop_times_updates not strictly sorted E002 25 erreurs

stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence

Exemples d'erreurs

trip_id 20477583 stop_sequence [17, 1] is not strictly sorted by increasing stop_sequence
trip_id 20477582 stop_sequence [22, 1] is not strictly sorted by increasing stop_sequence
trip_id 20477581 stop_sequence [17, 1] is not strictly sorted by increasing stop_sequence
trip_id 20477580 stop_sequence [17, 1] is not strictly sorted by increasing stop_sequence
trip_id 20477579 stop_sequence [13, 1] is not strictly sorted by increasing stop_sequence

GTFS-rt stop_sequence isn't provided for trip that visits same stop_id more than once E009 2 erreurs

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

Exemples d'erreurs

trip_id 20472983 visits stop_id [bsmdal1] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided
trip_id 20472984 visits stop_id [bsmdal1] more than once and GTFS-rt stop_time_update is missing stop_sequence field - stop_sequence must be provided

GTFS-rt stop_id does not exist in GTFS data E011 5 erreurs

All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt

Exemples d'erreurs

trip_id 20477348 stop_id bsmuniv does not exist in GTFS data stops.txt
trip_id 20477346 stop_id bsmuniv does not exist in GTFS data stops.txt
trip_id 20477532 stop_id bsmuniv does not exist in GTFS data stops.txt
trip_id 20477531 stop_id bsmuniv does not exist in GTFS data stops.txt
trip_id 20477530 stop_id bsmuniv does not exist in GTFS data stops.txt

Sequential stop_time_update times are not increasing E022 204 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 20477677 stop_sequence 4 arrival_time 09:55:48 (1725695748) is less than previous stop arrival_time 09:56:21 (1725695781) - times must increase between two sequential stops
trip_id 20477677 stop_sequence 4 arrival_time 09:55:48 (1725695748) is less than previous stop departure_time 09:56:21 (1725695781) - times must increase between two sequential stops
trip_id 20477677 stop_sequence 4 departure_time 09:55:48 (1725695748) is less than previous stop departure_time 09:56:21 (1725695781) - times must increase between two sequential stops
trip_id 20477677 stop_sequence 4 departure_time 09:55:48 (1725695748) is less than previous stop arrival_time 09:56:21 (1725695781) - times must increase between two sequential stops
trip_id 20477676 stop_sequence 4 arrival_time 09:13:48 (1725693228) is less than previous stop arrival_time 09:14:21 (1725693261) - times must increase between two sequential stops

Sequential stop_time_updates have the same stop_id E037 5 erreurs

Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id

Exemples d'erreurs

trip_id 20477348 has repeating stop_id bsmieu - sequential stop_ids should be different
trip_id 20477346 has repeating stop_id bsmieu - sequential stop_ids should be different
trip_id 20477532 has repeating stop_id bsmieu - sequential stop_ids should be different
trip_id 20477531 has repeating stop_id bsmieu - sequential stop_ids should be different
trip_id 20477530 has repeating stop_id bsmieu - sequential stop_ids should be different

GTFS-rt stop_sequence not found in GTFS data E051 16 erreurs

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 20477583 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 20477582 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 20477581 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 20477580 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 20477579 contains stop_sequence 1 that does not exist in GTFS stop_times.txt for this trip

Avertissements

timestamp not populated W001 67 erreurs

Timestamps should be populated for all elements

Exemples d'erreurs

trip_id 20575983 does not have a timestamp
trip_id 20477677 does not have a timestamp
trip_id 20477676 does not have a timestamp
trip_id 20477675 does not have a timestamp
trip_id 20576036 does not have a timestamp

vehicle_id not populated W002 36 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id 20477677 does not have a vehicle_id
trip_id 20477676 does not have a vehicle_id
trip_id 20576036 does not have a vehicle_id
trip_id 20575991 does not have a vehicle_id
trip_id 20575985 does not have a vehicle_id

Valider ce GTFS-RT maintenant

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
E022	stop_time_update arrival/departure times between sequential stops should always increase - they should never be the same or decrease.	2 624	30 fois (100 % des validations)
W001	Timestamps should be populated for all elements	1 727	30 fois (100 % des validations)
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	1 018	30 fois (100 % des validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	225	29 fois (97 % des validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	103	28 fois (93 % des validations)
E011	All stop_ids referenced in GTFS-rt feeds must exist in GTFS stops.txt	255	23 fois (77 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	101	22 fois (73 % 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	18	8 fois (27 % 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.	3	3 fois (10 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 08/09/2024 à 02h19 Europe/Paris.

service_alerts (0) trip_updates (0) vehicle_positions (0)

Entités présentes dans ce flux lors des 7 derniers jours.

trip_updates

Flux GTFS-RT décodé

Voir le contenu du flux

Voici le flux GTFS-RT décodé au format Protobuf le 08/09/2024 à 02h19 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


{
  "header": {
    "gtfs_realtime_version": "2.0",
    "timestamp": "1725754757"
  }
}