Timezonesetting in Metadata2 ignores setting in pictures

[Viscus]

With the one of the updates it changed also the behaviour from the import the Timezone Information.
Even when in the picture is a timezone set, imatch will set also his timezone.
So i have now two timezones in the time field.

An example. In the import i set the timezone as +02:00 but the picture is set with +01:00

ExifViewer tells

[Composite]     Create Date                     : 2017:11:29 15:49:10+01:00
[Composite]     Date/Time Original              : 2017:11:29 15:49:10+01:00

The Field Date Digitazed tells: 2017:11:29 15:49:10+01:00+02:00
Date Created: 2017:11:29 15:49:10+01:00+02:00

if i change the import setting to +01:00 and reinforce the import.
i have
Field Date: 2017:11:29 15:49:10+01:00+01:00
Date Created: 2017:11:29 15:49:10+01:00+01:00

Version 2017.11.4

[Mario]

This may be related to another issue (time zone detection in string formats) I'm already investigating.
Please provide a small example image which exhibits the problem and attach.

[Viscus]

The cause is here in a Canon RAW Picture and its of a size of 23MB. I can post it on a downloadlink for you.
Should sent the link on your support mail address?

[Mario]

You can send the link to my support email.
Please include a link back to this thread in your email because I deal with 50 or so emails per day...

[Mario]

Thanks for sending the file. IMatch is correct in this case.
If you look at the metadata in your file, you see that it has time-zone information already embedded:

[EXIF:IFD0]     ModifyDate                      : 2017:12:03 17:33:49
[EXIF:ExifIFD]  DateTimeOriginal                : 2017:11:29 15:49:10
[EXIF:ExifIFD]  CreateDate                      : 2017:11:29 15:49:10
[EXIF:ExifIFD]  OffsetTime                      : +01:00
[EXIF:ExifIFD]  OffsetTimeOriginal              : +01:00
[EXIF:ExifIFD]  OffsetTimeDigitized             : +01:00
[MakerNotes:Canon] TimeZone                     : +01:00
[MakerNotes:Canon] TimeZoneCity                 : Paris
[MakerNotes:Canon] DaylightSavings              : Off

This means that ExifTool uses this time-zone and returns it as part of the time stamp.
The time-zone override you can set under Edit > Preferences > Metadata 2 is only applied if the Exif / IPTC timestamps have no time-zone already applied.

Proof: Removing the TimeZoneOffsets in the file from the EXIF data and then re-importing the file applied the manual time-zone offsets configured in IMatch correctly.

[Viscus]

Thanks a lot for your hint. I would investigate it further. I'm wondering only because the problem startet with an Update of Imatch. And copying the information to a .jpg is not a problem. Strange.

[Mario]

There was no change in this area for a long time. Maybe ExifTool added support for the time-zone offsets in a release. Or your camera started writing them. Or ExifTool added an implicit support for the proprietary Canon timeZone maker note - and maps this info into the corresponding EXIF time zone offsets - which would a intelligent thing to do.

If camera vendors would stop using the 40 year old EXIF data (and adding more and more proprietary and undocumented stuff to it) and would instead use XMP metadata, all these problems would be solved. All XMP time stamps have time zone support. Camera vendors could store all their proprietary data in a nicely encapsulated XMP namespace. Every XMP-aware application would be able to see and display the maker notes, even if it does not understand them. No more damaged files because of proprietary maker notes storing hard-coded offsets etc.

But camera vendors only care for the buck, not for their users. And users don't care at all and let them get away with it.

[Viscus]

I had no change from the camera vendor. I didn't made an Upgrade.
The original image is without any information.
But you're right there is a new exiftool Version.

But i know now from where the problem is coming. In the Settings under Metadata are the options to set the correct timezone settings.
But only if nothing is set. But know it sets the timezone also even there is already an information in the XMP File.
If i remove this everything is working fine. The double entry is away.
And btw it is not a Canon specific problem. I had from a course some Olympus Raw files. Also i have here the same behaviour.
This happens when i change the timezone settings after the first import and a new reimport.