<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div>Hi,<br><br>Has anyone seen problems losing geoloc and other metadata when starting from Sony raw files?<br><br>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.<br><br>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.<br>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).<br><br>Here's a summary of the various combinations.<br>- Both digikam's "raw batch
converter" and loses the both geoloc information and the caption in the raw file.<br>- Only conversion from raw using import in the digikam editor preserves the caption and the geoloc information <br>- 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. <br>- 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.<br>- For curiosity, if I export to picasa, everything which the right sidebar in digikam shows as having geoloc information still has it in picasa<br><br>Is there any way to force digikam to write the geoloc information from its internal database to the EXIF data in a file?<br><br>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.<br><br>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.<br><br>Thanks<br><br>Jon<br>---------------------------------------------------------------------------------<br>digiKam version 1.9.0<br>Exiv2 can write to Jp2: Yes<br>Exiv2 can write to Jpeg: Yes<br>Exiv2 can write to Pgf: No<br>Exiv2 can write to Png: Yes<br>Exiv2 can write to Tiff: Yes<br>Exiv2 supports XMP metadata: Yes<br>LibCImg: 130<br>LibClapack: internal library<br>LibExiv2: 0.19<br>LibJPEG: 62<br>LibJasper: 1.900.1<br>LibKDE: 4.5.3 (KDE 4.5.3)<br>LibKExiv2: 1.1.0<br>LibKdcraw: 1.1.0<br>LibLCMS: 118<br>LibLensFun: external shared library<br>LibLqr: internal library<br>LibPGF: 6.09.44 -
internal library<br>LibPNG: 1.2.42<br>LibQt: 4.7.0<br>LibRaw: 0.11.0-Beta7<br>LibTIFF: LIBTIFF, Version 3.9.2 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc.<br>Marble widget: 0.10.3<br>Parallelised demosaicing: Yes<br>Database backend: QSQLITE<br>LibGphoto2: 2.4.8<br>LibKipi: 1.1.0<br><br></div>
</div></body></html>