Nominatim

mirror of https://github.com/osm-search/Nominatim.git synced 2026-02-14 18:37:58 +00:00

Files

Sarah Hoffmann 7295cad715 compute address parts for rank 30 objects on the fly

Rank 30 objects usually use the address parts of their parent.
When the parent has address parts that are areas but not marked
as isaddress, then the parent might go through multiple administrative
areas. In that case recheck if the right area has been choosen
for the object in question instead of relying on isaddress.
Note that we really only have to do the recomputation in the
case of 'isarea = True and isaddress = False' which hopefully
keeps the number of additional geometric operations we have to do
to a minimum.

There is one more special case to be taken into account here: a
street may go through two administrative areas and a house along
that street is placed in one of the area while the addr:* tags
says it belongs to the other. In that case we must not switch
the isaddress to the one it is situated. To avoid that recheck
the address names against the name of the ara. That is not perfect
but should cover most cases.

Fixes #328.

2020-12-01 11:58:25 +01:00

functions

compute address parts for rank 30 objects on the fly

2020-12-01 11:58:25 +01:00

aux_tables.sql

make tables for external data (Tiger and aux) configurable

2016-04-07 21:47:51 +02:00

hstore_compatability_9_0.sql

hstore in 9.2 replaces k=>v with hstore(k,v). Update sql to reflect change and introduce compatability function for pre 9.1 postgresql

2012-11-01 01:46:19 +00:00

indices_search.src.sql

revert building indexes concurrently