Some image annotation render outside the image frame

[kintopp]

For example here https://explorer.odeuropa.eu/smells/2240a201-c1e4-56ed-9d71-f0e082f2f973?q=butter&display=text&page=3&stype=smells&sapi=%2Fapi%2Fsearch&spath=%2Fsmells or here https://explorer.odeuropa.eu/smells/299ac334-5161-5a54-966e-5f6f00b09ee2?q=butter&display=text&page=4&stype=smells&sapi=%2Fapi%2Fsearch&spath=%2Fsmells

[rtroncy]

Good bug found! I guess that we are rescaling the images to display them in Explorer and that image annotations are expressed using absolute positioning in pixels to higher definition of images. This would be non trivial though to extrapolate the coordinates of the box to lower scale images.

[pasqLisena]

I think may be dependent by this other issue Odeuropa/knowledge-graph#10

[ehrhart]

We are not rescaling the images on the Explorer. However, some annotations seem to be out of bound. Let's take this example:

• Smell: https://explorer.odeuropa.eu/smells/5cc83f25-f36d-5393-bffa-67e1f5e9ef36
• Image URL: https://data.odeuropa.eu/image/fa71a96a-381b-6881-fe60-c3b2f790a627.jpg
• Size: 509x650

This annotation http://data.odeuropa.eu/source/bba099d9-9ae0-586e-aad6-09861b7b4798#xywh=573,377,55,52 is at coordinates 573:377 which is outside of the image boundaries.

So it seems that the images on data.odeuropa.eu have a different size than the ones that have been processed by the image annotation system. Do we resize images somewhere in the process when uploading them?

[pasqLisena]

No we do not resize the image.

But there is a deeper problem: the original image should be https://rkd.nl/nl/explore/images/34340
So, we uploaded at that uri an image that is not the correct one.

I can correct this specific case manually, but I doubt we can easily detect and download all of them

[mathiaszinnen]

The problem comes from our data, Prathmesh and I will look into this next week

[prathmeshrmadhu]

Note to @mathiaszinnen and me - This should also be done for ODOR-v3 too.

[rtroncy]

@prathmeshrmadhu This is not clear to me how to interpret your comment. Do you mean you have something to do for the ODOR-v3 dataset? Or do you mean that you have done everything already and that we should re-process the data? If so, where are the resources?

[prathmeshrmadhu]

Sorry, @rtroncy - This was for an internal point (between me and Mathias), I will edit it. Currently, nothing needs to be done at your end.

[rtroncy]

@prathmeshrmadhu Can you please update us on this issue?

[mathiaszinnen]

If I recall correctly, we updated the metadata and image files to fix the issue. I do see now, however, that the issue in the example @ehrhart linked still persists. Maybe it can be fixed by incorporating the latest metadata and image files @pasqLisena?

[rtroncy]

@mathiaszinnen Can you provide us again with the link where we can download the latest version of the metadata and the corresponding directory of image files?

[mathiaszinnen]

These are the latest image files.
This is the latest metadata file.

[pasqLisena]

Ok, apparently we were parsing an old version of the annotation, we will fix this in next data release.

(keeping this open until next data load)