X-Git-Url: https://git.openstreetmap.org./nominatim.git/blobdiff_plain/cf36e8d2fba81351889208e4499e8d28e7d9593c..1d89098f7709791cafca26c72ceb59bbbf817a51:/tests/features/api/reverse.feature diff --git a/tests/features/api/reverse.feature b/tests/features/api/reverse.feature index 2486b013..39519177 100644 --- a/tests/features/api/reverse.feature +++ b/tests/features/api/reverse.feature @@ -11,6 +11,15 @@ Feature: Reverse geocoding | ID | country | 0 | Deutschland + + Scenario: Boundingbox is returned + Given the request parameters + | format | zoom + | xml | 4 + When looking up coordinates 53.9788769,13.0830313 + And results contain valid boundingboxes + + @Tiger Scenario: TIGER house number Given the request parameters @@ -23,3 +32,113 @@ Feature: Reverse geocoding | 0 | 7094 | Kings Estate Drive | 84128 | us And result 0 has not attributes osm_id,osm_type + + @Tiger + Scenario: No TIGER house number for zoom < 18 + Given the request parameters + | addressdetails | zoom + | 1 | 17 + When looking up coordinates 40.6863624710666,-112.060005720023 + And exactly 1 result is returned + And result addresses contain + | ID | road | postcode | country_code + | 0 | Kings Estate Drive | 84128 | us + And result 0 has attributes osm_id,osm_type + + Scenario Outline: Reverse Geocoding with extratags + Given the request parameters + | extratags + | 1 + When looking up coordinates 48.86093,2.2978 + Then result 0 has attributes extratags + + Examples: + | format + | xml + | json + | jsonv2 + + Scenario Outline: Reverse Geocoding with namedetails + Given the request parameters + | namedetails + | 1 + When looking up coordinates 48.86093,2.2978 + Then result 0 has attributes namedetails + + Examples: + | format + | xml + | json + | jsonv2 + + + Scenario Outline: Reverse Geocoding contains TEXT geometry + Given the request parameters + | polygon_text + | 1 + When looking up coordinates 48.86093,2.2978 + Then result 0 has attributes + + Examples: + | format | response_attribute + | xml | geotext + | json | geotext + | jsonv2 | geotext + + Scenario Outline: Reverse Geocoding contains polygon-as-points geometry + Given the request parameters + | polygon + | 1 + When looking up coordinates 48.86093,2.2978 + Then result 0 has not attributes + + Examples: + | format | response_attribute + | xml | polygonpoints + | json | polygonpoints + | jsonv2 | polygonpoints + + + + Scenario Outline: Reverse Geocoding contains SVG geometry + Given the request parameters + | polygon_svg + | 1 + When looking up coordinates 48.86093,2.2978 + Then result 0 has attributes + + Examples: + | format | response_attribute + | xml | geosvg + | json | svg + | jsonv2 | svg + + + Scenario Outline: Reverse Geocoding contains KML geometry + Given the request parameters + | polygon_kml + | 1 + When looking up coordinates 48.86093,2.2978 + Then result 0 has attributes + + Examples: + | format | response_attribute + | xml | geokml + | json | geokml + | jsonv2 | geokml + + + Scenario Outline: Reverse Geocoding contains GEOJSON geometry + Given the request parameters + | polygon_geojson + | 1 + When looking up coordinates 48.86093,2.2978 + Then result 0 has attributes + + Examples: + | format | response_attribute + | xml | geojson + | json | geojson + | jsonv2 | geojson + +