Bounding boxes disappeared?

[alanstenhouse]

Describe the bug
Bounding boxes no longer exist. After tagging and saving project multiple times resulting in almost 1000 images from several Source Connections being tagged with bounding boxes and labels, I've today re-opened the project and started looking at them again and it appears as though all the bounding box information and labels have been lost, except for the very last image.

Source Connections are all Local File System.

To Reproduce
Not sure how to reproduce as I don't want to go through this again. Wonder if anyone else has experienced this and what might cause it. Can changing your Source or Target Connection at any stage result in this problem?

Expected behavior
I do not expect to lose my labels and bounding boxes for each image unless I forget to save the project.

Desktop (please complete the following information):

• OS: MacOS 10.14.5
  Vott.app v.2.0.0

[anhlt]

I have the same problem, seem like the asset file is broken while save

{
    "asset": {
        "format": "jpg",
        "id": "ef76b3d34e62cff09efee9110adf799c",
        "name": "174.20553.jpg",
        "path": "file:/Users/abesoya/%E5%90%8D%E7%A7%B0%E6%9C%AA%E8%A8%AD%E5%AE%9A%E3%83%95%E3%82%A9%E3%83%AB%E3%82%BF%E3%82%99/%E7%97%85%E5%AE%B3%E8%99%AB%E3%82%AB%E3%83%A1%E3%83%A9%EF%BC%92/%E3%81%86%E3%81%A8%E3%82%99%E3%82%93%E3%81%93%E7%97%85/174.20553.jpg",
        "size": {
            "width": 400,
            "height": 272
        },
        "state": 2,
        "type": 1
    },
    "regions": [
        {
            "id": "z6Y-d4Jl8",
            "type": "RECTANGLE",
            "tags": [
                "うどん粉病"
            ],
            "boundingBox": {
                "height": 199.5903831562974,
                "width": 204.51496388028895,
                "left": 182.77541279669762,
                "top": 36.52968512898331
            },
            "points": [
                {
                    "x": 182.77541279669762,
                    "y": 36.52968512898331
                },
                {
                    "x": 387.29037667698657,
                    "y": 36.52968512898331
                },
                {
                    "x": 387.29037667698657,
                    "y": 236.12006828528072
                },
                {
                    "x": 182.77541279669762,
                    "y": 236.12006828528072
                }
            ]
        }
    ],
    "version":

This is my asset.json file content.

[alanstenhouse]

Ok, I did a little testing and it's my mistake/lack of knowledge about the system that contributed to this. But perhaps an enhancement request instead?

I could replicate it by doing some work on a set of images, saving, and then (the key point) - changing the projects "Target Connection" folder. This resulted in the loss of all bounding box information for all images up to that point.

Of course, now that I realise this is where the project data are also stored, I can understand it a little better. But, I would think that better behaviour would be to also save all the current images + bounding boxes information inside the project to the new target location, rather than losing the bounding boxes info.

So... not sure if I should leave this as a bug/enhancement request, or to close?

[Clayton-Klemm]

Ok, I did a little testing and it's my mistake/lack of knowledge about the system that contributed to this. But perhaps an enhancement request instead?

I could replicate it by doing some work on a set of images, saving, and then (the key point) - changing the projects "Target Connection" folder. This resulted in the loss of all bounding box information for all images up to that point.

Of course, now that I realise this is where the project data are also stored, I can understand it a little better. But, I would think that better behaviour would be to also save all the current images + bounding boxes information inside the project to the new target location, rather than losing the bounding boxes info.

So... not sure if I should leave this as a bug/enhancement request, or to close?

good god yeah I think the same thing append to me. I also deleted all the folders in destination location because the export wasn't what i needed not realizing that the labeling data is stored there as well. luckily this was the one time where I didn't immediately empty the recycle bin which would have been a loss of around 2 hours of video labeling.

[marireeves]

It's also really a pain on windows, due to the slash backslash issue, so hopefully you're using a different OS. I did get my photos back by re-assigning the drive letter to what it used to be (with identical path) but it seems to have lost all the bounding boxes. I've changed the target directory (creating several different VoTT files in the process) to places where I had previously exported json files, tfrecords, and a csv file for the project (three targets, three vott files...), but still no bounding boxes have re-appeared. Their information is definitely contained in the json files at least (the csv is empty - the tfrecords are either binary or mostly encoded, so I can't figure out how to read them). So if anyone knows how to get VoTT to read those bounding boxes back out of the original json files, I would appreciate it.! This is useful, but as pointed out in comments, difficult to implement in windows. https://github.com/cnrmck/update-vott-assets