Support for house numbers without street (addr:place schema)

[lonvia]

This is a proposal to add support for addr:place by adding a new column 'addr_place' which works just like the 'street' column. A house number is simply interpreted as attachable to a street or a place (currently up to search rank 16) according to which of the two columns is not NULL. The search algorithm can remain unmodified. Requires some modifications of osm2pgsql.

Works nicely with the Polish addr:place system, needs minimal modifications, can be adopted without reimport and has almost no overhead. Figures for planet import:

Import time: 2165 min (-43 min)
DB size: 524 GB ( +4 GB)

Downside is that I don't know how to make it work with the conscription number system without resorting to some ugly hacks. The whole double addressing idea probably requires to duplicate the housenumber column as well and possibly also parent_place_id, which in turn would have more severe implications for the front end.

[twain47]

It seems like a significant improvement with no obvious down side.

I have a slight worry about the performance effect of the change to search.php but hopefully it is minor.

[lonvia]

Alright, let's merge this in then and worry about conscription numbers later.

There were still some issues with correct invalidation when parent objects are updated. Should be fixed now, updates are doing fine. I've also applied the change of search.php to the OSM instance and couldn't see any impact on performance. Still need to make sure that the DB migration actually works. I'll merge once those tests have passed.

[lonvia]

Merged.

To migrate existing DBs run (with updates disabled):

ALTER TABLE place ADD COLUMN addr_place TEXT;
ALTER TABLE placex ADD COLUMN addr_place TEXT;

To also update any existing street-less addresses in the DB get all appropriately tagged data from the Overpass API using this query and import into your DB with ./utils/update.php --import file <placefile> --index.