Version: 2.0.0 (using KDE 4.6.2) OS: Linux New /location tags do not replace the existing ones and a repeated reverse geotagging is applied. Reproducible: Always Steps to Reproduce: Open MyBestImage.jpg in Geolocation plugin, set GPS coordines to CityA, apply reverse geotagging. Either close Geo-location plugin or even keep it open and change the GPS coordinates for MyBestImage.jpg to CityB and apply new reverse geotagging. Actual Results: MyBestImage.jpg has two locations in tags: /location/blabla/blabla/CityA and /location/blabla/blabla/CityB. Expected Results: Only the last /location/blabla/blabla/CityB is set. Any prior /location/... shall be removed. Further, if an image, which already has /location/.... set, is opened in Geo-location plugin, the /location/... should be shown in the plugin's Tag column as well.
Hi Milan, the problem here is that we don't store that some tags are 'location' tags, they are just regular tags once stored in the database or in the image. To do something as you propose, we would either have to start noting the 'location' type in the database, or also allow the user to specify a pattern of tags which should be removed once new geotags arrive. Maybe one could let the user mark one tag as the 'location' tag, instead of creating patterns. Michael
Milan, the bugs you are filing here actually belong to kipi-plugins/gpssync.
I have overlooked the "list all.." projects during the selections phase of reporting a new bug and kipi-plugins is not listed in those pre-selected, sorry - I promise to get better ;-) (I do not use kde bugs reporting system regularly and it always takes some time to get used to its user interface. )
Milan, Michael, This file still valid using kipi-plugins 2.4 ? Gilles Caulier
As far as I can tell, the behaviour has not changed.
This file still valid using last kipi-plugins 4.10.0 ? Gilles Caulier
With kipi-plugins 4.12.0 the buggy behaviour is still the same.
*** Bug 304591 has been marked as a duplicate of this bug. ***
Can you reproduce the problem using digiKam Linux AppImage bundle ? The last bundle is available at this url: https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM Gilles Caulier
digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Best Regards Gilles Caulier
Unfortunatelly, the bug is the same as reported originally.
@Milan digiKam 8.0.0 is out. Problem still reproducible ? Best regards Gilles Caulier
#Milan, What's about this file using current 8.2.0 AppImage Linux bundle ? It's reproducible ? https://files.kde.org/digikam/ Note: bundle is now based on Qt 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier