Bug 479949 - Reverse Geo Coding does not write (anymore) geo metadata into XMP fields for jpeg from a Google Pixel 5
Summary: Reverse Geo Coding does not write (anymore) geo metadata into XMP fields for ...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Geolocation-ReverseGeoCoding (show other bugs)
Version: 8.2.0
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-17 15:49 UTC by mahikeulbody
Modified: 2024-01-17 17:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 8.3.0


Attachments
debug log file (47.50 KB, text/x-log)
2024-01-17 16:40 UTC, mahikeulbody
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mahikeulbody 2024-01-17 15:49:50 UTC
SUMMARY
Reverse Geo Coding does not write geo metadata into XMP fields for jpeg from a Google Pixel 5, only into IPTC fields.
It writes them into both XMP and IPTC fields for jpeg from a Motorola G6.

That seems a regression since I have older jpeg from the same Pixel 5 with fulfilled XMP geo tags.
Comment 1 caulier.gilles 2024-01-17 16:16:33 UTC
Which Exiv2 library version do you use ? Look in Help/Components Info for details.

You can switch from Exiv2 to Exiftool backend to write this kind of metadata in JPEG. Look Setup/Metadata for details:

https://docs.digikam.org/en/setup_application/metadata_settings.html#behavior-settings

Gilles Caulier
Comment 2 mahikeulbody 2024-01-17 16:25:04 UTC
(In reply to caulier.gilles from comment #1)
> Which Exiv2 library version do you use ?

0.28.1

> You can switch from Exiv2 to Exiftool backend to write this kind of metadata
> in JPEG. Look Setup/Metadata for details:

"delegate to exiftool backend ..." option is already set on my config.
Comment 3 caulier.gilles 2024-01-17 16:27:52 UTC
Go to setup/mics/system and enable debug traces :

https://docs.digikam.org/en/setup_application/miscs_settings.html#system-settings

Restart digiKam from a console. You will see plenty of traces while application is running. Repeat the defective operation and capture the corresponding traces.

Gilles Caulier
Comment 4 mahikeulbody 2024-01-17 16:40:57 UTC
Created attachment 164988 [details]
debug log file
Comment 5 caulier.gilles 2024-01-17 16:43:19 UTC
It's clear:

digikam.metaengine: ExifTool "Load Metadata" "-json -G:0:1:2:4:6 -l /home/michel/Images/en_attente/Pixel_5/PXL_20240117_153120023.jpg"
digikam.metaengine: Loading metadata with "Exiv2" backend from "/home/michel/Images/en_attente/Pixel_5/PXL_20240117_153120023.jpg"
digikam.general: Metadata loading with Exiv2 took 2 ms ( true )
digikam.general: "Standard Exif Tags" decoding took 0 ms ( false )
digikam.general: "MakerNote Exif Tags" decoding took 0 ms ( false )
digikam.general: "IPTC Records" decoding took 0 ms ( false )
digikam.general: "XMP Schema" decoding took 0 ms ( false )
digikam.metaengine: Cannot get Xmp metadata tag title with Exiv2:  (Error # 36 :  "No namespace info available for XMP prefix `Item'"
digikam.metaengine: Cannot get Xmp metadata tag title with Exiv2:  (Error # 36 :  "No namespace info available for XMP prefix `Item'"
digikam.metaengine: Cannot get Xmp metadata tag title with Exiv2:  (Error # 36 :  "No namespace info available for XMP prefix `Item'"
digikam.metaengine: Cannot get Xmp metadata tag title with Exiv2:  (Error # 36 :  "No namespace info available for XMP prefix `Item'"
digikam.metaengine: Cannot get Xmp metadata tag title with Exiv2:  (Error # 36 :  "No namespace info available for XMP prefix `Item'"

File is read and metadata chunck is passed to Exiv2 which cannot parse the contents...

Gilles Caulier
Comment 6 mahikeulbody 2024-01-17 16:52:11 UTC
(In reply to caulier.gilles from comment #5)
> It's clear:
> File is read and metadata chunck is passed to Exiv2 which cannot parse the contents...

Couldn't this be a regression of Exiv2 since I have older jpegs of the same Pixel 5 that are correctly tagged ?

The only other alternative would be a wrong Google update of their camera app.
Comment 7 caulier.gilles 2024-01-17 17:02:32 UTC
For Exiv2 regression, it's simple to verify: use the command line tool from Exiv2 and try to parse XMP metadata, like this :

exiv2 -px my_gg_pixel5.jpeg

Gilles Caulier
Comment 8 caulier.gilles 2024-01-17 17:03:50 UTC
If exiv2 CLI tool report and exception, well report this problem to Exiv2 issues:

https://github.com/Exiv2/exiv2/issues

Gilles Caulier
Comment 9 Maik Qualmann 2024-01-17 17:07:30 UTC
Fixed with Bug 478899

Pre-release digiKam-8.3.0:

https://files.kde.org/digikam/

Maik
Comment 10 mahikeulbody 2024-01-17 17:11:48 UTC
(In reply to caulier.gilles from comment #8)
> If exiv2 CLI tool report and exception, well report this problem to Exiv2
> issues:
> 
> https://github.com/Exiv2/exiv2/issues
> 
> Gilles Caulier
No exception :

Xmp.hdrgm.Version                            XmpText     3  1.0
Xmp.xmpNote.HasExtendedXMP                   XmpText    32  E387B24F1C1301EF8B68775866224573
Xmp.Container.Directory                      XmpText     0  type="Seq"
Xmp.Container.Directory[1]                   XmpText     0  type="Struct"
Xmp.Container.Directory[1]/Container:Item    XmpText     0  type="Struct"
Xmp.Container.Directory[1]/Container:Item/Item:Mime XmpText    10  image/jpeg
Xmp.Container.Directory[1]/Container:Item/Item:Semantic XmpText     7  Primary
Xmp.Container.Directory[2]                   XmpText     0  type="Struct"
Xmp.Container.Directory[2]/Container:Item    XmpText     0  type="Struct"
Xmp.Container.Directory[2]/Container:Item/Item:Semantic XmpText     7  GainMap
Xmp.Container.Directory[2]/Container:Item/Item:Mime XmpText    10  image/jpeg
Xmp.Container.Directory[2]/Container:Item/Item:Length XmpText     5  87288