Cannot GPS correlate raw files

[Fabio]

Hi All,

I am using
DigiKam Version 3.1.0
Using KDE Development Platform 4.10.2
Platform is Windows 7


After running the gps correlator, when trying to save it I get "Unable to save changes to File"
same happens when manually finding a location and copying the location to the files.

It works fine when working with jpg files but not with RAW.
I am using a Nikon D5000. Raw files are .NEF.

I can use GpicSync to correlate the files, but it is a pain to switch between too many programs

Any help is appreciated


_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

RAW are read only files. GPS info are normally stored in digiKam DB
for read only files. It's work properly with my ARW files.

You can turn on XMP sidecar files management into digiKam metadata setup.

Gilles Caulier

2013/7/8 Fabio <[hidden email]>:

> Hi All,
>
> I am using
> DigiKam Version 3.1.0
> Using KDE Development Platform 4.10.2
> Platform is Windows 7
>
>
> After running the gps correlator, when trying to save it I get "Unable to
> save changes to File"
> same happens when manually finding a location and copying the location to
> the files.
>
> It works fine when working with jpg files but not with RAW.
> I am using a Nikon D5000. Raw files are .NEF.
>
> I can use GpicSync to correlate the files, but it is a pain to switch
> between too many programs
>
> Any help is appreciated
>
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Fabio]

RAW are read only files. GPS info are normally stored in digiKam DB
for read only files. It's work properly with my ARW files.

->
Thanks for the response.

1. If this is expected you might want to consider changing the reported error. For an end user, the error message "Unable to save changes to File" means something is wrong.

2. Since I can add the GPS location using other programs directly into the RAW file (GpicSync for example), I was expecting digiKam to be able to do the same. If I add a gps location to a raw file, I expect to be able to process my file into other formats, or use a different editor, and still be able to see the GPS info. Maybe you want to consider allowing this feature.

I know it is easy to ask but not so easy to actually do it... just my feedback. Thanks for your efforts

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2013/7/8  <[hidden email]>:
> RAW are read only files. GPS info are normally stored in digiKam DB
> for read only files. It's work properly with my ARW files.
>
> ->
> Thanks for the response.
>
> 1. If this is expected you might want to consider changing the reported error. For an end user, the error message "Unable to save changes to File" means something is wrong.
>
> 2. Since I can add the GPS location using other programs directly into the RAW file (GpicSync for example), I was expecting digiKam to be able to do the same. If I add a gps location to a raw file, I expect to be able to process my file into other formats, or use a different editor, and still be able to see the GPS info. Maybe you want to consider allowing this feature.

Aha. In fact RAW writing metadata support is delegate to a sub
component named Exiv2. Only few Raw tiff/ep based file format can be
updated. Look in digiKam/setup/metadata page. This option is disable
by default.

But i recommend to turn on XMP sidecar support which is more
dangerous. After all, RAW are digital negative and must be unchanged.

I don't know how other program do, but i suspect to use Exiftool in
background. In all case i must aware you about file alteration risk
here. Raw are proprietary format not documented. Thanks to camera
maker to build a big puzzle here. Writing metadata support is done
through reverse engineering. As usual in computer science, a bug is
always possible somewhere...

Gilles Caulier
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Remco Viëtor]

On Monday 08 July 2013 18:40:21 Gilles Caulier wrote:
> (...)
> Aha. In fact RAW writing metadata support is delegate to a sub
> component named Exiv2. Only few Raw tiff/ep based file format can be
> updated. Look in digiKam/setup/metadata page. This option is disable
> by default.
>
> But i recommend to turn on XMP sidecar support which is more
> dangerous. After all, RAW are digital negative and must be unchanged.
>
I suppose you mean to say '*less* dangerous' .. As indeed the RAW files are
comparable to negatives and irreplacable.

>(...)

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

2013/7/9 Remco Viëtor <[hidden email]>:

> On Monday 08 July 2013 18:40:21 Gilles Caulier wrote:
>> (...)
>> Aha. In fact RAW writing metadata support is delegate to a sub
>> component named Exiv2. Only few Raw tiff/ep based file format can be
>> updated. Look in digiKam/setup/metadata page. This option is disable
>> by default.
>>
>> But i recommend to turn on XMP sidecar support which is more
>> dangerous. After all, RAW are digital negative and must be unchanged.
>>
> I suppose you mean to say '*less* dangerous' .. As indeed the RAW files are
> comparable to negatives and irreplacable.

yes sure, I'm writing to fast (:=)))

Gilles Caulier
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Fabio]

But i recommend to turn on XMP sidecar support which is more
dangerous. After all, RAW are digital negative and must be unchanged.

-> I enabled the XMP sidecard for read only images and it resolved the error message.

Thanks for the help!!

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users