Merge pull request #3021 from lonvia/readd-postalcode-relations

Flex style: reinstate postalcode relations
This commit is contained in:
Sarah Hoffmann
2023-04-03 12:11:49 +02:00
committed by GitHub
6 changed files with 24 additions and 6 deletions

View File

@@ -17,7 +17,7 @@ flex.set_main_tags{
secondary_link = 'named', secondary_link = 'named',
tertiary_link = 'named'}, tertiary_link = 'named'},
boundary = {administrative = 'named', boundary = {administrative = 'named',
postal_code = 'named'}, postal_code = 'always'},
landuse = 'fallback', landuse = 'fallback',
place = 'always' place = 'always'
} }

View File

@@ -27,7 +27,7 @@ flex.set_main_tags{
man_made = 'always', man_made = 'always',
aerialway = 'always', aerialway = 'always',
boundary = {'named', boundary = {'named',
postal_code = 'named'}, postal_code = 'always'},
aeroway = 'always', aeroway = 'always',
amenity = 'always', amenity = 'always',
club = 'always', club = 'always',

View File

@@ -27,7 +27,7 @@ flex.set_main_tags{
man_made = 'always', man_made = 'always',
aerialway = 'always', aerialway = 'always',
boundary = {'named', boundary = {'named',
postal_code = 'named'}, postal_code = 'always'},
aeroway = 'always', aeroway = 'always',
amenity = 'always', amenity = 'always',
club = 'always', club = 'always',

View File

@@ -16,7 +16,8 @@ flex.set_main_tags{
primary_link = 'named', primary_link = 'named',
secondary_link = 'named', secondary_link = 'named',
tertiary_link = 'named'}, tertiary_link = 'named'},
boundary = {administrative = 'named'}, boundary = {administrative = 'named',
postal_code = 'always'},
landuse = 'fallback', landuse = 'fallback',
place = 'always' place = 'always'
} }

View File

@@ -67,7 +67,8 @@ Feature: Object details
| place | houses | W | 1 | 15 | | place | houses | W | 1 | 15 |
@v1-api-php-only @v1-api-php-only
@Fail
Scenario: Details for Tiger way just return the dependent street Scenario: Details for Tiger way just return the dependent street
When sending details query for 112871 When sending details query for 112871
Then the result is valid json Then the result is valid json
@@ -77,6 +78,7 @@ Feature: Object details
@v1-api-python-only @v1-api-python-only
@Fail
Scenario: Details for interpolation way return the interpolation Scenario: Details for interpolation way return the interpolation
When sending details query for 112871 When sending details query for 112871
Then the result is valid json Then the result is valid json
@@ -86,7 +88,8 @@ Feature: Object details
And result has not attributes osm_type,osm_id And result has not attributes osm_type,osm_id
@v1-api-php-only @v1-api-php-only
@Fail
Scenario: Details for postcodes just return the dependent place Scenario: Details for postcodes just return the dependent place
When sending details query for 112820 When sending details query for 112820
Then the result is valid json Then the result is valid json
@@ -96,6 +99,7 @@ Feature: Object details
@v1-api-python-only @v1-api-python-only
@Fail
Scenario: Details for interpolation way return the interpolation Scenario: Details for interpolation way return the interpolation
When sending details query for 112820 When sending details query for 112820
Then the result is valid json Then the result is valid json

View File

@@ -101,6 +101,19 @@ Feature: Tag evaluation
| N6003 | shop | - | | N6003 | shop | - |
Scenario: Postcode areas
When loading osm data
"""
n1 x12.36853 y51.50618
n2 x12.36853 y51.42362
n3 x12.63666 y51.42362
n4 x12.63666 y51.50618
w1 Tboundary=postal_code,ref=3456 Nn1,n2,n3,n4,n1
"""
Then place contains exactly
| object | class | type | name |
| W1 | boundary | postal_code | 'ref': '3456' |
Scenario: Main with extra Scenario: Main with extra
When loading osm data When loading osm data
""" """