hans/Nominatim
1
0
Fork 1
mirror of https://github.com/osm-search/Nominatim.git synced 2026-02-16 15:47:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

align limits for deferring delete and reindexing on insert

Browse Source 
Right now when a boundary with an area between 1 and 2 broke, it
was deleted but on reinsert afer repair, the addresses are not updated
resulting in inconsistent data.
This commit is contained in:
Sarah Hoffmann
2025-07-21 16:11:06 +02:00
parent e1cef3de0a
commit 4cbbe04f7f
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
lib-sql/functions/placex_triggers.sql
View File

@@ -732,7 +732,7 @@ BEGIN
IF NEW.rank_address between 2 and 27 THEN IF NEW.rank_address between 2 and 27 THEN
IF (ST_GeometryType(NEW.geometry) in ('ST_Polygon','ST_MultiPolygon') AND ST_IsValid(NEW.geometry)) THEN IF (ST_GeometryType(NEW.geometry) in ('ST_Polygon','ST_MultiPolygon') AND ST_IsValid(NEW.geometry)) THEN
-- Performance: We just can't handle re-indexing for country level changes -- Performance: We just can't handle re-indexing for country level changes
IF (NEW.rank_address < 26 and st_area(NEW.geometry) < 1) IF (NEW.rank_address < 26 and st_area(NEW.geometry) <= 2)
OR (NEW.rank_address >= 26 and st_area(NEW.geometry) < 0.01) OR (NEW.rank_address >= 26 and st_area(NEW.geometry) < 0.01)
THEN THEN
-- mark items within the geometry for re-indexing -- mark items within the geometry for re-indexing