You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: p.weber[at]ucl.ac.uk [Submitted to the original trac issue database at 12.21pm, Friday, 12th February 2010]
This is my first ticket I ever submitted so please bear with me.
I not so recently ago (a year ago) tagged most Luxembourgish villages place tags with is_in tags to attribute each village with the right municipality. According to documentation, Nominatim makes use of is_in* tags, but when you search for a Lux village in Nominatim, Nominatim always return the village as part of Luxembourg only, it doesnt take into account the municipality.
Example is Rodenbourg, which belongs to Junglinster and is tagged as such [http://nominatim.openstreetmap.org/details.php?place_id=1030225] and OSM Node [http://www.openstreetmap.org/browse/node/289182356] . In Nominatim it comes out as belonging to Luxembourg...
Another example, where I changed the is_in tag to is_in:municipality with no effect:
[http://www.openstreetmap.org/browse/node/60844424] and corresponding Nominatim place page: [http://nominatim.openstreetmap.org/details.php?place_id=222886]
How can this be explained?
The text was updated successfully, but these errors were encountered:
Author: p.weber[at]ucl.ac.uk [Added to the original trac issue at 4.50pm, Friday, 12th February 2010]
So there needs to be an administrative boundary tagged as junglister for nominatim to recognize the hierarchy? Junglinster exists [http://nominatim.openstreetmap.org/details.php?place_id=239866] , how would I need to tag it to be recognized as both one of several villages forming a municipality, as well as the municipality itself by Nominatim ??!?!
Author: twain [Added to the original trac issue at 5.09pm, Friday, 12th February 2010]
It doesn't make sense for a village to be child of another village.
I would say that they are both children of a larger administrative area that shares the name of one of the villages. This is quite normal, although it more commonly occurs with cities.
Reporter: p.weber[at]ucl.ac.uk
[Submitted to the original trac issue database at 12.21pm, Friday, 12th February 2010]
This is my first ticket I ever submitted so please bear with me.
I not so recently ago (a year ago) tagged most Luxembourgish villages place tags with is_in tags to attribute each village with the right municipality. According to documentation, Nominatim makes use of is_in* tags, but when you search for a Lux village in Nominatim, Nominatim always return the village as part of Luxembourg only, it doesnt take into account the municipality.
Example is Rodenbourg, which belongs to Junglinster and is tagged as such [http://nominatim.openstreetmap.org/details.php?place_id=1030225] and OSM Node [http://www.openstreetmap.org/browse/node/289182356] . In Nominatim it comes out as belonging to Luxembourg...
Another example, where I changed the is_in tag to is_in:municipality with no effect:
[http://www.openstreetmap.org/browse/node/60844424] and corresponding Nominatim place page: [http://nominatim.openstreetmap.org/details.php?place_id=222886]
How can this be explained?
The text was updated successfully, but these errors were encountered: