Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Geotagged images with minus longitiudes incorrectly shown #2246

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 5 comments
Closed

Geotagged images with minus longitiudes incorrectly shown #2246

openstreetmap-trac opened this issue Jul 23, 2021 · 5 comments

Comments

@openstreetmap-trac
Copy link

Reporter: kevjs1982
[Submitted to the original trac issue database at 5.48am, Tuesday, 1st September 2009]

When importing images Geotagged using GeoSetter (they display okay in Google Earth) which have negative longitude value they are displayed at longitude value without the minus sign.

The attached image should be displayed at lat=52.94490900; lon=-1.08963100; but is actually displayed at lat=52.94490900; lon=1.08963100;

@openstreetmap-trac
Copy link
Author

Author: Koying
[Added to the original trac issue at 12.39pm, Tuesday, 15th September 2009]

I don't have the problem on Windows.

If not windows, please state OS/Qt version/exiv2 version...

@openstreetmap-trac
Copy link
Author

Author: Koying
[Added to the original trac issue at 9.46am, Tuesday, 29th September 2009]

Someone else noticed this?

@openstreetmap-trac
Copy link
Author

Author: tms13
[Added to the original trac issue at 12.15pm, Tuesday, 29th September 2009]

I fixed an issue with the sign of longitude and latitude a few
months ago. My images from gpscorrelate were appearing the wrong side
of the Greenwich Meridian.

To diagnose, it would be useful to have a dump of the data from the GPS*
tags in the exif. E.g. from one of my images:

$ exiv2 -pv 20090909-121938.jpg | grep '^0x.... GPSInfo'
0x0000 GPSInfo      GPSVersionID                Byte        4  2 0 0 0 
0x0001 GPSInfo      GPSLatitudeRef              Ascii       2  N
0x0002 GPSInfo      GPSLatitude                 Rational    3  57/1 28/1 4203/100
0x0003 GPSInfo      GPSLongitudeRef             Ascii       2  W
0x0004 GPSInfo      GPSLongitude                Rational    3  4/1 5/1 3561/100
0x0005 GPSInfo      GPSAltitudeRef              Byte        1  0 
0x0006 GPSInfo      GPSAltitude                 Rational    1  764675/5000
0x0007 GPSInfo      GPSTimeStamp                SRational   3  12/1 19/1 38/1
0x0012 GPSInfo      GPSMapDatum                 Ascii       7  WGS-84
0x001d GPSInfo      GPSDateStamp                Ascii      11  2009:09:09

Obviously, it's the GPSLongitude and GPSLongitudeRef that are
particularly interesting to this issue.

@openstreetmap-trac
Copy link
Author

Author: tms13
[Added to the original trac issue at 12.34pm, Tuesday, 29th September 2009]

Replying to [comment:3 tms13]:

I found
[http://lists.openstreetmap.org/pipermail/merkaartor/2009-April/001579.html the mail containing my patch].

According to Chris Browet's followup, he applied it on 28 April 2009.

@openstreetmap-trac
Copy link
Author

Author: Koying
[Added to the original trac issue at 12.46pm, Tuesday, 29th September 2009]

Probably why I cannot reproduce in 0.14 ;-)

To the reporter: Please upgrade to 0.14

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant