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

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[instance_segmentation_prediction, keypoint_detection_prediction, object_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>"
}