when reloading an annotations file, polygons show up as rectangles

[hqm]

Describe the bug I labeled some polygons on some images, and exported the dataset as COCO JSON file

When I reload the page and add the images, then import that saved annotations file, the annotations appear as bounding box rectangles, rather than polygons

To Reproduce Steps to reproduce the behavior:

1. Go to makesense.ai
2. Click on Drop Images,
3. drop some images in
4. load a labels.txt file
5. label some polygons
6. Export the annotations COCO json format file
7. Reload the page and go through the steps above to load images and labels
8. click on the Action -> Import Annotations
9. The annotations appear as white rectangles rather than polygons

Expected behavior I would expect the re-imported annotations to appear as polygons

Screenshots

Desktop (please complete the following information):

• OS: OSX
• Browser CHROME
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

[github-actions[bot]]

👋 Hello @hqm, thank you for your interest in make-sense labelling tool 🏷️!

🐞 Bug reports

Please provide us with as much information as possible. To make your life easier, we have prepared a bug report template. We know! We ask for a lot of information, but please believe that it really helps us to know which browser you are using. 😉

💻 Local setup

# clone repository
git clone https://github.com/SkalskiP/make-sense.git

# navigate to main dir
cd make-sense

# install dependencies
npm install

# serve with hot reload at localhost:3000
npm start

To ensure proper functionality of the application locally, an npm 6.x.x and node.js v11.x.x versions are required. More information about this problem is available in the #16 issue.

[SkalskiP]

Hello 👋, @hqm! Many thanks for drawing our attention to this problem. It is indeed not possible at the moment to export polygons in COCO JSON format. Which consequently leads to, the behavior you described. I don't know if this is a bug report or a feature request, but one thing is for sure we need to provide the ability to export and re-import polygons in COCO JSON format. I am starting work on the make-sense beta, and I want this issue to be part of it.

[hqm]

thanks, yes this is a feature request , I'm training Mask RCNN detectron2 networks, and would like to work with polygons.

What confuses me is it look like the downloaded exported COCO dataset does have polygon segmentation contours in it, so it looks like they are being exported, just not being read on import?

{
  "id": 0,
  "iscrowd": 0,
  "image_id": 1,
  "category_id": 3,
  "segmentation": [
    [
      1052.6541554959786,
      630.0804289544236,
      1219.946380697051,
      676.4075067024129,
      1449.0080428954423,
      313.51206434316356,
      1330.6166219839142,
      292.92225201072387
    ]
  ],
  "bbox": [
    1052.6541554959786,
    292.92225201072387,
    396.3538873994637,
    383.485254691689
  ],
  "area": 58480.58708105418
}

On Fri, Aug 27, 2021 at 5:26 PM Piotr Skalski @.***> wrote:

Hello 👋, @hqm https://github.com/hqm! Many thanks for drawing our attention to this problem. It is indeed not possible at the moment to export polygons in COCO JSON format. Which consequently leads to, the behavior you described. I don't know if this is a bug report or a feature request, but one thing is for sure we need to provide the ability to export and re-import polygons in COCO JSON format. I am starting work on the make-sense beta, and I want this issue to be part of it.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/SkalskiP/make-sense/issues/181#issuecomment-907485638, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAAORTN3NFTJFSWHGXXWDLT677KBANCNFSM5C6CAZTQ .

-- Henry Minsky

[SkalskiP]

Don't worry, we will certainly be able to solve this problem. However, I do not know how quickly we will be able to deal with it. Unfortunately, we have several higher-priority issues in the queue. :/ Please be patient.