Nominatim considers place nodes and administrative boundaries
in specific cases (same name, same level in the hierarchy, etc.)
as different representations of the same entity: one is the
center point and one the exact area. To avoid duplicates, it
merges the two and returns one object. The adminstrative
boundary is considered the 'main object' of the two. the place
node is only used to complete the information.
You can extract most of the data from the place node. The
name tags are merged, so they appear automaticaly. If you
add 'extratags=1' to your search query, then you get a list
of additional tags, including the place tag. The position of
the node can be found in the center point of the result
(lat and lon parameters).
There is one thing you cannot get: the original OSM id. It
would be easy to add, though, if there is a valid use case.
On Tue, Sep 20, 2016 at 02:07:27PM +0000, Andrey Syschikov wrote:
> Hi all,
> I noticed that Nominatim has strange preference for boundary:administrative
> over place:XYZ when they have same name. Here is very simple example:
> It returns one result:
> Which is boundary:administrative. In the linked places there is this place:
> Which is place:village. I am wondering why doesn't it show up in search
> results. I am personally more interested in places so I am wondering if it
> is possible to add a parameter to search to prefer places or it is
> a server-side setting for Nominatim. I have a local instance running as
> well so I can try to play with that.
> PS: I am totally new to OSM, geocoding and all that stuff, so please don't
> judge too hard if my question sounds stupid :)
> Geocoding mailing list
Geocoding mailing list