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