[Digikam-users] loss of geoloc and other metadata when starting from Sony raw files

jon piesing jon33040 at yahoo.co.uk
Sun Apr 3 14:10:47 BST 2011


Has anyone seen problems losing geoloc and other metadata when starting from 
Sony raw files?

I've done some tests with a number of different workflows and have failed to 
find one which starts from a Sony raw file with geoloc information added in 
digikam and ends up with an EXIF file with GPS headers.

I've tried 3 different routes for converting from Sony ARW format - 1) digikam's 
"raw batch converter", 2) import in the digikam editor and 3) the dcraw command 
line utility.
I've tried 3 different routes for generating jpeg - 1) save as from the digikam 
editor, 2) "convert to jpeg" in the digikam batch queue manager and 3) upload it 
to flickr (which is where I want it to end up).

Here's a summary of the various combinations.
- Both digikam's "raw batch converter" and loses the both geoloc information and 
the caption in the raw file.
- Only conversion from raw using import in the digikam editor preserves the 
caption and the geoloc information 

- BUT, having converted from raw in the digikam editor, although digikam shows 
geoloc information in the right sidebar, it's not there in the EXIF. 

- When exported to flickr, the pictures converted from raw in the digikam editor 
have captions and none of the others. None of them have geoloc information.
- For curiosity, if I export to picasa, everything which the right sidebar in 
digikam shows as having geoloc information still has it in picasa

Is there any way to force digikam to write the geoloc information from its 
internal database to the EXIF data in a file?

I could understand the situation if adding geoloc information to Sony raw files 
in digikam simply didn't work at all. What I can't understand is that it half 
works - it's OK as far as digikam's internal database is concerned but not for 
the EXIF. It's OK for export to Picasa but not Flickr.

This is using digikam 1.9.0 on KDE 4.5.3. The information on the components used 
is below. The EXIF in the files has been inspected with the command line 'exif' 
utility for the jpegs and the Gnome image viewer 'eog' for other formats.



digiKam version 1.9.0
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: No
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibClapack: internal library
LibExiv2: 0.19
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.5.3 (KDE 4.5.3)
LibKExiv2: 1.1.0
LibKdcraw: 1.1.0
LibLCMS: 118
LibLensFun: external shared library
LibLqr: internal library
LibPGF: 6.09.44 - internal library
LibPNG: 1.2.42
LibQt: 4.7.0
LibRaw: 0.11.0-Beta7
LibTIFF: LIBTIFF, Version 3.9.2 Copyright (c) 1988-1996 Sam Leffler Copyright 
(c) 1991-1996 Silicon Graphics, Inc.
Marble widget: 0.10.3
Parallelised demosaicing: Yes
Database backend: QSQLITE
LibGphoto2: 2.4.8
LibKipi: 1.1.0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20110403/885d1344/attachment.html>

More information about the Digikam-users mailing list