We’ve noticed in recent weeks that when using the Vaadin upload component in a web app, the geo-data of images is very often changed to a value of 0. Is there any information on this?
Have you checked the source images that they contain the correct data?
That does not sound anything Vaadin touches at all. Should not. This is part of the binary, right?
If the data is in the original images, and the application itself does not remove it. Is there anything between (browser itself, network proxy, …) that could potentially modify this e.g. to protect users.
We are using a software tool (web app) in the browser (Edge, Chrome, Safari, Samsung Internet, etc.) on mobile devices.
The file/image upload component of Vaadin selects previously saved photos with geotags.
According to our analysis, the geotags of the images are changed to 0 as soon as they are selected, effectively removing them. This can be reproduced very often with different browsers and operating systems, but not always.
The same behavior occurs when new photos are taken using the file/image upload component on mobile devices.
The same behavior occurs when new photos are taken using the file/image upload component on mobile devices.
Google says: totally normal. Ask apple about it. https://stackoverflow.com/questions/16297730/image-upload-from-iphone-strips-exif-data