Search before asking
Description
I am currently utilizing the as_coco function from sv.DetectionDataset within the Supervision API extensively and find it incredibly useful. However, I've encountered an issue when importing these labels into CVAT label tool. It seems that CVAT accepts category_id starting from 1, whereas the as_coco output starts with category_id at 0. This discrepancy leads to import failures.
Would it be possible to add a parameter to the as_coco function to adjust the starting index of category_id? This feature would greatly enhance compatibility with CVAT and streamline the workflow for users facing similar issues.
Thank you for considering this enhancement. I look forward to any updates you might have on this request.
Use case
No response
Additional
No response
Are you willing to submit a PR?
Search before asking
Description
I am currently utilizing the
as_cocofunction from sv.DetectionDataset within the Supervision API extensively and find it incredibly useful. However, I've encountered an issue when importing these labels into CVAT label tool. It seems that CVAT accepts category_id starting from 1, whereas the as_coco output starts with category_id at 0. This discrepancy leads to import failures.Would it be possible to add a parameter to the as_coco function to adjust the starting index of category_id? This feature would greatly enhance compatibility with CVAT and streamline the workflow for users facing similar issues.
Thank you for considering this enhancement. I look forward to any updates you might have on this request.
Use case
No response
Additional
No response
Are you willing to submit a PR?