| Summary: | How do I get digikam to take the geoinformation from NEF files into account? | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Kurpfaelzer <Stephan.Kranz> |
| Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.7.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.7.0 | |
| Sentry Crash Report: | |||
| Attachments: |
GPS data of NEF-File
Metadata settings |
||
|
Description
Kurpfaelzer
2025-04-19 14:39:27 UTC
Did you try to enable ExifTool backend instead Exiv2 ? https://docs.digikam.org/en/setup_application/metadata_settings.html#behavior-settings (In reply to caulier.gilles from comment #1) > Did you try to enable ExifTool backend instead Exiv2 ? > > https://docs.digikam.org/en/setup_application/metadata_settings. > html#behavior-settings Yes, I already enabled ExifTool backend instead of Exiv2. Created attachment 180413 [details]
Metadata settings
ok now force to reread file metadata to sync database using menu Item/Reread Metadata From File... I did it - but unfortunately no change https://magentacloud.de/s/4KPZWRtBZ7Ey2Lc above you will find a link to an example-picture. One as NEF-File while the other is the same picture as a JPEG-file. The cause is that metadata reading is enabled with ExifTool. ExifTool doesn't seem to be transferring the GPS information to our EXV container. I'll look into it. Maik The problem is clear. Nikon Z* images generally border on the 64k Exif limit. When ExifTool copies the metadata into an EXV container, it exceeds the 64k limit and creates a multi-segment Exif file. Currently, only ExifTool itself or Adobe can read this Exif metadata, so Exiv2 results in error messages and the GPS information and MakerNotes cannot be read. I don't see any solutions at the moment; we would have to omit certain elements when creating the EXV container, such as the preview image. I recommend not using ExifTool to read the metadata for these images. By the way, commercial software also has this problem, for example, when creating JPG images from NEF and copying the metadata. Maik Thank you very much for your explanations, which I am happy to take note of. Unfortunately, I can't categorise them technically as I don't have the necessary programming knowledge and insights in ExifTool/EXIV2. Just for your information: I use Luminar neo and have used it to convert the NEF file to JPEG (after a few image enhancements). The GPS information has been transferred unchanged, as can be seen from my two sample images. GeoSetter is also able to interpret the GPS data from the NEF file correctly (In this context, I would like to refer again to my idea from bug 495599). Stephan digiKam can also read the geolocation information in your NEF files if you disable reading with ExifTool in the digiKam metadata settings. You can leave the writing with ExifTool option enabled. Don’t forget to reread the metadata from the NEF files. Maik Ok, thanks for the hint. I've just tried it out and it actually works. Many thanks - and I've learnt something again (about/from digikam). Stephan I mark this file as resolved now. Best regards |