Light weight toolkit for bounding boxes providing conversion between bounding box types and simple computations. Supported bounding box types (italicized text indicates normalized values):
Glossary
Support for Python<3.8 will be dropped starting version 0.2 though the development for Python3.6 and Python3.7 may
continue where it will be developed under version 0.1.x for future versions. This may introduce; however, certain
discrepancies and/or unsupported operations in the 0.1.x versions. To fully utilize and benefit from the entire
package, we recommend using Python3.8 at minimum (Python>=3.8).
Through pip (recommended),
pip install pybboxes
or build from source,
git clone https://github.com/devrimcavusoglu/pybboxes.git
cd pybboxes
python setup.py install
You can easily create bounding box as easy as
from pybboxes import BoundingBox
my_coco_box = [98, 345, 322, 117]
coco_bbox = BoundingBox.from_coco(*my_coco_box) # <[98 345 322 117] (322x117) | Image: (?x?)>
# or alternatively
# coco_bbox = BoundingBox.from_array(my_coco_box)
Pybboxes supports OOB boxes, there exists a keyword strict in both Box classes (construction) and in functional
modules. When strict=True, it does not allow out-of-bounds boxes to be constructed and raises an exception, while
it does allow out-of-bounds boxes to be constructed and used when strict=False. Also, there is a property is_oob
that indicates whether a particular bouding box is OOB or not.
Important Note that, if the return value for is_oob is None, then it indicates that OOB status is unknown
(e.g. image size required to determine, but not given). Thus, values None and False indicates different information.
from pybboxes import BoundingBox
image_size = (640, 480)
my_coco_box = [98, 345, 580, 245] # OOB box for 640x480
coco_bbox = BoundingBox.from_coco(*my_coco_box, image_size=image_size) # Exception
# ValueError: Given bounding box values is out of bounds. To silently skip out of bounds cases pass 'strict=False'.
coco_bbox = BoundingBox.from_coco(*my_coco_box, image_size=image_size, strict=False) # No Exception
coco_bbox.is_oob # True
If you want to allow OOB, but still check OOB status, you should use strict=False and is_oob where needed.
With the BoundingBox class the conversion is as easy as one method call.
from pybboxes import BoundingBox
my_coco_box = [98, 345, 322, 117]
coco_bbox = BoundingBox.from_coco(*my_coco_box) # <[98 345 322 117] (322x117) | Image: (?x?)>
voc_bbox = coco_bbox.to_voc() # <[98 345 420 462] (322x117) | Image: (?x?)>
voc_bbox_values = coco_bbox.to_voc(return_values=True) # (98, 345, 420, 462)
However, if you try to make conversion between two bounding boxes that require scaling/normalization it'll give an error
from pybboxes import BoundingBox
my_coco_box = [98, 345, 322, 117]
coco_bbox = BoundingBox.from_coco(*my_coco_box) # <[98 345 322 117] (322x117) | Image: (?x?)>
# yolo_bbox = coco_bbox.to_yolo() # this will raise an exception
# You need to set image_size for coco_bbox and then you're good to go
coco_bbox.image_size = (640, 480)
yolo_bbox = coco_bbox.to_yolo() # <[0.4047 0.8406 0.5031 0.2437] (322x117) | Image: (640x480)>
Image size associated with the bounding box can be given at the instantiation or while using classmethods e.g
from_coco().
from pybboxes import BoundingBox
my_coco_box = [98, 345, 322, 117]
coco_bbox = BoundingBox.from_coco(*my_coco_box, image_size=(640, 480)) # <[98 345 322 117] (322x117) | Image: (640x480)>
# no longer raises exception
yolo_bbox = coco_bbox.to_yolo() # <[0.4047 0.8406 0.5031 0.2437] (322x117) | Image: (640x480)>
Box operations now available as of v0.1.0.
from pybboxes import BoundingBox
my_coco_box = [98, 345, 322, 117]
my_coco_box2 = [90, 350, 310, 122]
coco_bbox = BoundingBox.from_coco(*my_coco_box, image_size=(640, 480))
coco_bbox2 = BoundingBox.from_coco(*my_coco_box2, image_size=(640, 480))
iou = coco_bbox.iou(coco_bbox2) # 0.8117110631149508
area_union = coco_bbox + coco_bbox2 # 41670 | alternative way: coco_bbox.union(coco_bbox2)
total_area = coco_bbox.area + coco_bbox2.area # 75494 (not union)
intersection_area = coco_bbox * coco_bbox2 # 33824 | alternative way: coco_bbox.intersection(coco_bbox2)
first_bbox_diff = coco_bbox - coco_bbox2 # 3850
second_bbox_diff = coco_bbox2 - coco_bbox # 3996
bbox_ratio = coco_bbox / coco_bbox2 # 0.9961396086726599 (not IOU)
Note: functional computations are moved under pybboxes.functional starting with the version 0.1.0. The only
exception is that convert_bbox() which still can be used by importing pybboxes only (for backward compatibility).
You are able to convert from any bounding box type to another.
import pybboxes as pbx
coco_bbox = (1,2,3,4) # COCO Format bbox as (x-tl,y-tl,w,h)
voc_bbox = (1,2,3,4) # Pascal VOC Format bbox as (x-tl,y-tl,x-br,y-br)
pbx.convert_bbox(coco_bbox, from_type="coco", to_type="voc") # (1, 2, 4, 6)
pbx.convert_bbox(voc_bbox, from_type="voc", to_type="coco") # (1, 2, 2, 2)
Some formats require image width and height information for scaling, e.g. YOLO bbox (resulting coordinates are rounded to 2 decimals to ease reading).
import pybboxes as pbx
voc_bbox = (1,2,3,4) # Pascal VOC Format bbox as (x-tl,y-tl,x-br,y-br)
pbx.convert_bbox(voc_bbox, from_type="voc", to_type="yolo", image_size=(28, 28)) # (0.07, 0.11, 0.07, 0.07)
You can also make computations on supported bounding box formats.
import pybboxes.functional as pbf
coco_bbox = (1,2,3,4) # COCO Format bbox as (x-tl,y-tl,w,h)
voc_bbox = (1,2,3,4) # Pascal VOC Format bbox as (x-tl,y-tl,x-br,y-br)
pbf.compute_area(coco_bbox, bbox_type="coco") # 12
pbf.compute_area(voc_bbox, bbox_type="voc") # 4
pybboxes now supports the conversion of annotation file(s) across different annotation formats. (yolo, voc and coco are currently supported)
This is a 3 step process.
from pybboxes.annotations import Annotations
anns = Annotations(annotation_type='yolo')
Important you have to explicitly declare annotation_type beforehand. post declaration, you will be only able to load annotation in declared format but you will be able to export to other annotation formats.
After you have instantiated the Annotations class declaring annotation_type, you can now load the annotations using appropriate method of the Annotations class.
from pybboxes.annotations import Annotations
anns = Annotations(annotation_type='yolo')
anns.load_from_yolo(labels_dir='./labels', images_dir='./images', classes_file='./classes.txt')
As yolo normalizes the bounding box metadata, path to corresponding images directory must be provided (via images_dir) so that physical dimension of image data can be inferred.
Also, path to classes_file (usually classes.txt) should be provided that lists all the class labels that is used for the annotation. Without this, pybboxes will fail to assign appropriate class labels when converting across different annotations format.
from pybboxes.annotations import Annotations
anns = Annotations(annotation_type='voc')
anns.load_from_voc(labels_dir='./labels')
from pybboxes.annotations import Annotations
anns = Annotations(annotation_type='coco')
anns.load_from_coco(json_path='./validation.json')
As every image data has its own corresponding annotation file in yolo format, you have to provide path to export_dir where all the annotation files will be written.
from pybboxes.annotations import Annotations
anns = Annotations(annotation_type='coco') # just for the demonstration purpose
anns.load_from_coco(json_path='./validation.json') # we could have loaded the annotation data from other format as well
anns.save_as_yolo(export_dir='./labels')
This will create all the required annotation files (in yolo format) in given directory. Additionally, it will also create classes.txt in the given folder which will list all the class labels used for the annotation.
Just like yolo format, in voc format, every image data has also its own corresponding annotation file. So, you have to provide path to export_dir where all the annotation files will be written.
from pybboxes.annotations import Annotations
anns = Annotations(annotation_type='coco') # just for the demonstration purpose
anns.load_from_coco(json_path='./validation.json') # we could have loaded the annotation data from other format as well
anns.save_as_voc(export_dir='./labels')
To export annotations in coco format, you just have to provide name (or path) of the output file (in json format) via export_file.
from pybboxes.annotations import Annotations
anns = Annotations(annotation_type='voc') # just for the demonstration purpose
anns.load_from_voc(labels_dir='./labels') # we could have loaded the annotation data from other format as well
anns.save_as_coco(export_file='./validation.json')
Install the package as follows, which will set you ready for the development mode.
pip install -e .[dev]
To tests simply run.
python -m tests.run_tests
To check code style,
python -m tests.run_code_style check
To format codebase,
python -m tests.run_code_style format
Licensed under the MIT License.
FAQs
Light Weight Toolkit for Bounding Boxes
We found that pybboxes demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.