Author: lonvia
[Added to the original trac issue at 3.25pm, Saturday, 25th February 2012]

The description on the OSM Wiki about the Czech addressing system is in Czech only. Please, provide more information about these tags and how they are used in addresses and when searching.

Author: lonvia
[Added to the original trac issue at 5.31pm, Saturday, 25th February 2012]

Understanding the system now and why it causes problems.

Basically, addr:streetnumber are the same as addr:housenumber in other countries and need to be handled in the same way. addr:conscriptionnumber and addr:provisionalnumber are slightly different because they are not really attached to a street but belong to a suburb or town.

Not sure about addr:alternatenumber, it seems rarely used.

Author: MichalP
[Added to the original trac issue at 5.45pm, Thursday, 12th April 2012]

addr:conscriptionnumber is basically number of house in given city, addr:provisionalnumber is number on given street, housenumber is a combination of both.

rationalle is that in many villages, there are no street names, thus addr:conscriptionnumber only is used.

currently it seems that if there is no street_name, the address cannot be found, searching for "chrenovec-brusno 350" should zoom to http://osm.org/go/0LMzVZ1Hs-- but it does not find anything...

Author: kayle
[Added to the original trac issue at 6.50pm, Thursday, 12th April 2012]

small note to Slovakia

addr:conscriptionnumber - is unique number of house in town(suburb)/village. This number is rarely used when somebody search address in towns and villages with street names, but it is ONLY' number in villages 'WITHOUT street names!
When used in search string with street name usually in combination "addr:conscriptionnumber/addr:streetnumber" (again rarely)

addr:streetnumber - only used when street names exists. This numbers people search in town/villages with street names.
note: One building (usally block of flats) with one addr:conscriptionnumber can have multiple addr:streetnumbers, each entrance own addr:streetnumber.

sample addr:conscriptionnumber and addr:streetnumber [[BR]]
http://osm.org/go/0LMb9eu4M-- [[BR]]
addr:housenumber = addr:conscriptionnumber/addr:streetnumber

sample with addr:conscriptionnumber ONLY[[BR]]
http://osm.org/go/0LHmCaEYI--

addr:provisionalnumber - in Slovakia not used after 31.12.1998

Author: andrew_shadoura
[Added to the original trac issue at 1.20pm, Thursday, 24th January 2013]

In CZ and SK, a house number is composed of two numbers: a conscription
number and a street number. The conscription number is unique within the
place (city, town, village), and the street number is local to the street
the house is located at. Usually this is written as 1135/45, where 1135 is
the conscription number, and 45 is the street number. In small villages
houses don't usually have individual street numbers.

The patch enables osm2pgsql to read addr:conscriptionnumber and
addr:streetnumber tags used in CZ and SK, in Gazetteer mode. If any of those
two is found alone, it supersedes addr:housenumber, if both exist, they are
joined with a slash, and used instead addr:housenumber as well. This is done
because addr:housenumber is often used to specify what Mapnik would render (as
it doesn't currently recognise additional tags), so quite often it contains
incomplete information.

Author: lonvia
[Added to the original trac issue at 8.02pm, Saturday, 26th January 2013]

I've set up a test instance with this patch at http://osm.lonvia.de/nominatim/
(CZ, SK only and no Wikipedia importance, so search results may be ordered differently)

It looks good as far as I can see, maybe a few locals could look over it and confirm that it does not result in regressions or weird behaviour with search. Please keep in mind that this patch does not resolve the issue with addresses without a street name. They still won't be found.

I have a mild reservation against overwriting addr:housenumber but according to taginfo addr:conscriptionnumber is used in CZ/SK only and the few addr:streetnumber tags outside of these countries seem to be mostly tagging errors. So, if it goes with local conventions, then so be it. twain, any thoughts?

One final thing you should be aware of: this patch has not only an influence on search but also on address lookup. When looking up coordinates, the addresses will also always be returned with house numbers in conscriptionnumber/streetnumber format.

Author: twain
[Added to the original trac issue at 2.28pm, Sunday, 27th January 2013]

I'm likewise not a great fan of reuse of the same field for a different meaning since I think it probably blocks implementation of non-street house numbers. The fact that there is a addr:conscriptionnumber is needed in order to select that behaviour and we can't use the existence of a '/' in number since I think some people have done things like '12 1/2' for 12 and a half.

However I can see the expediency of doing it this way for the time being.

Could the patch maybe be changed to also add addr:conscriptionnumber to the 'extratags' field as well? This would leave us a way forward although it does cause some bloat.

lonvia?

Author: lonvia
[Added to the original trac issue at 6.03pm, Sunday, 27th January 2013]

I'd certainly consider the patch only a temporary solution that needs to be reevaluated when non-street house numbers get implemented. (Although the implication of this patch, namely that people do search by a combination of conscription number and street, is going to make that implementation a little bit more interesting.) In the end, I wouldn't be too worried about compatibility with a non-street house number implementation as I don't see this being done without a DB reimport.

However, good idea about the extra tags, also for debugging. Maybe add addr:streetnumber as well.

Author: Kozuch
[Added to the original trac issue at 6.37pm, Sunday, 27th January 2013]

How can I stop receiving notifications for this bug???

Author: andrew_shadoura
[Added to the original trac issue at 12.19am, Thursday, 31st January 2013]

One final thing you should be aware of: this patch has not only an influence on search but also on address lookup. When looking up coordinates, the addresses will also always be returned with house numbers in conscriptionnumber/streetnumber format.

I'm sure this is not only not bad, but also useful: it makes it possible to find out the correct full address by double-resolving it.

Author: lonvia
[Added to the original trac issue at 9.22pm, Sunday, 28th April 2013]

Looking through a few Czech examples, I can't quite figure out how to find the correct place to attach the conscription numbers to. Sometimes, an addr:city is added but I'm not sure that this is always the right thing to attach to. Do you expect some special admin boundaries to be used?

Author: lonvia
[Added to the original trac issue at 11.39am, Wednesday, 1st May 2013]

Support for the [http://wiki.openstreetmap.org/wiki/Key:addr:place addr:place] tag for street-less addresses has just been added to Nominatim. This also adds limited support for conscription numbers.

Addresses without street numbers can be made searchable by adding an appropriate addr:place tag. However, there is still no support for dual addresses. So, if there is a street number tagged (or to be more precise: if there is a addr:street tag and no addr:place tag), then this will take precedence and the place will get the street address only.