Scenario: place nodes are added to the address when they are close enough
Given the 0.002 grid
| 2 | | | | | | 1 | | 3 |
- And the named places
- | osm | class | type | geometry |
- | N1 | place | square | 1 |
- | N2 | place | hamlet | 2 |
- | N3 | place | hamlet | 3 |
+ And the places
+ | osm | class | type | name | geometry |
+ | N1 | place | square | Square | 1 |
+ | N2 | place | hamlet | West Farm | 2 |
+ | N3 | place | hamlet | East Farm | 3 |
When importing
Then place_addressline contains
| object | address | fromarea |
Then place_addressline doesn't contain
| object | address |
| N1 | N2 |
+ When sending search query "Square"
+ Then results contain
+ | osm | display_name |
+ | N1 | Square, East Farm |
Scenario: given two place nodes, the closer one wins for the address
Given the grid
And place_addressline doesn't contain
| object | address |
| W1 | R1 |
- When searching for "Bolder"
+ When sending search query "Bolder"
+ Then results contain
+ | osm | display_name |
+ | N1 | Bolder, Wonderway, Left |
+
+ Scenario: addr:* tags do not produce addresslines when the parent has the address part
+ Given the grid
+ | 1 | | | 5 |
+ | | 8 | 9 | |
+ | 4 | | | 6 |
+ And the places
+ | osm | class | type | admin | name | geometry |
+ | R1 | boundary | administrative | 8 | Outer | (1,5,6,4,1) |
+ And the places
+ | osm | class | type | name | addr+city | geometry |
+ | W1 | highway | primary | Wonderway | Outer | 8,9 |
+ | N1 | amenity | cafe | Bolder | Outer | 9 |
+ When importing
+ Then place_addressline contains
+ | object | address | isaddress |
+ | W1 | R1 | True |
+ And place_addressline doesn't contain
+ | object | address |
+ | N1 | R1 |
+ When sending search query "Bolder"
+ Then results contain
+ | osm | display_name |
+ | N1 | Bolder, Wonderway, Outer |
+
+ Scenario: addr:* tags on outside do not produce addresslines when the parent has the address part
+ Given the grid
+ | 1 | | 2 | | | 5 |
+ | | | | 8 | 9 | |
+ | 4 | | 3 | | | 6 |
+ And the places
+ | osm | class | type | admin | name | geometry |
+ | R1 | boundary | administrative | 8 | Left | (1,2,3,4,1) |
+ | R2 | boundary | administrative | 8 | Right | (2,3,6,5,2) |
+ And the places
+ | osm | class | type | name | addr+city | geometry |
+ | W1 | highway | primary | Wonderway | Left | 8,9 |
+ | N1 | amenity | cafe | Bolder | Left | 9 |
+ When importing
+ Then place_addressline contains
+ | object | address | isaddress |
+ | W1 | R1 | True |
+ | W1 | R2 | False |
+ And place_addressline doesn't contain
+ | object | address |
+ | N1 | R1 |
+ When sending search query "Bolder"
Then results contain
- | osm_type | osm_id | name |
- | N | 1 | Bolder, Wonderway, Left |
+ | osm | display_name |
+ | N1 | Bolder, Wonderway, Left |
+ Scenario: POIs can correct address parts on the fly
+ Given the grid
+ | 1 | | | | 2 | | 5 |
+ | | | | 9 | | 8 | |
+ | 4 | | | | 3 | | 6 |
+ And the places
+ | osm | class | type | admin | name | geometry |
+ | R1 | boundary | administrative | 8 | Left | (1,2,3,4,1) |
+ | R2 | boundary | administrative | 8 | Right | (2,3,6,5,2) |
+ And the places
+ | osm | class | type | name | geometry |
+ | W1 | highway | primary | Wonderway | 2,3 |
+ | N1 | amenity | cafe | Bolder | 9 |
+ | N2 | amenity | cafe | Leftside | 8 |
+ When importing
+ Then place_addressline contains
+ | object | address | isaddress |
+ | W1 | R1 | False |
+ | W1 | R2 | True |
+ And place_addressline doesn't contain
+ | object | address |
+ | N1 | R1 |
+ | N2 | R2 |
+ When sending search query "Bolder"
+ Then results contain
+ | osm | display_name |
+ | N1 | Bolder, Wonderway, Left |
+ When sending search query "Leftside"
+ Then results contain
+ | osm | display_name |
+ | N2 | Leftside, Wonderway, Right |
+
+
+ Scenario: POIs can correct address parts on the fly (with partial unmatching address)
+ Given the grid
+ | 1 | | | | 2 | | 5 |
+ | | | | 9 | | 8 | |
+ | | 10| 11| | | 12| |
+ | 4 | | | | 3 | | 6 |
+ And the places
+ | osm | class | type | admin | name | geometry |
+ | R1 | boundary | administrative | 8 | Left | (1,2,3,4,1) |
+ | R2 | boundary | administrative | 8 | Right | (2,3,6,5,2) |
+ And the places
+ | osm | class | type | name | geometry |
+ | W1 | highway | primary | Wonderway | 10,11,12 |
+ And the places
+ | osm | class | type | name | addr+suburb | geometry |
+ | N1 | amenity | cafe | Bolder | Boring | 9 |
+ | N2 | amenity | cafe | Leftside | Boring | 8 |
+ When importing
+ Then place_addressline contains
+ | object | address | isaddress |
+ | W1 | R1 | True |
+ | W1 | R2 | False |
+ And place_addressline doesn't contain
+ | object | address |
+ | N1 | R1 |
+ | N2 | R2 |
+ When sending search query "Bolder"
+ Then results contain
+ | osm | display_name |
+ | N1 | Bolder, Wonderway, Left |
+ When sending search query "Leftside"
+ Then results contain
+ | osm | display_name |
+ | N2 | Leftside, Wonderway, Right |
+
+
+
+ Scenario: POIs can correct address parts on the fly (with partial matching address)
+ Given the grid
+ | 1 | | | | 2 | | 5 |
+ | | | | 9 | | 8 | |
+ | | 10| 11| | | 12| |
+ | 4 | | | | 3 | | 6 |
+ And the places
+ | osm | class | type | admin | name | geometry |
+ | R1 | boundary | administrative | 8 | Left | (1,2,3,4,1) |
+ | R2 | boundary | administrative | 8 | Right | (2,3,6,5,2) |
+ And the places
+ | osm | class | type | name | geometry |
+ | W1 | highway | primary | Wonderway | 10,11,12 |
+ And the places
+ | osm | class | type | name | addr+state | geometry |
+ | N1 | amenity | cafe | Bolder | Left | 9 |
+ | N2 | amenity | cafe | Leftside | Left | 8 |
+ When importing
+ Then place_addressline contains
+ | object | address | isaddress |
+ | W1 | R1 | True |
+ | W1 | R2 | False |
+ And place_addressline doesn't contain
+ | object | address |
+ | N1 | R1 |
+ | N2 | R2 |
+ When sending search query "Bolder"
+ Then results contain
+ | osm | display_name |
+ | N1 | Bolder, Wonderway, Left |
+ When sending search query "Leftside"
+ Then results contain
+ | osm | display_name |
+ | N2 | Leftside, Wonderway, Left |
projects / nominatim.git / blobdiff