Created attachment 180406 [details] GPS data of NEF-File *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY I have numerous NEF files (Nikon camera) in which the geoinformation is stored as GPS data in the metadata (e.g. GPS altitude, GPS position, etc.). If I look at the metadata in the ExifTool tab in the right-hand window, the data is available. Unfortunately, however, they are not displayed on the map. Even in the preview images, the images are not marked as containing geoinformation. However, if the image is converted to JPG, the data is visible and can also be edited. Am I making a mistake somewhere or do I have the wrong settings? I would appreciate a short help from you. Thx in advance. Otherwise, a happy Easter to you all. Greetings Stephan
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