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

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>"
}