Open bramws opened 1 month ago
You should use the wizard with the input "historic=castle". This would create a query including ways (and relations) which your current query misses.
Thank you, indeed with this query is works fine for the castle:
/ This has been generated by the overpass-turbo wizard. The original search was: “historic=castle” / [out:json][timeout:25]; // gather results nwr"historic"="castle"; // print results out geom;
The problem is our query is our native app with graphHopper. Was there a change in the last weeks?
graphHopper is a routing engine. I have no idea what your problem is with it. I do not know its api. Please try https://community.openstreetmap.org/
Thank you. For your information GraphHopper has also a Geocoding API https://docs.graphhopper.com/#tag/Geocoding-API
We receive help from OSM Belgium. The problem was we only search on Nodes and not on Way & Relation. The nwr["historic"="castle"] search on nodes, way & relation. Some of the historic data is changed from Nodes to Way or Relation.
Node: A single point with coordinates, used for simple points of interest (POIs) and as building blocks for more complex structures.
Way: A series of nodes that form a line or area, used for roads, boundaries, and regions.
Relation: A group of nodes, ways, and/or other relations, used to describe complex connections and structures.
We use OSM tags for our app, since a few weeks we have an issue mostly with the historic tags. There a lot of castles who are tagged with historic=castle but the overpass turbo find only a few and we have the same issue with other historic tags.
I give an example around Brussels Belgium
https://overpass-turbo.eu/ node [historic=castle] ({{bbox}}); out;
He find only one castle but there are a lot more on the map and also tagged. We have the same issue with graphHopper so maybe the issue is not related to overpass turbo.
Thank you for your help.