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