Page 1 of 1

XnViewMP 0.48 : some problems with XMP Location field

Posted: Thu Apr 19, 2012 3:25 pm
by mahikeulbody
IPTC/XMP Source Panel Editor shows a 'Content Location Name' field (as a list) and a 'Sublocation' field (as a string).

It is a little bit confusing because :

- If you set a value into Sublocation Editor field, the value is written in the file into a iptc4xmpCore:Location field. It is right since there is no more sublocation field (it is deprecated) but it would be less confusing to call this field "Location" into the IPTC/XMP Editor.

- The value is also written in the file into a photoshop:Location field. It is not wrong but it is strongly recommended to avoid to duplicate XMP information (of course it is allowed to duplicate it if you set XMP and IPTC metadata into the file).

- If you set a value into 'Content location Name' Editor field, the value is also written in the file within the iptc4xmpCore:Location field. Why ? Moreover, according to XMP standard 'Content Location Name' is part of the old IIMv4 schema and is used only by iView.

- If the value set into 'Content location Name' Editor field has several words (such as "71 rue Pierre"), each of them is shown as a different value into the windows but only the first one is written to the file (in the Location field).

- If I erase the Sublocation Editor field, the value into the file is not erased.

Re: XnViewMP 0.48 : some problems with XMP Location field

Posted: Thu Apr 19, 2012 3:38 pm
by xnview
So which changes must be made (the problem is IPTC support list of 'Content Location Name' not XMP)

Re: XnViewMP 0.48 : some problems with XMP Location field

Posted: Thu Apr 19, 2012 3:57 pm
by mahikeulbody
I suggest :

- to inhibit 'Content Location Name' if 'XMP only' is set
- if 'XMP only' is not set and a value for 'Content Location Name' is typed, there are two cases :
* the standard defines a mapping with XMP (but it would be surprinsing since according XnViewMP 'Content Location Name' field is a list when Sublocation is a string) ; XnViewMP applies this mapping
* the standard doesn't define a mapping with XMP ; in this case, XnViewMP doesn't write this value into iptc4xmpCore:Location field
- to rename 'Sublocation' field as 'Location field'
- to allow to erase 'Sublocation' field in the file if erased into the Editor

I don't know if 'Content Location Name' field is a list or a string (I am not using IPTC) but anyway there is a problem if you type many words (see my post).

Re: XnViewMP 0.48 : some problems with XMP Location field

Posted: Thu Apr 19, 2012 5:23 pm
by mahikeulbody
I think photohop:location field doesn't exist. Exiftool can display it but it cannot write (if so, which is the tag name ?). Anyway the field is not documented neither on Exiftool site or Adobe site.

Re: XnViewMP 0.48 : some problems with XMP Location field

Posted: Fri Apr 20, 2012 3:15 am
by mahikeulbody
http://www.metadataworkinggroup.org/pdf ... idance.pdf contains a chapter related to the way to manage Location items between the different standards (EXIF, IIM, XMP).

Re: XnViewMP 0.48 : some problems with XMP Location field

Posted: Fri Apr 20, 2012 8:36 am
by mahikeulbody
The § 5.8.4 of the document (see my post above) shows an array which explains the mess. For example, according to IPTC Core 1.0, City is mapped on photoshop:City but this is obsolete now ! IPTC 1.1 defines City has to be mapped on a new IPTC Extension field City.


In the latest specification (IPTC Extension 1.1), the IPTC has moved to a set of definitions that clearly
differentiates between camera location and subject location defining both “Location Created” and
“Location Shown” as a set of hierarchical properties (World Region, Country Name/ISO Country code,
Province or State, City and Sublocation). The older [ambiguous] location definition (IPTC Core 1.0) is
to be treated as legacy.