Is your feature request related to a problem? If so, Please describe.
VIAME CSV is unique to VIAME/DIVE. We would like to incorporate DIVE outputs into our processing pipelines. The current outputs from DIVE (such as VIAME CSV) are not good for this, because they aren't common standards. Frankly, 2D CSV just isn't powerful enough to handle computer vision annotation data. The current VIAME CSV is "ragged right" to try to deal with some of this, but this is breaks most common CSV reader software (e.g. pandas).
Describe the solution you'd like
Preferably kwcoco for video, with fields limited to coco-compatible fields for image data.
Describe alternatives you've considered
Honestly, the landscape for video and image annotation formats is extremely broad, so finding truly "interoperable standards" is difficult. COCO is supported very broadly, and kwcoco is already a Kitware standard which supports natural COCO extensions to accommodate video and soft targets. We are more than happy to see DIVE support other formats, but COCO/kwcoco would get us a long way for now.
Additional context
NMFS is actively insisting that optics groups format their data as COCO/kwcoco. Please support these formats.
Is your feature request related to a problem? If so, Please describe.
VIAME CSV is unique to VIAME/DIVE. We would like to incorporate DIVE outputs into our processing pipelines. The current outputs from DIVE (such as VIAME CSV) are not good for this, because they aren't common standards. Frankly, 2D CSV just isn't powerful enough to handle computer vision annotation data. The current VIAME CSV is "ragged right" to try to deal with some of this, but this is breaks most common CSV reader software (e.g. pandas).
Describe the solution you'd like
Preferably kwcoco for video, with fields limited to coco-compatible fields for image data.
Describe alternatives you've considered
Honestly, the landscape for video and image annotation formats is extremely broad, so finding truly "interoperable standards" is difficult. COCO is supported very broadly, and kwcoco is already a Kitware standard which supports natural COCO extensions to accommodate video and soft targets. We are more than happy to see DIVE support other formats, but COCO/kwcoco would get us a long way for now.
Additional context
NMFS is actively insisting that optics groups format their data as COCO/kwcoco. Please support these formats.