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

Error nearest place #5042

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

Error nearest place #5042

openstreetmap-trac opened this issue Jul 23, 2021 · 2 comments
Assignees
@openstreetmap-trac
Labels
Component: nominatim Priority: trivial Resolution: fixed Type: enhancement
Milestone
Wishlist

Comments

@openstreetmap-trac
Copy link

Reporter: emilio.mejia[at]gmail.com
[Submitted to the original trac issue database at 6.43pm, Thursday, 28th November 2013]

In the query disply place Catarata, but the nearest place is Sixaola.

http://nominatim.openstreetmap.org/reverse?format=xml&lat=9.5024033&lon=-82.61462833&zoom=18&addressdetails=1
@openstreetmap-trac openstreetmap-trac added this to the Wishlist milestone Jul 23, 2021
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 10.58am, Friday, 29th November 2013]

That's by design. reverse actually returns the address of the closest object, not the address of the point you requested. In this case, the closest object is a very long road that goes through many villages among them Catarata.

Splitting ways in Nominatim is something that's been considered but generally the problem goes away by itself, when areas are mapped in more detail and roads are split in OSM because bridges and the like are added.

@openstreetmap-trac
Copy link
Author

Author: emilio.mejia[at]gmail.com
[Added to the original trac issue at 1.15pm, Friday, 29th November 2013]

Solved change search by reverse.
Tks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@openstreetmap-trac openstreetmap-trac

Labels
Component: nominatim Priority: trivial Resolution: fixed Type: enhancement
Projects
None yet
Milestone
Wishlist
Development

No branches or pull requests
1 participant
@openstreetmap-trac