secondary_link = 'named',
tertiary_link = 'named'},
boundary = {administrative = 'named',
- postal_code = 'named'},
+ postal_code = 'always'},
landuse = 'fallback',
place = 'always'
}
man_made = 'always',
aerialway = 'always',
boundary = {'named',
- postal_code = 'named'},
+ postal_code = 'always'},
aeroway = 'always',
amenity = 'always',
club = 'always',
man_made = 'always',
aerialway = 'always',
boundary = {'named',
- postal_code = 'named'},
+ postal_code = 'always'},
aeroway = 'always',
amenity = 'always',
club = 'always',
primary_link = 'named',
secondary_link = 'named',
tertiary_link = 'named'},
- boundary = {administrative = 'named'},
+ boundary = {administrative = 'named',
+ postal_code = 'always'},
landuse = 'fallback',
place = 'always'
}
| place | houses | W | 1 | 15 |
- @v1-api-php-only
+ @v1-api-php-only
+ @Fail
Scenario: Details for Tiger way just return the dependent street
When sending details query for 112871
Then the result is valid json
@v1-api-python-only
+ @Fail
Scenario: Details for interpolation way return the interpolation
When sending details query for 112871
Then the result is valid json
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
When sending details query for 112820
Then the result is valid json
@v1-api-python-only
+ @Fail
Scenario: Details for interpolation way return the interpolation
When sending details query for 112820
Then the result is valid json
| 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
When loading osm data
"""