Question about {EXIF:Latitude}, {EXIF:Longitude}, {EXIF:Altitude}

[Tapio]

I updated XNConvert to the latest version.

Some problems...:

a) {EXIF:Altitude} - nothing does not show up in picture any more. In the older version it also wasn't good, because it displayed like "358.100" (ugly display, rounding needed) - but now Altitude not shown at all

b) {EXIF:Latitude}, {EXIF:Longitude} - before they were decimal ("51.1234, 7.8901"), now they are displayed in degrees, minutes, seconds. Why the change in format?

I was testing against the same source images I used in with the old .90 XNConvert version.

Thanks!

I wish for some conditional output. In foobar2000 for instance, [] are used. I.e.:

Code: Select all

[Blah $var bluh ]blubb

if $var not set, it displays "blubb" only.

[xnview]

a) {EXIF:Altitude} - nothing does not show up in picture any more. In the older version it also wasn't good, because it displayed like "358.100" (ugly display, rounding needed) - but now Altitude not shown at all

Thanks to your detailed description I can reproduce the problem.

b) {EXIF:Latitude}, {EXIF:Longitude} - before they were decimal ("51.1234, 7.8901"), now they are displayed in degrees, minutes, seconds. Why the change in format?

I was testing against the same source images I used in with the old .90 XNConvert version.

1.90??

I wish for some conditional output. In foobar2000 for instance, [] are used. I.e.:

Code: Select all

[Blah $var bluh ]blubb

if $var not set, it displays "blubb" only.

you can use

Code: Select all

((Blah $var bluh ))blubb

[Tapio]

Oh, thanks! Yes I used 1.90. It didn't notify me on an update (it's set to weekly), not sure if there's something wrong maybe.

Can you explain the conditional parsing? No matter what I do, see below, it displays the ()

Code: Select all

{IPTC:City}(( - {IPTC:Sublocation}))
{IPTC:City}( - {IPTC:Sublocation})

[xnview]

Oh, thanks! Yes I used 1.90. It didn't notify me on an update (it's set to weekly), not sure if there's something wrong maybe.

I have the same output in 1.94

Can you explain the conditional parsing? No matter what I do, see below, it displays the ()

Code: Select all

{IPTC:City}( - {IPTC:Sublocation})

In text tools?

[Tapio]

Oh, thanks! Yes I used 1.90. It didn't notify me on an update (it's set to weekly), not sure if there's something wrong maybe.

I have the same output in 1.94

Can you explain the conditional parsing? No matter what I do, see below, it displays the ()

Code: Select all

{IPTC:City}( - {IPTC:Sublocation})

In text tools?

Yes - I have my profile attached. This is how I convert my hi-res 4:3 camera pictures for use at my 16:9 4k TV.
EDIT: Cannot attach XBS file. Here it is:

Code: Select all

<?xml version="1.0" encoding="UTF-8"?><XnView_script version="1.0" name="HDTV_Camera_Ortsdaten_4K">
    <Resize mode="0" width="3840" height="2880" unit="0" ratio="true" orientation="false" enlarge="0" resample="7" gamma_correct="false"/>
    <Canvas_resize mode="0" width="3840" height="2160" unit="0" relative="false" ratio="true" orientation="false" color="#00000000" alpha="0" position="4"/>
    <Automatic_contrast/>
    <Automatic_levels active="false"/>
    <Text text="{IPTC:City} - {IPTC:Sublocation}&#10;{EXIF:Date Taken [d.m.Y, H:M]} Uhr" position="6" marginX="169" marginY="-158" angle="0" fontName="Arial Rounded MT Bold" fontSize="38" isBold="false" isItalic="false" isUnderline="false" isStrike="false" align="0" fontUnit="0" textColor="#ffffff" textOpacity="100" useBorder="false" borderColor="#000000" borderOpacity="0" borderSize="1" useFill="false" fillColor="#000000" fillOpacity="40" useOutline="true" outlineColor="#dfdfdf" outlineSize="0.5" useShadow="true" shadowColor="#000000" shadowOffsetY="20" shadowOffsetX="20" shadowBlur="8"/>
    <Text text="{Folder name}, {EXIF:Make} {EXIF:Model}" position="6" marginX="169" marginY="-130" angle="0" fontName="Arial Rounded MT Bold" fontSize="14" isBold="false" isItalic="false" isUnderline="false" isStrike="false" align="1" fontUnit="0" textColor="#ffffff" textOpacity="100" useBorder="false" borderColor="#000000" borderOpacity="100" borderSize="1" useFill="false" fillColor="#000000" fillOpacity="100" useOutline="false" outlineColor="#000000" outlineSize="1" useShadow="true" shadowColor="#000000" shadowOffsetY="2" shadowOffsetX="2" shadowBlur="2"/>
    <Text text="{EXIF:Latitude}, {EXIF:Longitude}" position="6" marginX="3" marginY="3" angle="0" fontName="Arial Rounded MT Bold" fontSize="13" isBold="false" isItalic="false" isUnderline="false" isStrike="false" align="0" fontUnit="0" textColor="#000000" textOpacity="100" useBorder="false" borderColor="#000000" borderOpacity="100" borderSize="1" useFill="false" fillColor="#000000" fillOpacity="100" useOutline="true" outlineColor="#ffffff" outlineSize="4" useShadow="false" shadowColor="#ffffff" shadowOffsetY="5" shadowOffsetX="5" shadowBlur="3"/>
    <Output folder="M:/Bilder/Google Photos" filename="{Current Date [Ymd]}\{Filename}" case="1" startIndex="1" format="JPEG">
        <Options overwrite="0" orgDate="true" keepMeta="false" keepICC="false" keepFolder="false" keepParentFolder="false" keepExtension="true" delOrg="false" multipage="false" allPages="false" openExplorer="true" openBrowser="false" clearItems="false"/>
        <JPEG quality="98" progressive="false" optimizeHuffman="true" rebuildThumb="true" orgQuality="false" DCTMethod="2" subSampling="2" smoothFactor="0"/>
    </Output>
</XnView_script>

[xnview]

Yes - I have my profile attached. This is how I convert my hi-res 4:3 camera pictures for use at my 16:9 4k TV.

Ok, i can reproduce (sometimes), latitude & longitude as decimal is a bug. so i add another template field

[xnview]

This problem is supposed to be fixed in XnView MP 0.99.4. Please check and confirm the bug fix here.

[Tapio]

Hi,

thx for the fixes.

- Altitude: Fixed, BUT to be useful, builtin rounding or a rounding function is needed. Displaying e.g. 48.124m is not useful on pictures.
- Lat/Lon: fixed. Can you please increase the precision to a 5. digit? Lat/lon with 4 digits is something around the 15m, not too precise. A 5. digit is still more than reasonable as for the string length, but adds to the precision.

Best regards