Commencer

Estimation de la vitesse avec Ultralytics YOLO26

Qu’est-ce que l’estimation de la vitesse ?#

L’estimation de la vitesse consiste à calculer la vitesse de déplacement d’un objet dans un contexte donné. Elle est souvent utilisée dans des applications de vision par ordinateur. Avec Ultralytics YOLO26, tu peux calculer la vitesse des objets en combinant le suivi d’objets avec des données de distance et de temps. Cette fonctionnalité est utile pour des tâches comme la surveillance du trafic et la vidéosurveillance.



Regarder : Estimation de la vitesse avec Ultralytics YOLO26

Avantages de l’estimation de la vitesse#

  • Gestion efficace du trafic : Une estimation précise de la vitesse aide à gérer la circulation, à renforcer la sécurité et à réduire les embouteillages.
  • Navigation autonome précise : Dans les systèmes autonomes comme les voitures autonomes, une estimation fiable de la vitesse garantit une navigation sûre et précise.
  • Sécurité renforcée de la vidéosurveillance : L’estimation de la vitesse dans les systèmes d’analyse vidéo aide à repérer les comportements inhabituels ou les menaces potentielles, améliorant ainsi l’efficacité des mesures de sécurité.

Applications concrètes#

TransportTransport
Estimation de la vitesse sur une route avec Ultralytics YOLO26Estimation de la vitesse sur un pont avec Ultralytics YOLO26
Estimation de la vitesse sur une route avec Ultralytics YOLO26Estimation de la vitesse sur un pont avec Ultralytics YOLO26
La vitesse est une estimation

La vitesse est estimée et les résultats peuvent manquer de précision. Ils varient également en fonction des caractéristiques de la caméra et d’autres facteurs connexes.

Estimer la vitesse avec YOLO26#

La solution SpeedEstimator suit chaque objet d’une image à l’autre et convertit son déplacement en pixels en vitesse à l’aide de la fréquence d’images de la vidéo (fps) et d’une échelle réelle (meter_per_pixel). Ajuste meter_per_pixel à la configuration de ta caméra et utilise max_speed pour limiter les valeurs aberrantes dues au bruit dans les trajectoires.

Estimation de la vitesse avec Ultralytics YOLO
# Run a speed example
yolo solutions speed show=True

# Pass a source video
yolo solutions speed source="path/to/video.mp4"

# Adjust meter per pixel value based on camera configuration
yolo solutions speed meter_per_pixel=0.05

Arguments de SpeedEstimator#

Voici un tableau des arguments de SpeedEstimator :

ArgumentTypeValeur par défautDescription
modelstrNoneChemin vers un fichier de modèle Ultralytics YOLO.
fpsfloat30.0Images par seconde utilisées pour les calculs de vitesse.
max_histint5Nombre maximal de points historiques à suivre par objet pour les calculs de vitesse et de direction.
meter_per_pixelfloat0.05Facteur d’échelle utilisé pour convertir les distances en pixels en unités du monde réel.
max_speedint120Vitesse maximale en km/h ; les vitesses estimées supérieures sont plafonnées à cette valeur.
line_widthint2Épaisseur des lignes des boîtes, des points clés et des compteurs dessinés par la solution.
verboseboolTrueActive le journal de la solution pour chaque image, qui indique la forme de l'entrée, le nombre d'éléments par classe et la vitesse de traitement. L'appel de suivi reste toujours silencieux.

La solution SpeedEstimator permet d’utiliser les paramètres track :

ArgumentTypeValeur par défautDescription
trackerstr'tracktrack.yaml'Indique l'algorithme de suivi à utiliser. Options intégrées : botsort.yaml, bytetrack.yaml, ocsort.yaml, deepocsort.yaml, fasttrack.yaml, tracktrack.yaml.
conffloat0.25Définit le seuil de confiance des détections ; des valeurs plus faibles permettent de suivre davantage d'objets, mais peuvent inclure des faux positifs.
ioufloat0.5Définit le seuil d'intersection sur l'union (IoU) utilisé pour filtrer les détections qui se chevauchent.
classeslistNoneFiltre les résultats selon l'indice de classe. Par exemple, classes=[0, 2, 3] ne suit que les classes spécifiées.
devicestrNoneIndique le périphérique utilisé pour l'inférence (par exemple, cpu, cuda:0 ou 0). Permet de choisir entre le CPU, un GPU spécifique ou d'autres périphériques de calcul pour l'exécution du modèle.
imgszint or tuple640Taille cible de l'image pour l'inférence : un entier pour une image carrée ou une paire (height, width). Les dimensions sont ajustées au stride du modèle.
max_detint300Nombre maximal de détections conservées par image avant le suivi, ce qui limite le nombre d'objets qu'une solution traite dans les scènes denses.
quantizeint or strNonePrécision d’inférence : 16 (FP16) ou 32/unset (FP32) pour les modèles PyTorch et TorchScript hors CPU ; les autres formats utilisent la précision définie par leur artefact et leur environnement d’exécution. Remplace l’argument half obsolète.

Les options de visualisation suivantes sont également prises en charge :

ArgumentTypeValeur par défautDescription
showboolFalseSi True, affiche les images ou vidéos annotées dans une fenêtre. Utile pour obtenir un retour visuel immédiat pendant le développement ou les tests.
show_labelsboolTrueAffiche les étiquettes de chaque détection dans le résultat visuel. Permet d'identifier immédiatement les objets détectés.

FAQ#

  • L’estimation de la vitesse des objets avec Ultralytics YOLO26 combine la détection d’objets et le suivi. Le modèle détecte les objets dans chaque image, les suit d’une image à l’autre, puis convertit la distance parcourue entre les images en vitesse à l’aide de la fréquence d’images et de l’échelle meter_per_pixel. L’exemple Python ci-dessus exécute l’ensemble de ce processus : indique ta vidéo et ajuste meter_per_pixel en fonction de ta caméra. Pour en savoir plus, consulte notre article de blog officiel.

  • L’utilisation d’Ultralytics YOLO26 pour estimer la vitesse offre des avantages considérables pour la gestion du trafic :

    • Sécurité renforcée : Estime avec précision la vitesse des véhicules pour détecter les excès de vitesse et améliorer la sécurité routière.
    • Surveillance en temps réel : Profite de la capacité de détection d’objets en temps réel de YOLO26 pour surveiller efficacement la circulation et les embouteillages.
    • Évolutivité : Déploie le modèle sur différentes configurations matérielles, des appareils en périphérie aux serveurs, pour créer des solutions flexibles et évolutives adaptées aux déploiements à grande échelle.

    Pour découvrir d’autres applications, consulte les avantages de l’estimation de la vitesse.

  • Oui. YOLO26 repose sur PyTorch, et Ultralytics permet d’exporter les modèles YOLO26 dans des formats comme ONNX, TensorRT, CoreML et SavedModel de TensorFlow, pour assurer leur interopérabilité avec d’autres frameworks de ML.

    Pour exporter un modèle YOLO26 au format ONNX :

    yolo export model=yolo26n.pt format=onnx

    Pour en savoir plus sur l’exportation de modèles, consulte notre guide sur l’exportation.

  • La précision de l’estimation de la vitesse avec Ultralytics YOLO26 dépend de plusieurs facteurs, notamment de la qualité du suivi d’objets, de la résolution et de la fréquence d’images de la vidéo, ainsi que des variables environnementales. L’estimateur de vitesse fournit des estimations fiables, mais celles-ci peuvent ne pas être exactes à 100 % en raison des variations de la vitesse de traitement des images et de l’occultation des objets.

    Remarque : tiens toujours compte de la marge d’erreur et, si possible, valide les estimations à l’aide de données de référence.

Commentaires109

Pose une question, partage tes résultats ou aide quelqu’un d’autre.

  1. zwxdlutGitHub

    For estimating the speed of passing through a region, I set the "region" parameter while initializing the speed estimator , as follow:

    region_points = [(20, int(h / 2)), (w - 20, int(h / 2))]                      # line points
    # Initialize speed estimation object
    speedestimator = solutions.SpeedEstimator(
        show=True,  # display the output
        model="runs/detect/train/weights/best.pt",  # path to the model file
        fps=fps,  # adjust speed based on frame per second
        # max_speed=120,  # cap speed to a max value (km/h) to avoid outliers
        # max_hist=5,  # minimum frames object tracked before computing speed
        # meter_per_pixel=0.05,  # highly depends on the camera configuration
        classes=[3, 4, 5],  # estimate speed of specific classes.
        # line_width=2,  # adjust the line width for bounding boxes
        region=region_points,
    )
    ```python
    
    The model was customized trained with the VisDrone dataset.
    The speed estimator estimates each object speed whether it is within the region or not. The parameter "region" doesn't take effect at all.
    
    Has the function "estimating speed in regions" not been implemented yet?
  2. t47352GitHub

    I keep getting this error, whether I use reg_pts or line_pts to define the crossing line:

    "ValueError: reg_pts is not a valid solution argument"

    I was initially using Yolo11 with the code in the "Speed Estimation using Ultralytics YOLO" section on this webpage. Then I noticed that the Youtube video on the webpage was with Yolo8, so I changed the model to yolov8m.pt. Everything works with either model as long as I don't add "reg_points" or "line_pts".

    So I tried to use "region=[(200,0), (200,720)]" instead but that didn't seem to do anything. My goal here is to only record speeds of people moving through a certain area/region of the video, not the speed of everyone in the frame. Could this be achieved?

    (FYI, I do not know how to code at all... I've just been copy/pasting things together and then getting Gemini to help me fix stuff where it can.) Thank you!

    1. Glenn JocherUltralytics

      @t47352 reg_pts/line_pts aren’t valid for YOLO11’s solutions.SpeedEstimator; use the documented args (model, fps, meter_per_pixel, etc.) and call it directly, then read per-ID speeds from speed.spd as shown in the guide and API reference.

      import cv2, numpy as np
      from ultralytics import solutions
      
      cap = cv2.VideoCapture("video.mp4")
      fps = cap.get(cv2.CAP_PROP_FPS)
      
      speed = solutions.SpeedEstimator(model="yolo11n.pt", fps=fps, meter_per_pixel=0.05, show=True)
      
      # Optional ROI filter (only keep speeds for boxes whose centroid is inside this polygon)
      roi = np.array([(200,0),(200,720),(400,720),(400,0)], dtype=np.int32)
      
      while cap.isOpened():
          ok, im0 = cap.read()
          if not ok:
              break
          res = speed(im0)  # processes and annotates frame
          speeds_in_roi = {}
          for box, tid in zip(speed.boxes, speed.track_ids):  # xyxy and track ids from last frame
              x1,y1,x2,y2 = map(float, box)
              cx, cy = (x1+x2)/2, (y1+y2)/2
              if cv2.pointPolygonTest(roi, (cx, cy), False) >= 0 and tid in speed.spd:
                  speeds_in_roi[tid] = speed.spd[tid]  # km/h for objects in your area
      • CLI (no ROI filtering):
      yolo solutions speed source="video.mp4" model=yolo11n.pt meter_per_pixel=0.05 show=True

      For supported arguments and examples see the Speed Estimation guide and the SpeedEstimator API reference: Speed Estimation using Ultralytics YOLO11 and SpeedEstimator class reference. If an error persists, please share the exact command and the output of yolo checks.

  3. greviewer-edtGitHub

    Buen día, podrias compartir por favor los link de los videos que estan en este articulo porfa

  4. NawzHGitHub

    If I were to provide a live video feed from a moving vehicle, with the camera facing out the front window, could the speed estimator track the speeds of vehicles approaching and receding?

    I understand this is possible with a stationary setup, but I am curious if the system can handle the added complexity of movement from the capturing vehicle itself?

    1. Glenn JocherUltralytics

      @NawzH the current Ultralytics YOLO11 Speed Estimator assumes a stationary camera setup for accurate speed estimation. For a moving vehicle, additional considerations such as compensating for the camera's motion using GPS or IMU data would be required. This functionality is not natively supported in our implementation but could potentially be developed with custom modifications.

    2. NawzHGitHub

      Hello Glenn, thank you for your response. I plan to use an OBD reader to capture the speed of the recording vehicle and am also now considering incorporating GPS data to aid in the estimation process.

      Since I am exploring the route of custom modifications, could you kindly point me to any guidance or documentation that might assist with integrating GPS and OBD data into the YOLO speed estimator? Any advice or resources would be greatly appreciated!

    3. Glenn JocherUltralytics

      Thank you for your interest! While we don't have direct documentation on integrating GPS and OBD data into the YOLO speed estimator, a possible approach would involve synchronizing GPS/OBD speed data with object tracking outputs to adjust for the capturing vehicle's motion. You may start by modifying the SpeedEstimator class in ultralytics/solutions/speed_estimation.py to incorporate this additional data.

    1. Glenn JocherUltralytics

      @SourceOfNootmite to use speed estimation for other objects like people, trains, or animals, you can specify the desired object classes by setting the classes argument in the SpeedEstimator. For example, classes=[0] for people or classes=[1, 2] for specific vehicles. Refer to Speed Estimation Documentation for detailed examples. Let me know if you need further clarification!

  5. 1024-ZhangGitHub

    Hello, I want to get the speed of each vehicle detected in the speed estimation method and write the vehicle ID and corresponding speed into a csv file. The speed written in the code below is not the speed of each vehicle detected, but the time taken to reason without a frame in the video. I'm using version 8.1.0 of YOLO.

    speeds = [] tracks = model.track(im0, persist=True, show=False) for track in tracks: speed = speed_obj.estimate_speed(im0, track) if speed is not None: speeds.append(track.speed) im0 = speed_obj.estimate_speed(im0, tracks) video_writer.write(im0)

    1. Glenn JocherUltralytics(modifié)

      @1024-Zhang to write the detected vehicle ID and speed into a CSV file, use the speeds returned by the current SpeedEstimator in results.speed_dict ({track_id: km/h}) after each frame:

      import csv
      import time
      
      with open("speeds.csv", "w", newline="") as f:
          writer = csv.writer(f)
          writer.writerow(["timestamp", "id", "speed_kmh"])
          # inside your frame loop
          results = speed_obj(im0)
          for track_id, speed in results.speed_dict.items():
              writer.writerow([time.time(), track_id, speed])

      See the Speed Estimation guide for the full setup. Let me know if you need further clarification!

  6. samkitshah18GitHub

    I believe for the code provided in the guide, we get object speed once it enters the region which is not updated further. For my use case, I have a video of a road with cars and for all the cars in the video I want to continuously track/detect speed throughout the video. Is this feasible using solutions.SpeedEstimator ? If yes, can you provide the code snippet/idea behind this ?

    1. Glenn JocherUltralytics(modifié)

      @samkitshah18 the current solutions.SpeedEstimator computes each tracked object's speed once it has been tracked for max_hist frames, then keeps that speed for the object's ID rather than updating it continuously. If you need continuously updated speeds, you can modify the SpeedEstimator source (ultralytics/solutions/speed_estimation.py) to not lock IDs, or compute speeds yourself from the track history. Keep persist=True tracking so IDs stay consistent. See the Speed Estimation guide for the current arguments. Let us know if you need further clarification!

    2. samkitshah18GitHub(modifié)

      Thank you for your response ! I tried to implement it.

      My code:

      from ultralytics.solutions import speed_estimation
      import cv2
      
      model = YOLO("yolo11n.pt")
      
      video_path = 'Path'
      cap = cv2.VideoCapture(video_path)
      assert cap.isOpened(), "Error opening video file"
      
      fps = int(cap.get(cv2.CAP_PROP_FPS))
      w, h = (int(cap.get(cv2.CAP_PROP_FRAME_WIDTH)), int(cap.get(cv2.CAP_PROP_FRAME_HEIGHT)))
      video_writer = cv2.VideoWriter("speed_estimation8.mp4", cv2.VideoWriter_fourcc(*"mp4v"), fps, (w, h))
      
      speed_obj = speed_estimation.SpeedEstimator(
          region=[(0, 0), (w, 0), (w, h), (0, h)],
          names=model.names,
          show=True,
      )
      
      object_speeds = {}
      
      while cap.isOpened():
          success, img = cap.read()
          if not success:
              break
      
          tracks = model.track(img, persist=True, show=True, tracker="bytetrack.yaml") 
      
          if tracks is not None:
              updated_tracks = []
              for track in tracks:
                  obj_id = track.id if hasattr(track, 'id') else None
                  if obj_id is not None:
                      if obj_id not in object_speeds:
                          object_speeds[obj_id] = []
      
                      if hasattr(track, 'speed'):
                          object_speeds[obj_id].append(track.speed)
      
                      updated_tracks.append(track)
      
              img = speed_obj.estimate_speed(img)
      
          video_writer.write(img)
      
      cap.release()
      video_writer.release()
      cv2.destroyAllWindows()```
      
      Now it detects 0 speed for all the cars even though it tracks and detects cars.
      
      After Speed Detection: https://streamable.com/67n3f4
      
      Can you please point me what am I missing here ?
    3. Glenn JocherUltralytics(modifié)

      The current SpeedEstimator no longer has a reg_pts argument or a speed region: it estimates the speed of every tracked object across the whole frame, so you don't need to define one. If speeds look wrong, check fps, meter_per_pixel and max_hist against the Speed Estimation guide, and make sure tracking IDs are consistent. Let me know how it goes!

    4. samkitshah18GitHub

      Thank you ! In my use case, I've several videos from varied camera angles so defining the reg_pts is not feasible and I want to track the objects in the entire video and not just a region. Even when I try to narrow down the region, using the persist=True in the above code does not update the speed of vehicles in the above code. Can you please provide any suggestions on how to resolve this ?

    5. Glenn JocherUltralytics(modifié)

      @samkitshah18 the current SpeedEstimator already tracks speeds across the entire frame without a region, and reg_pts is no longer an argument, so there is nothing to disable. If the speed doesn't update, note that each object's speed is calculated after it has been tracked for max_hist frames and then kept for that ID. Verify that frame-to-frame object IDs are consistent, and tune meter_per_pixel and fps for your video. Let us know if you have further issues!

  7. moshiourGitHub

    Hi,

    I would like to write speed using label box. However, the above script for speed estimation does not work. Even, I have already updated yolo11. Please check the above script in examples and here in discussion not same at all.

    In the example above no tracking : speed_obj = solutions.SpeedEstimator( region=[(0, 360), (1280, 360)], model="yolo11n.pt", show=True, )

    while cap.isOpened(): success, im0 = cap.read() if not success: break im0 = speed_obj.estimate_speed(im0) video_writer.write(im0)

    And in the discussion:

    Init speed-estimation obj

    speed_obj = solutions.SpeedEstimator( reg_pts=line_pts, names=names, view_img=True, )

    while cap.isOpened(): success, im0 = cap.read() if not success: print("Video frame is empty or video processing has been successfully completed.") break

    tracks = model.track(im0, persist=True, show=False)
    
    im0 = speed_obj.estimate_speed(im0, tracks)
    video_writer.write(im0)

    ==============================================

    Thank you in advance!

    1. Glenn JocherUltralytics

      @moshiour thank you for your comment. It seems there might be a discrepancy between the examples. Please ensure you're using the correct tracking setup as shown in the discussion. For detailed guidance, refer to our speed estimation documentation at https://docs.ultralytics.com/guides/speed-estimation/. If you have further questions, feel free to ask here.

  8. hardsluggerGitHub

    Hi! I am very glad that you introduced Yolov11 speed estimation module. I am very excited to start working with it. I have a question: Can I estimate speed of the vehicle without drawing the horizontal or vertical line? I am working on speed estimation of vehicles from the images captured by a camera mounted on an autonomous vehicle. Let me know how I can work this out?

    1. Glenn JocherUltralytics(modifié)

      @hardslugger yes, the current SpeedEstimator doesn't require you to draw lines or regions: reg_pts is no longer an argument. It estimates the speed of every tracked object in the frame, so just set fps and a meter_per_pixel scale that fits your camera's perspective. For more details, visit our speed estimation guide.

  9. eps1lonlineGitHub(modifié)

    Hi everyone, how can i add to array the speed of the car that passed the line? here is the code

    import os
    import cv2
    import time
    
    from ultralytics import YOLO, solutions
    
    # Запуск таймера
    start_time = time.time()
    
    # Путь, где будет сохранятся файл
    current_directory = os.getcwd()
    print("The resulting file is saved to the path:", current_directory)
    
    # Загрузка модели YOLOv8
    model = YOLO("yolov8n.pt")
    names = model.model.names
    
    # Открытие видеофайла
    videoFile = "car7.mp4"
    cap = cv2.VideoCapture(videoFile)
    assert cap.isOpened(), "Error reading video file"
    w, h, fps = (int(cap.get(x)) for x in (
        cv2.CAP_PROP_FRAME_WIDTH, 
        cv2.CAP_PROP_FRAME_HEIGHT, 
        cv2.CAP_PROP_FPS))
    
    # Инициализация видеописателя
    video_writer = cv2.VideoWriter(
        "speed_estimation.avi",
        cv2.VideoWriter_fourcc(*"mp4v"),
        fps, (w, h))
    
    # Определение линии
    line_pts = [(0, int(h/2)), (int(w), int(h/2))]
    
    # Инициализация объекта оценки скорости
    speed_obj = solutions.SpeedEstimator(reg_pts=line_pts,
                                          names=names,
                                          view_img=True,)
    
    speeds = []
    
    while cap.isOpened():
        success, im0 = cap.read()
        if not success:
            break
        tracks = model.track(im0, persist=True, show=False)
        im0 = speed_obj.estimate_speed(im0, tracks)
        video_writer.write(im0)
        
        print(speed_obj.spdl)
            
    
    # Освобождение ресурсов
    cap.release()
    video_writer.release()
    cv2.destroyAllWindows()
    
    # Время работы программы
    end_time = time.time()
    execution_time = end_time - start_time
    print("Program running time:", int(execution_time//60), " min ", int(execution_time%60), " sec")
    1. Glenn JocherUltralytics(modifié)

      @eps1lonline to add the speed of the car to an array, use the speeds returned by the current SpeedEstimator in results.speed_dict ({track_id: km/h}). Here's a minimal example:

      speeds = {}
      
      while cap.isOpened():
          success, im0 = cap.read()
          if not success:
              break
          results = speed_obj(im0)
          speeds.update(results.speed_dict)  # last known speed per track ID
          video_writer.write(results.plot_im)
      
      print(list(speeds.values()))

      This stores one speed per tracked car.

      -1
    2. eps1lonlineGitHub

      @glenn-jocher, good day.

      I wanted to know the speed of each car in km/h and put it in an array, but after looking at the code, I realized that this is not necessary, because all the speeds of cars can be obtained by accessing the Speed_obj object like this: Speed_obj.spd, we get a dictionary, where the index is the car number, and the value is the speed itself.

      Now I have a couple of other questions:

      1. For movement, we use the formula: U=S/t, where U is the speed of the car; S is the distance traveled by the car; t is time. My object: Speed_obj stores the coordinates along which each car moved, in order to get these coordinates, we must access the object like this: Speed_obj.trk_history. The distance itself is the Euclidean distance, i.e. we find the distance from the starting point to the next point, from this point to another point and so on until we reach the final one. So here's the question, I got that the distance = 600 pixels, how does your model convert pixels into meters, kilometers in order to calculate the speed?

      2. What is Speed_obj.spdl, it stores an array of several dozens that are constantly changing (10, 10, 10, 10, 10, 10...)

      Thank you for your attention!

    3. Glenn JocherUltralytics(modifié)

      @eps1lonline 1. The solution uses a calibration factor, meter_per_pixel, to convert pixels to real-world meters. You'll need to measure a known distance in the video to set this factor accurately.

      1. speed_obj.spdl belonged to an older version and no longer exists. In the current SpeedEstimator, the speeds are returned in results.speed_dict ({track_id: km/h}) each time you call it on a frame. See the speed estimation guide for details.