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

Merge pull request #4020 from kad-link/fix/add-admin-level-in-extratags

Browse Source 
fix: add admin_level in extratags for boundary=administrative
This commit is contained in:
Sarah Hoffmann
2026-03-10 22:42:45 +01:00
committed by GitHub
parent f11b21b0ba b71389274b
commit c44cac4c22
6 changed files with 139 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
test/bdd/features/api/search/params.feature
View File

@@ -318,6 +318,28 @@ Feature: Search queries
| jsonv2 | json |
| geojson | geojson |
Scenario Outline: Search boundary=administrative with extratags=1 returns admin_level
When sending v1/search with format <format>
| q | featureType | extratags |
| Triesenberg | city | 1 |
Then a HTTP 200 is returned
And the result is valid <outformat>
And more than 0 results are returned
And result 0 contains
| <cname> | <tname> |
| boundary | administrative |
And result 0 contains in field <ename>
| param | value |
| admin_level | 8 |
Examples:
| format | outformat | cname | tname | ename |
| xml | xml | class | type | extratags |
| json | json | class | type | extratags |
| jsonv2 | json | category | type | extratags |
| geojson | geojson | category | type | extratags |
| geocodejson | geocodejson | osm_key | osm_value | extra |
Scenario Outline: Search with namedetails
When sending v1/search with format <format>
| q | namedetails |