Bug 458754 - Geolocation of JPEG shown in Map vary of 100 meters from the correct position set in RAW
Summary: Geolocation of JPEG shown in Map vary of 100 meters from the correct position...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Geolocation-Places (show other bugs)
Version: 7.8.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-05 17:04 UTC by Bernd
Modified: 2022-11-09 18:22 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.9.0


Attachments
Jpg with incorrect Position (592.50 KB, image/png)
2022-09-05 17:04 UTC, Bernd
Details
RAW with correct position (555.90 KB, image/png)
2022-09-05 17:05 UTC, Bernd
Details
GPS-Data in JPG (12.27 KB, image/png)
2022-09-05 17:06 UTC, Bernd
Details
GPS-data in RAW (12.38 KB, image/png)
2022-09-05 17:06 UTC, Bernd
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernd 2022-09-05 17:04:35 UTC
Created attachment 151847 [details]
Jpg  with incorrect Position

SUMMARY
***
The Position of RAW (ORF) shown in the map is correkt.
The position of the JPEG with thame Data shown in the map varys some 100 meters.
***


STEPS TO REPRODUCE
1. Import RAW and JPEG with the same GPS-Data in digikam
2. The position in MAP (Karte) is different.
3. Raw ist shown on the exact position in the map (No matter of the kind of map (google osm))
4. JPG ist shown on wrong position in the map, differssome 100 meters from exact position (No matter of the kind of map (google, osm))






SOFTWARE/OS VERSIONS
Windows: 11 home/pro
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Bug is longer in Digikam, my first version was 6.3, now 7.8.0
Comment 1 Bernd 2022-09-05 17:05:40 UTC
Created attachment 151848 [details]
RAW with correct position
Comment 2 Bernd 2022-09-05 17:06:13 UTC
Created attachment 151849 [details]
GPS-Data in JPG
Comment 3 Bernd 2022-09-05 17:06:40 UTC
Created attachment 151850 [details]
GPS-data in RAW
Comment 4 caulier.gilles 2022-09-05 17:13:55 UTC
Please share the JPEG and the RAW files using cloud for future investiguations.

It's possible that JPEG includes GPS position outside Exif as XMP for exemple, and it can be problematic.

A view of complete GPS values from JPEG and RAW using exiv2 command line tool (not exiftool) can help to see if a diff exists somewhere. Exiv2 library is used to extract these information from image with 7.x releases.

Gilles Caulier
Comment 5 Maik Qualmann 2022-09-06 11:05:08 UTC
My Nikon uses a paired smartphone for GPS positioning. A test here with a RAW+JPG image shows, as expected, no difference in the GPS position between the RAW and JPG image.
We absolutely need a RAW+JPG sample image.

Maik
Comment 6 caulier.gilles 2022-09-06 11:10:10 UTC
Do you have any xmp sidecar shared between JPEG and RAW ?
Comment 7 Bernd 2022-09-06 16:09:24 UTC
Link to the Pictures:
https://1drv.ms/u/s!AlW6BV2k9radhEsxP7dJINxrUfOt?e=byHlAn
Comment 8 Bernd 2022-09-06 16:16:32 UTC
No, no sidecars. GPS is directly in RAW and after development with dxo in JPG. any oter Program shows the JEP on the exact location on maps.

I posted the Link to the sample-files a few minutes ago. Here it is again:
https://1drv.ms/u/s!AlW6BV2k9radhEvJGpJ2pvPkz0y1?e=KAS3Pj

Am 06.09.2022 um 13:10 schrieb bugzilla_noreply@kde.org:
> https://bugs.kde.org/show_bug.cgi?id=458754
>
> --- Comment #6 from caulier.gilles@gmail.com ---
> Do you have any xmp sidecar shared between JPEG and RAW ?
>
Comment 9 Maik Qualmann 2022-09-06 17:06:32 UTC
Thank you for the sample images. The positions are identical here. But, the altitude in the XMP metadata of the JPG image is wrong, 709 m to 70.9 m. If I understand correctly, the XMP metadata was created with DxO and ExifTool 12.34 as toolkit. In digiKam we first look at the XMP-GPS metadata, since these are probably more up-to-date for possible sidecar use. The difference occurs because your XMP metadata is incorrect, probably written by DxO.

Maik
Comment 10 Maik Qualmann 2022-11-06 21:43:18 UTC
*** Bug 461522 has been marked as a duplicate of this bug. ***
Comment 11 Maik Qualmann 2022-11-09 18:22:29 UTC
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 461522, bug 461633
FIXED-IN: 7.9.0

M  +1    -1    core/libs/metadataengine/engine/metaengine_gps.cpp

https://invent.kde.org/graphics/digikam/commit/b7d61cad9f0bb72398fb1de405b741d01d050bab