mirror of
https://github.com/osm-search/Nominatim.git
synced 2026-02-16 15:47:58 +00:00
Reverse geocode include geometry
This commit is contained in:
@@ -61,3 +61,75 @@ Feature: Reverse geocoding
|
||||
| xml
|
||||
| json
|
||||
| jsonv2
|
||||
|
||||
|
||||
Scenario Outline: Reverse Geocoding contains TEXT geometry
|
||||
Given the request parameters
|
||||
| polygon_text
|
||||
| 1
|
||||
When looking up <format> coordinates 48.86093,2.2978
|
||||
Then result 0 has attributes <response_attribute>
|
||||
|
||||
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 <format> coordinates 48.86093,2.2978
|
||||
Then result 0 has not attributes <response_attribute>
|
||||
|
||||
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 <format> coordinates 48.86093,2.2978
|
||||
Then result 0 has attributes <response_attribute>
|
||||
|
||||
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 <format> coordinates 48.86093,2.2978
|
||||
Then result 0 has attributes <response_attribute>
|
||||
|
||||
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 <format> coordinates 48.86093,2.2978
|
||||
Then result 0 has attributes <response_attribute>
|
||||
|
||||
Examples:
|
||||
| format | response_attribute
|
||||
| xml | geojson
|
||||
| json | geojson
|
||||
| jsonv2 | geojson
|
||||
|
||||
|
||||
|
||||
@@ -17,6 +17,49 @@ Feature: Simple Reverse Tests
|
||||
| -79.34 | 23.5
|
||||
| 0.23 | -178.555
|
||||
|
||||
Scenario Outline: Testing different parameters
|
||||
Given the request parameters
|
||||
| <parameter>
|
||||
| <value>
|
||||
When sending search query "Manchester"
|
||||
Then the result is valid html
|
||||
Given the request parameters
|
||||
| <parameter>
|
||||
| <value>
|
||||
When sending html search query "Manchester"
|
||||
Then the result is valid html
|
||||
Given the request parameters
|
||||
| <parameter>
|
||||
| <value>
|
||||
When sending xml search query "Manchester"
|
||||
Then the result is valid xml
|
||||
Given the request parameters
|
||||
| <parameter>
|
||||
| <value>
|
||||
When sending json search query "Manchester"
|
||||
Then the result is valid json
|
||||
Given the request parameters
|
||||
| <parameter>
|
||||
| <value>
|
||||
When sending jsonv2 search query "Manchester"
|
||||
Then the result is valid json
|
||||
|
||||
Examples:
|
||||
| parameter | value
|
||||
| polygon | 1
|
||||
| polygon | 0
|
||||
| polygon_text | 1
|
||||
| polygon_text | 0
|
||||
| polygon_kml | 1
|
||||
| polygon_kml | 0
|
||||
| polygon_geojson | 1
|
||||
| polygon_geojson | 0
|
||||
| polygon_svg | 1
|
||||
| polygon_svg | 0
|
||||
|
||||
|
||||
|
||||
|
||||
Scenario Outline: Wrapping of legal jsonp requests
|
||||
Given the request parameters
|
||||
| json_callback
|
||||
|
||||
@@ -230,3 +230,73 @@ Feature: Search queries
|
||||
| xml
|
||||
| json
|
||||
| jsonv2
|
||||
|
||||
|
||||
Scenario Outline: Search result with contains TEXT geometry
|
||||
Given the request parameters
|
||||
| polygon_text
|
||||
| 1
|
||||
When sending <format> search query "switzerland"
|
||||
Then result 0 has attributes <response_attribute>
|
||||
|
||||
Examples:
|
||||
| format | response_attribute
|
||||
| xml | geotext
|
||||
| json | geotext
|
||||
| jsonv2 | geotext
|
||||
|
||||
Scenario Outline: Search result contains polygon-as-points geometry
|
||||
Given the request parameters
|
||||
| polygon
|
||||
| 1
|
||||
When sending <format> search query "switzerland"
|
||||
Then result 0 has attributes <response_attribute>
|
||||
|
||||
Examples:
|
||||
| format | response_attribute
|
||||
| xml | polygonpoints
|
||||
| json | polygonpoints
|
||||
| jsonv2 | polygonpoints
|
||||
|
||||
|
||||
|
||||
Scenario Outline: Search result contains SVG geometry
|
||||
Given the request parameters
|
||||
| polygon_svg
|
||||
| 1
|
||||
When sending <format> search query "switzerland"
|
||||
Then result 0 has attributes <response_attribute>
|
||||
|
||||
Examples:
|
||||
| format | response_attribute
|
||||
| xml | geosvg
|
||||
| json | svg
|
||||
| jsonv2 | svg
|
||||
|
||||
|
||||
Scenario Outline: Search result contains KML geometry
|
||||
Given the request parameters
|
||||
| polygon_kml
|
||||
| 1
|
||||
When sending <format> search query "switzerland"
|
||||
Then result 0 has attributes <response_attribute>
|
||||
|
||||
Examples:
|
||||
| format | response_attribute
|
||||
| xml | geokml
|
||||
| json | geokml
|
||||
| jsonv2 | geokml
|
||||
|
||||
|
||||
Scenario Outline: Search result contains GEOJSON geometry
|
||||
Given the request parameters
|
||||
| polygon_geojson
|
||||
| 1
|
||||
When sending <format> search query "switzerland"
|
||||
Then result 0 has attributes <response_attribute>
|
||||
|
||||
Examples:
|
||||
| format | response_attribute
|
||||
| xml | geojson
|
||||
| json | geojson
|
||||
| jsonv2 | geojson
|
||||
|
||||
Reference in New Issue
Block a user