Support for house numbers without street (addr:place schema) #54
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.