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