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