coco-lib
COCO dataset library. Provides serializable native Python bindings for several COCO dataset formats.
Supported bindings and their corresponding modules:
- Object Detection:
objectdetection - Keypoint Detection:
keypointdetection - Panoptic Segmentation:
panopticsegmentation - Image Captioning:
imagecaptioning
Installation
coco-lib is available on PyPI:
pip install coco-lib
Usage
Creating a dataset (Object Detection)
>>> from coco_lib.common import Info, Image, License
>>> from coco_lib.objectdetection import ObjectDetectionAnnotation, \
... ObjectDetectionCategory, \
... ObjectDetectionDataset
>>> from datetime import datetime
>>> info = Info( # Describe the dataset
... year=datetime.now().year,
... version='1.0',
... description='This is a test dataset',
... contributor='Test',
... url='https://test',
... date_created=datetime.now()
... )
>>> mit_license = License( # Set the license
... id=0,
... name='MIT',
... url='https://opensource.org/licenses/MIT'
... )
>>> images = [ # Describe the images
... Image(
... id=0,
... width=640, height=480,
... file_name='test.jpg',
... license=mit_license.id,
... flickr_url='',
... coco_url='',
... date_captured=datetime.now()
... ),
... ...
... ]
>>> categories = [ # Describe the categories
... ObjectDetectionCategory(
... id=0,
... name='pedestrian',
... supercategory=''
... ),
... ...
... ]
>>> annotations = [ # Describe the annotations
... ObjectDetectionAnnotation(
... id=0,
... image_id=0,
... category_id=0,
... segmentation=[],
... area=800.0,
... bbox=[300.0, 100.0, 20.0, 40.0],
... is_crowd=0
... ),
... ...
... ]
>>> dataset = ObjectDetectionDataset( # Create the dataset
... info=info,
... images=images,
... licenses=[mit_license],
... categories=categories,
... annotations=annotations
... )
>>> dataset.save('test_dataset.json', indent=2) # Save the dataset
Loading a dataset
>>> from coco_lib.objectdetection import ObjectDetectionDataset
>>> dataset = ObjectDetectionDataset.load('test_dataset.json') # Load the dataset
Flexible Datetime Parsing
The library now supports flexible datetime parsing using dateparser. Date fields (Info.date_created and Image.date_captured) can now accept various datetime formats:
>>> from coco_lib.common import Info, Image
>>> # Various date formats are automatically parsed
>>> info1 = Info.from_json('{"date_created": "2023/01/15"}') # Original format
>>> info2 = Info.from_json('{"date_created": "2023-01-15"}') # ISO format
>>> info3 = Info.from_json('{"date_created": "January 15, 2023"}') # Natural language
>>> info4 = Info.from_json('{"date_created": "15 Jan 2023"}') # Short format
>>> # All produce the same date
>>> assert info1.date_created.date() == info2.date_created.date() == info3.date_created.date() == info4.date_created.date()
>>> # Invalid dates return None and emit a warning
>>> import warnings
>>> with warnings.catch_warnings(record=True) as w:
... warnings.simplefilter("always")
... info = Info.from_json('{"date_created": "invalid date"}')
... assert info.date_created is None # Returns None
... assert len([warning for warning in w if issubclass(warning.category, UserWarning)]) > 0 # Warning emitted
>>> # Serialization maintains original formats for backward compatibility
>>> from datetime import datetime
>>> info = Info(date_created=datetime(2023, 1, 15))
>>> json_str = info.to_json()
>>> assert "2023/01/15" in json_str # Uses YYYY/MM/DD format
Metadata
Release files for coco-lib 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| coco_lib-0.3.0.tar.gz | 23.1 kB | Without provenance | Details for coco_lib-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| coco_lib-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for coco_lib-0.3.0-py3-none-any.whl |
Total release size: 36.0 kB
Release files / coco_lib-0.3.0.tar.gz
| Download URL | coco_lib-0.3.0.tar.gz |
|---|---|
| Size | 23.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
791b848d8eb7028c3f9944a0cb0f7c0f1caf5a600d45034e5fef695b7685f169
|
|
BLAKE2b-256 checksum How to use checksums |
ff0e5896349e01377629f467ea91320ad5044b0cd856c49068fedb9724f24370
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.0
|
Release files / coco_lib-0.3.0-py3-none-any.whl
| Download URL | coco_lib-0.3.0-py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
87cd2735502fd0c25c5c4cba156a2f88be01bb8a40b696a861dccde650c5125b
|
|
BLAKE2b-256 checksum How to use checksums |
a4d8d226b3c97e97b35302e80f6b33e6f795b40b995dc99329a2617b56f89732
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.0
|
Security for coco-lib 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.