safety-screen/Nominatim
1
0
Fork 0
forked from hans/Nominatim
Code Pull Requests Activity

reorganize handling of place type changes

Browse Source 
Always replace existing entries in place, never delete them because
a direct delete will cause conflicts.
This commit is contained in:
Sarah Hoffmann
2022-11-14 13:57:26 +01:00
parent 63a9bc94f7
commit 36cf0eb922
2 changed files with 73 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
test/bdd/osm2pgsql/update/tags.feature
View File

@@ -364,3 +364,50 @@ Feature: Tag evaluation
| object | indexed_status |
| W1:tourism | 2 |
| W1:highway | 1 |
Scenario: Replay on administrative boundary
When loading osm data
"""
n10 x34.0 y-4.23
n11 x34.1 y-4.23
n12 x34.2 y-4.13
w10 Tboundary=administrative,waterway=river,name=Border,admin_level=2 Nn12,n11,n10
"""
Then place contains exactly
| object |
| W10:waterway |
| W10:boundary |
When updating osm data
"""
w10 Tboundary=administrative,waterway=river,name=Border,admin_level=2 Nn12,n11,n10
"""
Then place contains exactly
| object |
| W10:waterway |
| W10:boundary |
And placex contains exactly
| object |
| W10:waterway |
Scenario: Change admin_level on administrative boundary
When loading osm data
"""
n10 x34.0 y-4.23
n11 x34.1 y-4.23
n12 x34.2 y-4.13
w10 Tboundary=administrative,name=Border,admin_level=2 Nn12,n11,n10
"""
Then place contains exactly
| object | admin_level |
| W10:boundary | 2 |
When updating osm data
"""
w10 Tboundary=administrative,name=Border,admin_level=4 Nn12,n11,n10
"""
Then place contains exactly
| object | admin_level |
| W10:boundary | 4 |