| Summary: | Using rounded coordinates for map display causes wrong emplacement of picture | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | ThierryA <thierry> |
| Component: | Geolocation-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.8.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | https://invent.kde.org/graphics/digikam/commit/b7d61cad9f0bb72398fb1de405b741d01d050bab | Version Fixed/Implemented In: | 7.9.0 |
| Sentry Crash Report: | |||
| Attachments: |
Screenhot showing the map with the picture in the wrong place
Sample picture |
||
|
Description
ThierryA
2022-11-09 12:14:15 UTC
The coordinates are not rounded. I suspect incorrect coordinates in the XMP metadata area that digiKam reads first. Please upload a sample image if not public to my private mail. Has the image been processed with DxO? Maik Created attachment 153623 [details]
Sample picture
Sample picture as requested
(In reply to Maik Qualmann from comment #1) > The coordinates are not rounded. I suspect incorrect coordinates in the XMP > metadata area that digiKam reads first. Please upload a sample image if not > public to my private mail. > Has the image been processed with DxO? > > Maik Thanks for the QUICK answer ! Yes the image has been processed with DxO Sample picture added. The image is shown here in the correct position (digiKam-8.0.0 on Windows). Please re-read the metadata from the image, Item Menu-> Re-read metadata from file. Maik This image produces an error with Exiv2. In digiKam-8.0.0 it is then read with ExifTool, which can be the reason that the position is correct here. [5692] digikam.metaengine: Exiv2 ( 2 ) : Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored. Maik (In reply to Maik Qualmann from comment #5) > This image produces an error with Exiv2. In digiKam-8.0.0 it is then read > with ExifTool, which can be the reason that the position is correct here. > > [5692] digikam.metaengine: Exiv2 ( 2 ) : Directory OlympusCs, entry 0x0101: > Strip 0 is outside of the data area; ignored. > > Maik I refreshed metadata from files as suggested but no luck. I'm currently using version 7.8.0 of Digikam, maybe this explains it ? Maybe I should upgrade ? You can try to upgrade to 7.9.0 pre-release, but i doubt that Exiv2 will fix this error. The windows installer that we provide is compiled with an Exiv2 maintenance branch of source code. https://files.kde.org/digikam/ Best Gilles Caulier (In reply to caulier.gilles from comment #7) > You can try to upgrade to 7.9.0 pre-release, but i doubt that Exiv2 will fix > this error. > > The windows installer that we provide is compiled with an Exiv2 maintenance > branch of source code. > > https://files.kde.org/digikam/ > > Best > > Gilles Caulier Thanks for this very quick and effective support ! I upgraded straight to version 8.0.0 (I'm ready to cope with a few rough edges) and re-read the metadata from the files. The problem disappeared. We can close the issue for me: problem solved ! Many thanks again. Git commit b7d61cad9f0bb72398fb1de405b741d01d050bab by Maik Qualmann. Committed on 09/11/2022 at 18:20. Pushed by mqualmann into branch 'qt5-maintenance'. fix get geolocation coordinates from XMP string Related: bug 458754, bug 461522 FIXED-IN: 7.9.0 M +1 -1 core/libs/metadataengine/engine/metaengine_gps.cpp https://invent.kde.org/graphics/digikam/commit/b7d61cad9f0bb72398fb1de405b741d01d050bab (In reply to Maik Qualmann from comment #9) > Git commit b7d61cad9f0bb72398fb1de405b741d01d050bab by Maik Qualmann. > Committed on 09/11/2022 at 18:20. > Pushed by mqualmann into branch 'qt5-maintenance'. > > fix get geolocation coordinates from XMP string > Related: bug 458754, bug 461522 > FIXED-IN: 7.9.0 > > M +1 -1 core/libs/metadataengine/engine/metaengine_gps.cpp > > https://invent.kde.org/graphics/digikam/commit/ > b7d61cad9f0bb72398fb1de405b741d01d050bab Sorry: not fixed in 7.9.0 (tested not working) but fixed in 8.0.0 Yes, that will also be fixed in digiKam-7.9.0. But the current test version available for download does not yet include this latest fix. A little patience until Gilles creates new packages. Maik yes, and a i cannot re-build a Windows target at the moment after an update on my Kubuntu 22.04 system: Qt libraries are not found anymore in MXE env... I investigate actually. (In reply to caulier.gilles from comment #12) > yes, and a i cannot re-build a Windows target at the moment after an update > on my Kubuntu 22.04 system: Qt libraries are not found anymore in MXE env... > I investigate actually. No impatience here at all. Thanks for the info and for the work done here. I'll update when it is available. Hi Maik, I created a new VM with XUbuntu 18.04 without any Qt installed on host, and Qt cross compiled detection work again. I suspect a mix between files from cmake used to check Qt presence between host and cross compiled env. It rest few tune to pass the installer compilation. I will fix it this evening. Gilles Hi Thierry, The new 7.9.0 Windows installer is finally compiled and ready to test, at usual place. Best Gilles Caulier And it works very nicely once I have made Digikam re-read the exif from the files. Many thanks ! |