Jeu de données ouvert gtfs-rt - Offre TC temps réel STAR pour Réseau urbain Star

Détails de la ressource

Nom du fichier : Offre TC temps réel STAR

Format : gtfs-rt

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

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. En cas d'erreur 500, nous considèrerons que le flux est indisponible, sauf si il semble contenir du SOAP.

Rapport de validation

❌20 erreurs, 195 avertissements

Validation effectuée en utilisant le fichier GTFS en vigueur et le GTFS-RT, le 05/04/2025 à 09h11 Europe/Paris avec le validateur GTFS-RT de MobilityData.

Erreurs

stop_times_updates not strictly sorted E002 5 erreurs

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

Exemples d'erreurs

trip_id 1015 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 20] is not strictly sorted by increasing stop_sequence
trip_id 1058 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 12] is not strictly sorted by increasing stop_sequence
trip_id 1061 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 15, 16, 17, 18, 18] is not strictly sorted by increasing stop_sequence
trip_id 965 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 10, 11, 12, 13, 14, 14] is not strictly sorted by increasing stop_sequence
trip_id 966 stop_sequence [1, 2, 3, 4, 5, 6, 7, 8, 11, 12, 14, 16, 17, 18, 19, 20, 21, 22, 23, 24, 24] is not strictly sorted by increasing stop_sequence

Sequential stop_time_updates have the same stop_sequence E036 5 erreurs

Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence

Exemples d'erreurs

trip_id 1015 has repeating stop_sequence 20 - stop_sequence must increase for each stop_time_update
trip_id 1058 has repeating stop_sequence 12 - stop_sequence must increase for each stop_time_update
trip_id 1061 has repeating stop_sequence 18 - stop_sequence must increase for each stop_time_update
trip_id 965 has repeating stop_sequence 14 - stop_sequence must increase for each stop_time_update
trip_id 966 has repeating stop_sequence 24 - stop_sequence must increase for each stop_time_update

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 1015 has repeating stop_id HUBS at stop_sequence 20 - sequential stop_ids should be different
trip_id 1058 has repeating stop_id HUBN at stop_sequence 12 - sequential stop_ids should be different
trip_id 1061 has repeating stop_id HUBS at stop_sequence 18 - sequential stop_ids should be different
trip_id 965 has repeating stop_id HUBN at stop_sequence 14 - sequential stop_ids should be different
trip_id 966 has repeating stop_id HUBS at stop_sequence 24 - sequential stop_ids should be different

GTFS-rt stop_sequence not found in GTFS data E051 5 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 1015 contains stop_sequence 20 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 1058 contains stop_sequence 12 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 1061 contains stop_sequence 18 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 965 contains stop_sequence 14 that does not exist in GTFS stop_times.txt for this trip
GTFS-rt trip_id 966 contains stop_sequence 24 that does not exist in GTFS stop_times.txt for this trip

Avertissements

vehicle_id not populated W002 65 erreurs

vehicle_id should be populated for TripUpdates and VehiclePositions

Exemples d'erreurs

trip_id 1015 does not have a vehicle_id
trip_id 1016 does not have a vehicle_id
trip_id 1017 does not have a vehicle_id
trip_id 1018 does not have a vehicle_id
trip_id 1019 does not have a vehicle_id

schedule_relationship not populated W009 130 erreurs

trip.schedule_relationship and stop_time_update.schedule_relationship should be populated

Exemples d'erreurs

trip_id 1015 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 1015 does not have a schedule_relationship
trip_id 1016 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship
trip_id 1016 does not have a schedule_relationship
trip_id 1017 stop_sequence 1 (and potentially more for this trip) does not have a schedule_relationship

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
W002	vehicle_id should be populated for TripUpdates and VehiclePositions	1 933	27 fois (90 % des validations)
W009	trip.schedule_relationship and stop_time_update.schedule_relationship should be populated	3 866	27 fois (90 % des validations)
E002	stop_time_updates for a given trip_id must be strictly sorted by increasing stop_sequence	82	26 fois (87 % des validations)
E036	Sequential GTFS-rt trip stop_time_updates should never have the same stop_sequence	82	26 fois (87 % des validations)
E037	Sequential GTFS-rt trip stop_time_updates shouldn't have the same stop_id	82	26 fois (87 % des validations)
E051	All stop_time_update stop_sequences in GTFS-realtime data must appear in GTFS stop_times.txt for that trip	82	26 fois (87 % 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	279	19 fois (63 % des validations)

Contenu du flux GTFS-RT

Entités

Entités présentes dans ce flux le 06/04/2025 à 03h18 Europe/Paris.

vehicle_positions (0) service_alerts (0) trip_updates (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 06/04/2025 à 03h18 Europe/Paris. Vous pouvez consulter la documentation GTFS-RT.


{
  "header": {
    "gtfs_realtime_version": "1.0",
    "timestamp": "1743902307"
  }
}