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