Detections Merge

Class: DetectionsMergeBlockV1

Source: inference.core.workflows.core_steps.transformations.detections_merge.v1.DetectionsMergeBlockV1

The DetectionsMerge block combines multiple detections into a single bounding box that encompasses all input detections. This is useful when you want to: - Merge overlapping or nearby detections of the same object - Create a single region that contains multiple detected objects - Simplify multiple detections into one larger detection

The resulting detection will have: - A bounding box that contains all input detections - The classname of the merged detection is set to "merged_detection" by default, but can be customized via the class_name parameter - The confidence is set to the lowest confidence among all detections

Type identifier

Use the following identifier in step "type" field: roboflow_core/detections_merge@v1to add the block as as step in your workflow.

Properties

Name	Type	Description	Refs
name	str	Enter a unique identifier for this step..	❌
class_name	str	The class name to assign to the merged detection..	❌

The Refs column marks possibility to parametrise the property with dynamic values available in workflow runtime. See Bindings for more info.

Available Connections

Compatible Blocks

Check what blocks you can connect to Detections Merge in version v1.

• inputs: Detections Filter, Detections Combine, YOLO-World Model, Detections Stitch, VLM as Detector, Detections Classes Replacement, Google Vision OCR, Path Deviation, Time in Zone, Template Matching, Line Counter, Overlap Filter, Gaze Detection, Instance Segmentation Model, Perspective Correction, Time in Zone, Object Detection Model, Keypoint Detection Model, Bounding Rectangle, Detections Consensus, Dynamic Crop, OCR Model, EasyOCR, Time in Zone, Velocity, Keypoint Detection Model, Detections Stabilizer, Instance Segmentation Model, Segment Anything 2 Model, VLM as Detector, Detection Offset, Moondream2, Object Detection Model, Byte Tracker, PTZ Tracking (ONVIF).md), Dynamic Zone, Path Deviation, Detections Merge, Byte Tracker, Detections Transformation, Byte Tracker
• outputs: Detections Filter, Detections Combine, Distance Measurement, Icon Visualization, Detections Stitch, Detections Classes Replacement, Path Deviation, Model Monitoring Inference Aggregator, Time in Zone, Circle Visualization, Roboflow Dataset Upload, Dot Visualization, Line Counter, Overlap Filter, Blur Visualization, Perspective Correction, Time in Zone, Roboflow Dataset Upload, Background Color Visualization, Florence-2 Model, Detections Consensus, Dynamic Crop, Crop Visualization, Trace Visualization, Time in Zone, Color Visualization, Velocity, Triangle Visualization, Detections Stabilizer, Ellipse Visualization, Model Comparison Visualization, Segment Anything 2 Model, Detection Offset, Corner Visualization, Florence-2 Model, Size Measurement, Roboflow Custom Metadata, Line Counter, Bounding Box Visualization, Pixelate Visualization, Byte Tracker, Stitch OCR Detections, PTZ Tracking (ONVIF).md), Path Deviation, Label Visualization, Detections Merge, Byte Tracker, Detections Transformation, Byte Tracker

Input and Output Bindings

The available connections depend on its binding kinds. Check what binding kinds Detections Merge in version v1 has.

Bindings

• input

  • predictions (Union[object_detection_prediction, instance_segmentation_prediction, keypoint_detection_prediction]): Object detection predictions to merge into a single bounding box..

• output

  • predictions (object_detection_prediction): Prediction with detected bounding boxes in form of sv.Detections(...) object.

Example JSON definition of step Detections Merge in version v1

{
    "name": "<your_step_name_here>",
    "type": "roboflow_core/detections_merge@v1",
    "predictions": "$steps.object_detection_model.predictions",
    "class_name": "<block_does_not_provide_example>"
}