https://bugs.kde.org/show_bug.cgi?id=522907
Alex Hirzel <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Alex Hirzel <[email protected]> --- Gery, thank you for the report! It would be helpful to upload an image that triggers this behavior, if you have it already and can share. Alternatively, one can be created by selectively removing tags from another image. It appears that KExiv2::setGPSInfo (in kexiv2gps.cpp) first calls removeGPSInfo (in the same file), which wipes out (among other things) the GPSInfo EXIF section as well as the GPSImgDirection, GPSImgDirectionRef, GPSDestBearing, GPSDestBearingRef fields from XMP. It seems that some of this would need to be saved to be re-written in setGPSInfo (which currently does not support compass bearings) or perhaps just not cleared in removeGPSInfo. A fix for this bug would need to define what data remains after setGPSInfo is called - for example, the receiver information? Alternatively, it could be worthwhile to define other methods for use by digikam (like updateGPSLatitude/Longitude) that would leave some fields unchanged (so that the "clearing" behavior of setGPSInfo can remain part of its function). Any thoughts on the desired fix Tobias? -- You are receiving this mail because: You are watching all bug changes.
