Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong location info returned #1

Closed
danielegobbetti opened this issue Jan 29, 2015 · 10 comments
Closed

Wrong location info returned #1

danielegobbetti opened this issue Jan 29, 2015 · 10 comments
Labels

Comments

@danielegobbetti
Copy link

Hello! I noticed that the location info returned (eg to gallery) are off by a couple of tens of kilometers. Is this a "blur" introduced for privacy reasons? I tried entering the coordinates into the online search form on the map quest website and the info shown there are exact.

@mar-v-in
Copy link
Member

I usually do not get any offset at all and it is no intended feature to reduce accuracy. I'll look into that.

@mar-v-in mar-v-in added the bug label Jan 29, 2015
@danielegobbetti
Copy link
Author

Do you want a geo-tagged photo to test?

For instance a photo geotagged with these coordinates: (Edit: removed for privacy reasons)
is shown in the gallery app (menu -> show details) as being shot here: http://www.openstreetmap.org/way/214800599

If I choose (from the gallery app) "show photo on map" and open it in Osmand it shows the right coordinates.

@mar-v-in
Copy link
Member

Thanks, that led me to the reason:
Depending on your locale, numbers are formatted using different decimal marks, but the api requires to use a dot. Using comma will result in the number being cut off, the result shown is at geo coordinates (46,11), which is "slightly" off the real result.

I'll upload the fix soon

@danielegobbetti
Copy link
Author

Cool, thanks!

@danielegobbetti
Copy link
Author

Sorry to bug you, but could you tag the new release so that it gets picked up by f-droid? Thanks again!

@mar-v-in
Copy link
Member

The 1.1 version will be released soon (like a few hours), just some testing of the newly added feature.
As always, release results in new tag

@danielegobbetti
Copy link
Author

Understood, thanks again!

@aelmahmoudy
Copy link

@mar-v-in please make the tag matching the version v1.1.0 (not v1.1), that helps auto-updating the build in F-Droid

@mar-v-in
Copy link
Member

@aelmahmoudy done, didn't know the exact tag makes a difference.

@aelmahmoudy
Copy link

Thanks !

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

No branches or pull requests

3 participants