well, as I said in my last post, if I read the exif with this command :
`exiv2 -pv misplaced.jpg | grep GPS`

I do read `N` and `W` for latitude and longitude Ref so exifs match with officials standards.

What does Zenphoto show for these values?

`
Latitude: 46,68505
Latitude de référence: N,
Longitude: 73,01671662037
Longitude de référence: W-
Altitude: 301m
Altitude de référence: 006fb585
`
The picture is located in the middle of Kazakhstan instead of Canada. The longitude ref is not interpreted so E is set by default.

What this indicates is that there is an extra character in the longitude reference, the hyphen and the latitude reference, the comma. Zenphoto simply extracts what is there.

Hi,

both ref fields have length 2 (including the 0-byte) according to exiv2 output. Here is the hexdumped binary exif data from the image (using exiftool and hexdump -C):

`

000028e0 00 00 00 01 00 02 00 00 00 02 4e 00 2c 8b 00 02 |..........N.,...|

000028f0 00 05 00 00 00 03 00 00 02 0e 00 03 00 02 00 00 |................|

00002900 00 02 57 00 2d 99 00 04 00 05 00 00 00 03 00 00 |..W.-...........|

`

So it looks like some function in the pipeline stripped the 0-byte and added the following byte instead.

This may not happen always. I had the problem with an image yesterday but new generated jpegs from the same raw show up correctly in zenphoto.

Andreas

also the altitude reference seems to be messed up in zenphoto...

Andreas

A GPS exif is =< 12 bytes long :
2 bytes Tag name code
2 bytes data type code
4 bytes bytes of data
4 bytes datas

in gps.php at line 186 (function parseGPS())

Whatever if bytes of data is <4 it takes the 4 bytes (and garbage too)

just replace line `/zp-core/exif/makers/gps.php:187`
`$data = $value`

by

`$data = substr($value,0, $bytesofdata);`

it works fine