Summary: | Exif GPS metadata lost | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Sadi <sadiyumusak> |
Component: | General | Assignee: | amyspark <amy> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | amy, halla |
Priority: | NOR | ||
Version: | 4.4.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/graphics/krita/commit/9c59a7a05167c671e1171bdb163562f6e8742586 | Version Fixed In: | |
Sentry Crash Report: | |||
Attachments: | a sample jpeg file with GPS metada |
Description
Sadi
2021-03-14 13:23:41 UTC
* please provide such a file so we can try to reproduce. * which file format do you use to save in? (In reply to Halla Rempt from comment #1) Any jpg file with gps data... So, provide one, because I don't have any jpg file with gps data _and_ answer my question. Created attachment 136664 [details]
a sample jpeg file with GPS metada
(In reply to Halla Rempt from comment #3) Opening any jpg file with EXIF GPS metadata, editing and then saving it in the same jpg format with the same or different name results in the loss of GPS info. Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. Confirming. Our code does not parse Exif.GPSInfo structure at all, so it gets lost on import. A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1000 Git commit 9c59a7a05167c671e1171bdb163562f6e8742586 by Halla Rempt, on behalf of L. E. Segovia. Committed on 16/08/2021 at 13:41. Pushed by rempt into branch 'master'. kisexiv2: support GPSInfo Exif structure M +3 -1 libs/ui/kisexiv2/kis_exif_io.cpp M +40 -11 libs/ui/kisexiv2/kis_exiv2.cpp https://invent.kde.org/graphics/krita/commit/9c59a7a05167c671e1171bdb163562f6e8742586 |