XYplorer Beta Club

admin wrote: ↑02 Oct 2022 11:42 But this is still true: viewtopic.php?p=125412#p125412

Indeed! The raw data is ok. XY gives it back in a wrong way like in every third try. It is ok in every other software. And also XY can get the correct data. But not always.

Show me an example. What is the wrong way, and what is the right way?

...

Wait a moment, now I found a JPG file that gives different returns about every 10th time. WTF! I'll check that...

Totally weird. Can't explain. Could be a bug in GDI. The only way I can fix it is in the crudest way: I keep calling that value until it looks good.

It looks as something related to the length of data given back. Because there are more GPS IDs like from 0x0001 to 0x0007 and only the longest ones have this problem

0x0002 and 0x0004 AFAIK.

admin wrote: ↑02 Oct 2022 14:30 0x0002 and 0x0004 AFAIK.

Yes.

You wrote in the change log that the format was like "521623793/11930464 0/1 0/1". I get it rather like this: "47/1 31/1 79139/10000, 21/1 36/1 169200/10000" format called rational64u[3].

Anyway, I clicked on the Refresh column of my custom column many many times, I haven't got wrong value at all. Thanks!

Sure your numbers are different. You were at a different place when shooting.

Good it works now. So 5 tries are enough. Whenever you get a wrong number, tell me, and I raise to 6 times.

admin wrote: ↑02 Oct 2022 15:39 Sure your numbers are different. You were at a different place when shooting.

Good it works now. So 5 tries are enough. Whenever you get a wrong number, tell me, and I raise to 6 times.

The script works well. I was seeing if someone might know if it is possible to return the geolocation in decimal form rather than in degrees?

Nevermind, it seems I figured it out and just edited the exiftool command that was being used to include -n before it.