<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello Jean-François and Michael -<br>
<br>
Thank you for your replies - I have a better understanding of how
Digikam operates now, and what you say makes sense. Re-reading the
metadata of the images don't seem to change anything unfortunately,
so it probably only considers the XMP section. I'll raise a bug for
this.<br>
<br>
Jean-François, I'm guessing that the software you use for
correlating .gpx tracks with images does write to the XMP fields?
What software is it?<br>
<br>
Thanks,<br>
Martin<br>
<br>
<div class="moz-cite-prefix">On 31/12/13 16:52, Jean-François
Rabasse wrote:<br>
</div>
<blockquote
cite="mid:alpine.LNX.2.00.1312311723080.29767@azrael.victoria.net"
type="cite">
<br>
Hi Martin,
<br>
<br>
Some comments, as I geotag images files from GPX tracks logs too,
<br>
using an external program.
<br>
<br>
On Tue, 31 Dec 2013, Martin Gerner wrote:
<br>
<br>
<blockquote type="cite">I used a piece of software to synchronize
.gpx files with .jpg photos,
<br>
with the effect of setting a number of GPS exif tags such as
GPSLatitude, GPSLongitude, etc (GPSversionID is 2.3.0.0). My
understanding is that geolocation tags can also be saved to "XMP
Exif" tags - these tags were
<br>
empty after synchronization.
<br>
</blockquote>
<br>
Yes, Exif properties « can be saved » into proper XMP Exif schema,
but this
<br>
isn't a law. It's up to the writing software to choose to update
data in
<br>
the Exif section, or the XMP section, or both.
<br>
If your GPS correlation software updates only the Exif section,
your
<br>
XMP data remain empty, or worse, can contain values from a
previous GPS
<br>
correlation done with a different software.
<br>
<br>
Digikam keeps images GPS position in its database. These values
will be
<br>
read when scanning for new images and reading their metadata, and
will be
<br>
updated when you edit positions, inside Digikam.
<br>
<br>
<blockquote type="cite">My suspicion at the moment is that the
geolocation window reads location data from the 'plain' EXIF
fields (and probably the XMP ones too), that
<br>
inconsistently the rest of the map views only read the XMP
fields, and that the reading of only the XMP fields is incorrect
as it doesn't seem
<br>
to match what other similar software does. It's a pain, since it
means that Digikam doesn't operate well together with other
software.
<br>
</blockquote>
<br>
No, Digikam functions don't read position data from Exif, or XMP,
but
<br>
from the Digikam database. So they use what has been loaded when
reading
<br>
images metadata.
<br>
<br>
But, when you write metadata to your images, or sidecar files,
database
<br>
values are also exported into the Exif XMP schema.
<br>
<br>
And that's why, when you edit internally, database values are
updated
<br>
then metadata is exported viw XMP schema :
<br>
<br>
<blockquote type="cite">If I change the location of the photos in
the geolocation window and apply
<br>
the changes (from within Digikam), I can see that the XMP EXIF
geolocation
<br>
fields are updated for the photos; after this, they show up fine
in the rest of the map views in Digikam.
<br>
</blockquote>
(Show up fine because the database has been updated, not because
the data
<br>
has been XMP exported.)
<br>
<br>
<br>
I agree with Michael saying :
<br>
<br>
On Tue, 31 Dec 2013, Michael G. Hansen wrote:
<br>
<br>
<blockquote type="cite">since you used external software to update
the EXIF data, it may be that
<br>
the database of digikam was not updated yet. You can select your
newly tagged photos and do Image->"Reread metadata from
images".
<br>
</blockquote>
<br>
You should check. If you first geocorrelate your images then start
Digikam
<br>
and get the images as new images, metadata will be read.
<br>
But if you geocorrelate images already managed in Digikam, you
have to
<br>
trigger « Reread metadata » so that Digikam updates its database.
<br>
<br>
<br>
As for compatibility with other software, my personal opinion is
that
<br>
consistency must be guaranteed. GPS positions should be edited
with one
<br>
and only one software, not different ones. This could ensure Exif
GPS
<br>
data, or XMP GPS data be the same.
<br>
<br>
Most software will be able to read data in a fixed order, Exif
data first
<br>
then XMP data. But I have no idea of what could they do, facing an
inconsistency. Could probably lead to weird results.
<br>
<br>
As for me, I never faced that kind of problem because I edit
positions
<br>
with an external program and writes only XMP Exif GPS data. So,
the
<br>
original Exif GPS data in my images are always empty.
<br>
And I use Digikam only to « see » positions, not to edit.
<br>
(Of course, rereading metadata is required when I update positions
from
<br>
outside.)
<br>
<br>
Regards, and Happy New Year :)
<br>
Jean-François
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Digikam-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Digikam-users@kde.org">Digikam-users@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/digikam-users">https://mail.kde.org/mailman/listinfo/digikam-users</a>
</pre>
</blockquote>
<br>
</body>
</html>