Author: imz[at]altlinux.org
[Added to the original trac issue at 7.42pm, Tuesday, 23rd October 2012]

Another example:

, 9

doesn't work; though at least:

, 9

seems to work (the house is listed in the search results, so I can click it, and make it point at it).

Author: imz[at]altlinux.org
[Added to the original trac issue at 7.48pm, Tuesday, 23rd October 2012]

Hmm... I want to check once again what appars in the list of search results for my first address. So:

, 7 2

doesn't give results. Bad, because this is like a valid address (with the korpus number). But neither format with a korpus number seems to lead to adequate search results.

, 7

gives a list of several buildings (korpus) -- OK.

, 7

doesn't produce such a list. Bad, because this is a long, but frequently used way to spell out this part of the address (with the house number).

Author: lonvia
[Added to the original trac issue at 8.22pm, Tuesday, 23rd October 2012]

The following query would be the form that should already work with Nominatim: , 7 2

It does not because there is a bug in the handling of house numbers. The house numbers are saved in their untransliterated form (i.e. 7 2) in placex, but search.php actually queries it with the transliterated form (i.e. 7 k2).

For the other formats, support for ignoring words is needed and maybe some additional transliterations.

Author: lonvia
[Added to the original trac issue at 6.16pm, Saturday, 10th May 2014]

House number normalization issue fixed in [changeset:defb809/nominatim].