Wrong city tagging in some countries due to admin_level difference
|Reported by:||sander.vantulden@…||Owned by:||geocoding@…|
|Keywords:||boundary:administrative, admin_level, city, village||Cc:|
I found some roads in The Netherlands that have the wrong city associated with them. For example, if you take a street in the village called "Malden", Nominatim returns the corresponding village to be "Heumen", which is the municipality, but not the village.
It took me some time, but I think I found what could be the reason for this mistagging. In The Netherlands, the admin_level for city boundary is 10 and the municipality boundary is 8 (see here for an explanation). This seems to be the other way around for other countries.
Here is the "Heumen" city boundary relation (which holds the correct municipality boundary) and
Here is the "Heumen" suburb boundary relation (which holds the correct city boundary)
Here you can see that "Malden" also has a suburb boundary (which holds the correct city boundary). Because of the admin_level 10, "Heumen"'s admin_level 8 overrides it, to let it get the "Heumen" village tag.
Does this problem I describe make sense? Are country-specific admin_level tagging already handled in Nominatim? Or would it be possible to add it for specific countries?
This may be related to #5185, but I am not sure.
Change History (3)
comment:1 Changed 2 years ago by sander.vantulden@…
- Summary changed from Wrong city tagging in NL due to admin_level difference to Wrong city tagging in some countries due to admin_level difference