Download and convert MIDV-500 datasets into COCO instance segmentation format
Automatically download/unzip MIDV-500 and MIDV-2019 datasets and convert the annotations into COCO instance segmentation format.
Then, dataset can be directly used in the training of Yolact, Detectron type of models.
MIDV-500 Datasets
MIDV-500 consists of 500 video clips for 50 different identity document types including 17 ID cards, 14 passports, 13 driving licences and 6 other identity documents of different countries with ground truth which allows to perform research in a wide scope of various document analysis problems. Additionally, MIDV-2019 dataset contains distorted and low light images in it.
You can find more detail on papers:
MIDV-2019: Challenges of the modern mobile-based document OCR
Getting started
Installation
pip install midv500
Usage
- Import package:
import midv500
- Download and unzip desired version of the dataset:
# set directory for dataset to be downloaded
dataset_dir = 'midv500_data/'
# download and unzip the base midv500 dataset
dataset_name = "midv500"
midv500.download_dataset(dataset_dir, dataset_name)
# or download and unzip the midv2019 dataset that includes low light images
dataset_name = "midv2019"
midv500.download_dataset(dataset_dir, dataset_name)
# or download and unzip both midv500 and midv2019 datasets
dataset_name = "all"
midv500.download_dataset(dataset_dir, dataset_name)
- Convert downloaded dataset to coco format:
# set directory for coco annotations to be saved
export_dir = 'midv500_data/'
# set the desired name of the coco file, coco file will be exported as "filename + '_coco.json'"
filename = 'midv500'
# convert midv500 annotations to coco format
midv500.convert_to_coco(dataset_dir, export_dir, filename)
Metadata
Release files for midv500 0.2.1
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 |
|---|---|---|---|---|
| midv500-0.2.1.tar.gz | 8.9 kB | Without provenance | Details for midv500-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| midv500-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for midv500-0.2.1-py3-none-any.whl |
Total release size: 18.5 kB
Release files / midv500-0.2.1.tar.gz
| Download URL | midv500-0.2.1.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
67700de22a5bb6dc3413a84e9ae7da45f6212e8eba67ab881133573ac1f4fd6b
|
|
BLAKE2b-256 checksum How to use checksums |
59dc805b2ea2d865b85e5c72c76b90ed7007b83eb62333d48c478acfa629f55b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/47.1.0 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.8.5
|
Release files / midv500-0.2.1-py3-none-any.whl
| Download URL | midv500-0.2.1-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
390b659e023065dca913451a599defdde75ab9216b6a5a83599d27f9ffb5b0f9
|
|
BLAKE2b-256 checksum How to use checksums |
eb8fd900a8fed8fa7047fb43ace56860950cf3f9a0352379a1ec38ae035b4df6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/47.1.0 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.8.5
|
Security for midv500 0.2.1
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.