SUMMARY I have imported 50K+ pictures. None of the icons displays dimension. It shows 0x0 (0.00Mpx). STEPS TO REPRODUCE 1. Check the box at Settings | Configure digiKam | Icons tab | Show image dimensions 2. 0x0 (0.00Mpx) is shown for "all" the pictures in my collections. OBSERVED RESULT No image dimensions. No image dimension shown also in the exif data (Item Properties on the right hand side) EXPECTED RESULT Image dimension should be available and visible. SOFTWARE/OS VERSIONS Linux: Ubuntu 19.10 ADDITIONAL INFORMATION My digiKam version is digikam-7.0.0-beta3-20200309T071114-x86-64. I exported pictures from LR. Perhaps, this is a bug of LR export. LR could have deleted this data from exif. I am not sure.
What happens if you re-read the metadata on some images? Otherwise this problem can not be reproduced here, I am currently working on the Windows version of digiKam-7.0.0-Beta3. Maik
Note : if Exif was dropped from images with LR, there now way to extract image dim info without to decode image as well which will take age during import. So in this case the behavior is normal. Perhaps it's better to see "unknown" instead "0x0" in this kind of situation. Gilles Caulier
Re-reading metadata to the database brings the dimensions back. Thank you for the hint.
Perhaps, this bug should have been phrased this way: digikam not importing dimension data Re-reading data from files fixed the issue. As it seems, dimension data is available in the EXIF. Why didn't digiKam import dimension data during import?
DigiKam also reads dimension data during import. I can't say at the moment why it wasn't the case with you. How did you import images? Maik
I exported from LR with tags. Using exiftool, copied DateTimeOriginal to FileModifyDate. Imported to digiKam from a USB hard disk by creating auto folder (Year/Year-Month-Day format).
Maik, To get date from Exif with Import tool, the metadata handling option must be enabled in config dialog. Gilles
*** This bug has been marked as a duplicate of bug 424049 ***
Problem fixed with commit listed to https://bugs.kde.org/show_bug.cgi?id=424049#c13 ...and bugs closed : https://bugs.kde.org/show_bug.cgi?id=465312 https://bugs.kde.org/show_bug.cgi?id=465045