SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** DigiKam version Build date: 8/23/2022 3:24 PM (target: RelWithDebInfo) Revision: 87d0bb259a475adf94fd188cb3685d8efc16f121 Branch: qt5-maintenance STEPS TO REPRODUCE 1. Open a tag in the left panel (I have a tag set up for each step in my workflow) - it is one of those. 2. Select some of the images and discover that they really are missing IPTC location information. 3. Since this has to be done one image at a time in DigiKam (see bugs about Reverse geocoding not doing it, and templates being completely useless). Use Geosetter to do the reverse geocoding. 4. Now inspect the images in the digikam right panel. 5. Update the database from the metadata for the Album you were working on. 6. Inspect the images in the right panel again. OBSERVED RESULT The reverse GEOCode result is in the file. The reverse GEO code does not appear in the metadata editor. EXPECTED RESULT The reverse GEOCode information should appear in the editor SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Please upload an image edited with Geosetter. The digiKam metadata editor does not use the database, if the information does not appear in the editor fields, it is not in the metadata either. Maik
@jm7@acm.org Do you seen the last comment from Maik ? Gilles Caulier
@jm7@acm.org Maik ask you to provide files tagged with GeoSetter application. Without this, we cannot hack your problem. Thanks in advance Gilles Caulier
I tested Geosetter. digiKam takes over the reverse geolocation data in the template display without any problems. In order for the initial scan to update the information in the DB, the option to re-read the metadata when file changes should be activated in the digiKam Metadata settings. Maik