From cc1af99dbd1b1e28cc9f8da92914cba237de5d31 Mon Sep 17 00:00:00 2001 From: Sarah Hoffmann Date: Wed, 25 Nov 2020 20:33:15 +0100 Subject: [PATCH] filter postcodes by search rank when adding to address list The post codes are the last part that does not fit the new address ranking scheme. In particular, the search rank is still relevant for choosing if a postcode should be included into the address terms. Filter out irrelevant postcodes in getNearFeatures() already, to avoid having to check for geometry relation. --- sql/partition-functions.src.sql | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sql/partition-functions.src.sql b/sql/partition-functions.src.sql index 1197b3b7..703c08af 100644 --- a/sql/partition-functions.src.sql +++ b/sql/partition-functions.src.sql @@ -47,6 +47,9 @@ BEGIN WHERE geometry && feature AND is_relevant_geometry(ST_Relate(geometry, feature), ST_GeometryType(feature)) AND rank_address < maxrank + -- Postcodes currently still use rank_search to define for which + -- features they are relevant. + AND not (rank_address in (5, 11) and rank_search > maxrank) GROUP BY place_id, keywords, rank_address, rank_search, isguess, postcode, centroid LOOP RETURN NEXT r;