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