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