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

Wrong results in reverse geocoding for lat,lon : 48.464464,2.361410 #5389

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

Comments

@openstreetmap-trac
Copy link

Reporter: marc.bertran[at]yahoo.fr
[Submitted to the original trac issue database at 9.17pm, Wednesday, 24th February 2016]

Wrong reversegeocoding from lat: 48.464464 lon: 2.361410 gives :

Le Grand Saussay
Ballancourt-sur-Essonne
vry
Ile-de-France
France
91610
<country_code>fr</country_code>

Should give :

Rue du Cimetire
Guigneville-sur-Essonne
vry
Ile-de-France
France
91590
<country_code>fr</country_code>

@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 9.17pm, Monday, 7th March 2016]

I get Le Grand Saussay, which is about right given that there is no geocodable street reasonably close and thus the result is a more rough estimate.

@openstreetmap-trac
Copy link
Author

Author: marc.bertran[at]yahoo.fr
[Added to the original trac issue at 9.23am, Tuesday, 8th March 2016]

I live close to this area. I am detecting aircraft traffic and aircrafts send me there position.

If you call google map API with these coordinate, the position is OK : Guigneville-sur-Essonne

But nominatim returns a wrong position Ballancourt-sur-Essonne
All the adresspart is wrong. I can give you others coordinates that return wrong result all are included in this aera.

@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 8.58pm, Thursday, 13th October 2016]

Duplicate of #4519

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