Closed GniLudio closed 2 weeks ago
Nominatim by default doesn't import boundary=land_area
(https://github.com/osm-search/Nominatim/blob/master/settings/import-extratags.lua near line 85). As you've seen it often leads to duplicates with boundary-administrative
of the same name.
What did you hope to be able to do with the result data?
Nominatim by default doesn't import
boundary=land_area
(https://github.com/osm-search/Nominatim/blob/master/settings/import-extratags.lua near line 85). As you've seen it often leads to duplicates withboundary-administrative
of the same name.What did you hope to be able to do with the result data?
I want to get the GeoJSON of places in germany by their 'de:amtlicher_gemeindeschluessel'
and 'de:regionalschluessel'
.
So I get the IDs from Overpass and then tried to get the GeoJSON from Nominatim, but that didn't work for this one.
But now I know that I should just ignore land_area
s.
https://github.com/tyrasd/osmtogeojson can convert Overpass output to geojson. There are many (https://github.com/tmcw/awesome-geojson), some even have the same name, but this one worked for me on a similar project.
What did you search for?
When I use the following query in Overpass for the german state
Schleswig-Holstein
(Link)it returns two relations which represent roughly the same area (51529, 62775)
If I use the second ID for
Search By ID
in Nominatim (Link), I get an error:What result did you get?
No place with that OSM ID found.
What result did you expect?
The details of the relation with ID
62775
: Relation 62775 on OpenStreetMapFurther details