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

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, keypoint_detection_prediction, instance_segmentation_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>"
}