safety-screen/Nominatim
1
0
Fork 0
forked from hans/Nominatim
Code Pull Requests Activity

only return polygon if &polygon_geojson=1 is set

Browse Source
This commit is contained in:
Marc Tobias Metten
2018-03-19 01:34:48 +01:00
committed by Sarah Hoffmann
parent 45bc511955
commit 0eb71cdce8
4 changed files with 87 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files

43
test/bdd/api/details/params.feature Normal file
View File

@@ -0,0 +1,43 @@
@APIDB
Feature: Object details
Testing different parameter options for details API.
Scenario: JSON Details
When sending json details query for W78099902
Then the result is valid json
And result has attributes geometry
And result has not attributes keywords,address,linked_places,parentof
Scenario: JSON Details with keywords
When sending json details query for W78099902
| keywords |
| 1 |
Then the result is valid json
And result has attributes keywords
Scenario: JSON Details with addressdetails
When sending json details query for W78099902
| addressdetails |
| 1 |
Then the result is valid json
And result has attributes address
Scenario: JSON Details with linkedplaces
When sending json details query for R123924
| linkedplaces |
| 1 |
Then the result is valid json
And result has attributes linked_places
Scenario: JSON Details with childplaces
When sending json details query for W78099902
| childplaces |
| 1 |
Then the result is valid json
And result has attributes parentof
Scenario: JSON Details with linkedplaces
When sending json details query for R123924
| linkedplaces |
| 1 |
Then the result is valid json

61
test/bdd/api/details/simple.feature
View File

@@ -3,15 +3,30 @@ Feature: Object details
Check details page for correctness
Scenario Outline: Details via OSM id
When sending details query for <object>
Then the result is valid html
When sending <format> details query for <object>
Then the result is valid <format>
Examples:
| object |
| 492887 |
| N4267356889 |
| W230804120 |
| R123924 |
| format | object |
| html | 492887 |
| json | 492887 |
| html | N4267356889 |
| json | N4267356889 |
| html | W230804120 |
| json | W230804120 |
| html | R123924 |
| json | R123924 |
Scenario Outline: Details via unknown OSM id
When sending <format> details query for <object>
Then a HTTP 400 is returned
Examples:
| format | object |
| html | 1 |
| json | 1 |
| html | R1 |
| json | R1 |
Scenario: Details with keywords
When sending details query for W78099902
@@ -19,35 +34,3 @@ Feature: Object details
| 1 |
Then the result is valid html
Scenario: JSON Details
When sending json details query for W78099902
Then the result is valid json
And result has not attributes place_search_name_keywords,place_search_address_keywords,address_lines,linked_lines,parentof_lines
Scenario: JSON Details with keywords
When sending json details query for W78099902
| keywords |
| 1 |
Then the result is valid json
And result has attributes place_search_name_keywords,place_search_address_keywords
Scenario: JSON Details with addressdetails
When sending json details query for W78099902
| addressdetails |
| 1 |
Then the result is valid json
And result has attributes address_lines
Scenario: JSON Details with linkedplaces
When sending json details query for R123924
| linkedplaces |
| 1 |
Then the result is valid json
And result has attributes linked_lines
Scenario: JSON Details with childplaces
When sending json details query for W78099902
| childplaces |
| 1 |
Then the result is valid json
And result has attributes parentof_lines