Bug 386591 - Cannot save changes in geolocation coordinates to .RW2 RAW files from a Panasonic FZ300 camera
Summary: Cannot save changes in geolocation coordinates to .RW2 RAW files from a Panas...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-GeolocationEdit (show other bugs)
Version: 5.7.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-06 16:48 UTC by ldlafleur
Modified: 2020-08-04 11:27 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.1.0
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description ldlafleur 2017-11-06 16:48:09 UTC 
Cannot save changes in geolocation coordinates to .RW2 RAW files from a Panasonic FZ300 camera. (Geolocation changes save successfully to RAW files from my other cameras.)

Details: When attempting to save changes in geolocation coordinates (using Apply button), window titled "Error - digiKam" pops up. Window states, "Failed to save some information". Under that is a list of file(s) with the statement "Unable to save changes to file" appended to each filename.
Comment 1 caulier.gilles 2017-11-06 19:18:17 UTC 
When you mean, saved to other format, which one exactly, and Where (file metadata or XMP sidecar).

RW2 raw format is just not supported by Exiv2 library used in background to R/W metadata to files. Only few ones are supported, as NEF, CR2, or ARW for ex...

Gilles Caulier
Comment 2 Maik Qualmann 2018-06-05 05:56:34 UTC 
*** Bug 395037 has been marked as a duplicate of this bug. ***
Comment 3 caulier.gilles 2020-08-04 08:08:00 UTC 
digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Best Regards

Gilles Caulier
Comment 4 ldlafleur 2020-08-04 11:15:16 UTC 
Bug seems to have been fixed in digiKam 7.0.0