2 Feature: Parameters for Reverse API
3 Testing different parameter options for reverse API.
5 Scenario Outline: Reverse-geocoding without address
6 When sending <format> reverse coordinates 53.603,10.041
9 Then exactly 1 result is returned
10 And result has not attributes address
18 Scenario Outline: Reverse Geocoding with extratags
19 When sending <format> reverse coordinates 10.776234290950017,106.70425325632095
22 Then result 0 has attributes extratags
30 Scenario Outline: Reverse Geocoding with namedetails
31 When sending <format> reverse coordinates 10.776455623137625,106.70175343751907
34 Then result 0 has attributes namedetails
42 Scenario Outline: Reverse Geocoding contains TEXT geometry
43 When sending <format> reverse coordinates 47.165989816710066,9.515774846076965
46 Then result 0 has attributes <response_attribute>
49 | format | response_attribute |
54 Scenario Outline: Reverse Geocoding contains polygon-as-points geometry
55 When sending <format> reverse coordinates 47.165989816710066,9.515774846076965
58 Then result 0 has not attributes <response_attribute>
61 | format | response_attribute |
62 | xml | polygonpoints |
63 | json | polygonpoints |
64 | jsonv2 | polygonpoints |
66 Scenario Outline: Reverse Geocoding contains SVG geometry
67 When sending <format> reverse coordinates 47.165989816710066,9.515774846076965
70 Then result 0 has attributes <response_attribute>
73 | format | response_attribute |
78 Scenario Outline: Reverse Geocoding contains KML geometry
79 When sending <format> reverse coordinates 47.165989816710066,9.515774846076965
82 Then result 0 has attributes <response_attribute>
85 | format | response_attribute |
90 Scenario Outline: Reverse Geocoding contains GEOJSON geometry
91 When sending <format> reverse coordinates 47.165989816710066,9.515774846076965
94 Then result 0 has attributes <response_attribute>
97 | format | response_attribute |