2 Feature: Update of simple objects
5 Scenario: Do delete small boundary features
7 | osm_type | osm_id | class | type | admin_level | geometry
8 | R | 1 | boundary | administrative | 3 | (0 0, 1 0, 1 1, 0 1, 0 0)
10 Then table placex contains
11 | object | rank_search
13 When marking for delete R1
14 Then table placex has no entry for R1
16 Scenario: Do not delete large boundary features
18 | osm_type | osm_id | class | type | admin_level | geometry
19 | R | 1 | boundary | administrative | 3 | (0 0, 2 0, 2 2.1, 0 2, 0 0)
21 Then table placex contains
22 | object | rank_search
24 When marking for delete R1
25 Then table placex contains
26 | object | rank_search
29 Scenario: Do delete large features of low rank
30 Given the named place areas
31 | osm_type | osm_id | class | type | geometry
32 | W | 1 | place | house | (0 0, 2 0, 2 2.1, 0 2, 0 0)
33 | R | 1 | boundary | national_park | (0 0, 2 0, 2 2.1, 0 2, 0 0)
35 Then table placex contains
36 | object | rank_address
39 When marking for delete R1,W1
40 Then table placex has no entry for W1
41 Then table placex has no entry for R1
44 Scenario: type mutation
46 | osm_id | class | type | geometry
47 | 3 | shop | toys | 1 -1
49 Then table placex contains
50 | object | class | type
52 When updating place nodes
53 | osm_id | class | type | geometry
54 | 3 | shop | grocery | 1 -1
55 Then table placex contains
56 | object | class | type
60 Scenario: remove postcode place when house number is added
62 | osm_id | class | type | postcode | geometry
63 | 3 | place | postcode | 12345 | 1 -1
65 Then table placex contains
66 | object | class | type
67 | N3 | place | postcode
68 When updating place nodes
69 | osm_id | class | type | postcode | housenumber | geometry
70 | 3 | place | house | 12345 | 13 | 1 -1
71 Then table placex contains
72 | object | class | type