2023-10-13 22:32:03 +03:00
|
|
|
@SQLITE
|
2016-12-29 00:57:52 +03:00
|
|
|
@APIDB
|
|
|
|
Feature: Places by osm_type and osm_id Tests
|
2018-09-16 18:16:42 +03:00
|
|
|
Simple tests for response format.
|
2016-12-29 00:57:52 +03:00
|
|
|
|
|
|
|
Scenario Outline: address lookup for existing node, way, relation
|
2021-01-09 18:59:46 +03:00
|
|
|
When sending <format> lookup query for N5484325405,W43327921,,R123924,X99,N0
|
2019-07-22 00:20:48 +03:00
|
|
|
Then the result is valid <outformat>
|
2016-12-29 00:57:52 +03:00
|
|
|
And exactly 3 results are returned
|
|
|
|
|
|
|
|
Examples:
|
2019-07-22 00:20:48 +03:00
|
|
|
| format | outformat |
|
|
|
|
| xml | xml |
|
|
|
|
| json | json |
|
|
|
|
| jsonv2 | json |
|
|
|
|
| geojson | geojson |
|
|
|
|
| geocodejson | geocodejson |
|
2016-12-29 00:57:52 +03:00
|
|
|
|
|
|
|
Scenario: address lookup for non-existing or invalid node, way, relation
|
|
|
|
When sending xml lookup query for X99,,N0,nN158845944,ABC,,W9
|
|
|
|
Then exactly 0 results are returned
|
2019-08-06 00:32:46 +03:00
|
|
|
|
|
|
|
Scenario Outline: Boundingbox is returned
|
2021-01-09 18:59:46 +03:00
|
|
|
When sending <format> lookup query for N5484325405,W43327921
|
2019-08-06 00:32:46 +03:00
|
|
|
Then exactly 2 results are returned
|
2021-01-09 18:59:46 +03:00
|
|
|
And result 0 has bounding box in 47.135,47.14,9.52,9.525
|
|
|
|
And result 1 has bounding box in 47.07,47.08,9.50,9.52
|
2019-08-06 00:32:46 +03:00
|
|
|
|
|
|
|
Examples:
|
|
|
|
| format |
|
|
|
|
| json |
|
|
|
|
| jsonv2 |
|
|
|
|
| geojson |
|
|
|
|
| xml |
|
2022-11-16 23:11:56 +03:00
|
|
|
|
|
|
|
|
|
|
|
Scenario: Lookup of a linked place
|
|
|
|
When sending geocodejson lookup query for N1932181216
|
|
|
|
Then exactly 1 result is returned
|
|
|
|
And results contain
|
|
|
|
| name |
|
|
|
|
| Vaduz |
|