Address contains a suburb/county of a neighbouring area

[openstreetmap-trac]

Reporter: scillystuff [Submitted to the original trac issue database at 1.23am, Sunday, 26th February 2012]

http://nominatim.openstreetmap.org/reverse?format=xml&lat=53.722468&&lon=-1.781888&zoom=18&addressdetails=1

gives

Smith House Lane, Low Moor, Calderdale, West Yorkshire, Yorkshire and the Humber, England, United Kingdom Smith House Lane Low Moor Calderdale West Yorkshire Yorkshire and the Humber England United Kingdom gb

Suburb should be Lightcliffe, or council ward of Hipperholme and Lightcliffe. Node for Lightcliffe is present and is nearer to (but not covering) location than node for Low Moor, so I don't know why wrong suburb is returning.

[openstreetmap-trac]

Author: lonvia [Added to the original trac issue at 8.40pm, Monday, 27th February 2012]

This is another incarnation of the problem of missing administrative levels.

When making up an address, Nominatim tries to relate a place to as many administrative levels as possible. Because Calderdale does not have suburbs, Nominatim adds the closest suburb it can find, which in this case happens to be a suburb of Bradford.

Nominatim needs a detection that excludes place nodes that are outside the area of a lower administrative level polygon in the same address.

[openstreetmap-trac]

Author: lonvia [Added to the original trac issue at 8.11pm, Wednesday, 13th June 2012]

Note: the current solution with linked places does not solve the bug in cases where the suburb/county node does not have an administrative boundary. Those nodes still need to be excluded explicitly.

[openstreetmap-trac]

Author: lonvia [Added to the original trac issue at 6.25am, Monday, 20th August 2012]

Nominatim now also excludes nodes outside the parent area. This should fix all known cases.