Digikam will not write Geolocation information to an XMP sidecar file; instead, a corrupt sidecar file is generated. If a sidecar file already exists, it is overwritten by the corrupt file. Reproducible: Always Steps to Reproduce: 0. Set Digikam to write metadata to sidecar files 1. Select image, open Geolocation dialog from Image menu 2. Drag image onto map 3. Click Apply Actual Results: XMP file is generated with only "<?xml version="1.0" encoding="UTF-8"?>" as the contents. Expected Results: Geolocation information is written to the XMP file.
It's probably relevant of Exiv2. Can you reproduce using Exiv2 command line tool ? Gilles Caulier
Sorry, I wouldn't know what parameters or options I should be giving the exiv2 command line tool.
I did a test with the same image in Geeqie. That too issued the same truncated XMP file when writing metadata. In the terminal window was the message: Error: XMP Toolkit error 4: Invalid UTF-8 sequence length Error: Failed to encode XMP metadata. Error: XMP Toolkit error 4: Invalid UTF-8 sequence length Error: Failed to encode XMP metadata. The image in question was taken by a Samsung Galaxy S3 which for some reason embeds the caption "ø;" (including two nonprintable characters) in every photo. I re-tested Digikam with an image from a Canon 550D (which embeds no such nonsense), and the bug did not occur. Googling these error messages turned up this: http://dev.exiv2.org/boards/3/topics/1073 Is it possible that exiv2 is being fed non-UTF-8 characters, triggering the error?
Andreas, Comment #3 is for you... Gilles Caulier
I understand to reproduce, one needs a special file which contains possibly invalid data in the XMP. Can you provide an image file for testing?
Created attachment 74761 [details] Image with strange value in EXIF User Comment field No problem, here you go. Shrunken from original but still exhibits the problem.
The attached photo does not seem to have any metadata, neither Exif, not IPTC, XMP nor a JPEG comment.
Not reproducible as provided image does not seem to have any metadata
New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ?
digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance.
This problem is not reproducible using last digiKam 5.0.0 + Exiv2 0.25. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier