Bug 516762 - OM System .orf location absent from map module
Summary: OM System .orf location absent from map module
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Gps (other bugs)
Version First Reported In: 8.8.0
Platform: macOS (DMG) macOS
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-02-26 16:40 UTC by stewart.logie
Modified: 2026-02-28 03:14 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 9.0.0
Sentry Crash Report:


Attachments
attachment-1822201-0.html (2.51 KB, text/html)
2026-02-26 20:11 UTC, stewart.logie
Details
attachment-1843358-0.html (1.91 KB, text/html)
2026-02-26 21:31 UTC, stewart.logie
Details

Note You need to log in before you can comment on or make changes to this bug.
Description stewart.logie 2026-02-26 16:40:10 UTC
SUMMARY

OM System .orf raw files with GPS data (as verified by the ExifTool in digiKam Metadata tab) do not appear in the map module.

A companion jpg file shows in the map module.

digiKam shows the GPS data in the metadata tab, but not in the map view. 
Forcing digiKam to reread metadata does not help. digiKam version 8.8.0 ExifTool version 13.51

STEPS TO REPRODUCE
1. Import .orf raw file with gps metadata into digiKam
2. Verify that GPSLatitude and GPSLongitude have correct data in Metadata tab


OBSERVED RESULT
 Inspect Map tab and notice "No Geolocation Information Available"

EXPECTED RESULT
 Inspect Map tab and see location displayed on map

SOFTWARE/OS VERSIONS
Windows: 
macOS: 26.3
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Maik Qualmann 2026-02-26 19:15:04 UTC
Please provide a sample OM System image that can reproduce the problem. You could upload it to a cloud service or send it by email. My sample OM System *.orf images all lack GPS information. With Olympus *.orf images that do contain GPS information, there are no problems with digiKam.

Maik
Comment 2 stewart.logie 2026-02-26 19:51:31 UTC
Hi Maik,
Try this one.

-Stewart


On Thu, Feb 26, 2026 at 11:15 AM Maik Qualmann <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=516762
>
> Maik Qualmann <metzpinguin@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |metzpinguin@gmail.com
>
> --- Comment #1 from Maik Qualmann <metzpinguin@gmail.com> ---
> Please provide a sample OM System image that can reproduce the problem. You
> could upload it to a cloud service or send it by email. My sample OM System
> *.orf images all lack GPS information. With Olympus *.orf images that do
> contain GPS information, there are no problems with digiKam.
>
> Maik
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 stewart.logie 2026-02-26 20:11:25 UTC
Created attachment 190138 [details]
attachment-1822201-0.html

Hi Maik,
Try this one.

 _2250540.ORF
<https://drive.google.com/open?id=1UIncVBwbeK05Gkbsl-CJnYPtghWaDWWX>


On Thu, Feb 26, 2026 at 11:15 AM Maik Qualmann <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=516762
>
> Maik Qualmann <metzpinguin@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |metzpinguin@gmail.com
>
> --- Comment #1 from Maik Qualmann <metzpinguin@gmail.com> ---
> Please provide a sample OM System image that can reproduce the problem. You
> could upload it to a cloud service or send it by email. My sample OM System
> *.orf images all lack GPS information. With Olympus *.orf images that do
> contain GPS information, there are no problems with digiKam.
>
> Maik
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 4 Maik Qualmann 2026-02-26 20:51:09 UTC
In digiKam-8.8.0, I can only reproduce the problem if ExifTool is enabled for reading metadata in the digiKam metadata settings. If reading metadata with ExifTool is disabled and a re-read of the metadata from the file is performed, geolocation is present.

Is this the case for you?

However, the problem is fixed in the pre-release of digiKam-9.0.0.

Maik
Comment 5 stewart.logie 2026-02-26 21:31:45 UTC
Created attachment 190142 [details]
attachment-1843358-0.html

Correct. If I disable ExifTool and perform a re-read, then the geolocation
is present.
Glad to hear that digiKam-9.0.0 has this fixed.
Thanks so much for your help

*-Stewart*




On Feb 26, 2026, at 12:51 PM, Maik Qualmann <bugzilla_noreply@kde.org>
wrote:

https://bugs.kde.org/show_bug.cgi?id=516762

--- Comment #4 from Maik Qualmann <metzpinguin@gmail.com> ---
In digiKam-8.8.0, I can only reproduce the problem if ExifTool is enabled
for
reading metadata in the digiKam metadata settings. If reading metadata with
ExifTool is disabled and a re-read of the metadata from the file is
performed,
geolocation is present.

Is this the case for you?

However, the problem is fixed in the pre-release of digiKam-9.0.0.

Maik