Use polygon as search area overpass api / overpass turbo - openstreetmap

I'm fairly new at using overpass API, I finally managed to generate a query to retrieve all nodes within an area by using overpass-turbo wizard.
Using highway=* in "Paulino Navarro" in the wizard generates me the following query.
/*
This has been generated by the overpass-turbo wizard.
The original search was:
“highway=* in "Paulino Navarro"”
*/
[out:json][timeout:25];
// fetch area “Paulino Navarro” to search in
{{geocodeArea:Paulino Navarro}}->.searchArea;
// gather results
(
// query part for: “highway=*”
node["highway"](area.searchArea);
way["highway"](area.searchArea);
relation["highway"](area.searchArea);
);
// print results
out body;
>;
out skel qt;
However, how could I use a polygon as a search area? maybe something like highway=* in poly([lat,lon],[lat,lon],...,[lat,lon]) or how can I do that on the query itself.
I don't quite understand the documentation in overpass wiki nor overpass-turbo wizard.

The polygon filter is explained in the Overpass QL documentation.
Example:
[out:xml][timeout:30];
way[highway=primary](poly:"50.7 7.1 50.7 7.2 50.75 7.15");
(._;>;);
out;

If the polygon you want to query inside of is an OSM feature, you can also query using an area ID.
Area IDs are generated by the Overpass server to make querying data within existing polygons easier. You can determine the area ID for a way by adding 2400000000 to the way ID and the area ID for a relation by adding 3600000000 to the relation ID (assuming that the way or relation is a valid area feature).
Example:
[out:xml][timeout:30];
way[highway=primary](area:2400000001);
(._;>;);
out;

Related

Maplibre : Access 'way' and 'relation' ID from the mbtiles on the map - queryRenderedFeatures

I'm using the queryRenderedFeatures function from https://maplibre.org/maplibre-gl-js-docs/example/queryrenderedfeatures/ to query all features over the mouse on a MapLibre map.
I have access to all Node, and the id identified in the windows looks similar to the OSM ID (where the mbtiles seems to add a '0' at the end of the OSM ID :
mbtiles ID : 1230 corresponds to OSM ID N123)
(A) When I'm trying to access Way, the ID doesn't show up in the queryRenderedFeatures function
A console.log of the queried feature shows the ID as undefined
When I compare to the query on OpenStreetMap website, I can confirm that both return similar results by re-building the LineString output from MapLibre.
In other words, the query looks good and accurate, but I'm curious on how to fetch the OSM_ID from a way with this function ?
The source ID is road_path_pedestrian, with its source layer being Transportation for which I've added the osm_id (in case this could have been the root cause)
(B) as for the relation, is there any way to fetch those from the mbtiles (rendered or not) directly on the map ?
In the example above, the summit track has a relation on OSM that gathers all portions of the summit track ways. Is there a way to access as well the ID of this relation from the mbtiles, on the go ?
The objective is to have the user clicking on a path/track on a maplibre map, and the function to return the full OSM relation ID and LineString.
Exactly the same way it's currently done on OpenStreetMap website. For the same example, it would be the yellow track with its 7 members.
Thanks in advance for your support!

OpenstreetMap Overpass API - Validate tag if present

I have this query
[out:json];
(
way['addr:street'='Kurzenmoor']['addr:housenumber'='12']['addr:postcode'='25370']['addr:country'='DE'];
node(around:700)['highway'='bus_stop'][!'ref'];
);
out;
This does not return a result due to the fact that the country has not been specified at the API.
This works:
[out:json];
(
way['addr:street'='Kurzenmoor']['addr:housenumber'='12']['addr:postcode'='25370'];
node(around:700)['highway'='bus_stop'][!'ref'];
);
out;
Is there a way to combine these? If there is no country present, I want the result, if there is a country present it should match the desired one (in this example "DE", if it matches, I want the result, otherwise I do not want it.
Overpass API is not a geocoder.
A better approach is to first determine the location via geocoding, e.g. by using Nominatim, Photon or one of the other OSM-based geocoders. In the second step use Overpass API to find bus stops near this location.

Get more details for given coordinates using overpass api

I am currently using this query (API URL) to get the county name from a coordinate.
[out:json];
node[place='county'](around:20000.0,49.8728,8.6512);
out;
I wish to have more details like state, city etc etc along with county. Any help would be greatful.
I guess you want to use is_in instead:
is_in(49.8728,8.6512);
out;
try it in overpass turbo: http://overpass-turbo.eu/s/k2p
Also see this very similar question: Administrative relations of a place with openstreetmap

Overpass API way coordinates

I'm trying to query the OSM Overpass API to find any amenities within a bounding box. The actual query in my program will be generic but in my testing I noticed I cannot retrieve the coordinates(latitude, longitude) of any of the ways. Here is my script:
(
node
["amenity"="police"]
(39.235,-76.715,39.373,-76.525);
way
["amenity"="police"]
(39.235,-76.715,39.373,-76.525);
);
(._;>;);
out meta;
I need to use ways because I'm missing a significant amount of data without them. Unfortunately they do not include any coordinate data despite me adding out meta instead of the normal out. This was answered here, overpass-api ways query include coordinates about a year ago but that solution no longer works. Is this a bug? Or am I doing something wrong? I've also tried out center, out geom, and out skel to no success. I'm outputting the data in xml.
ANSWERED, I left on the recursion line on the end by accident. Thanks Tyr.

Getting Streets of a specific postcode using Open Street Maps

I want to write a code that has the Countrycode and Postcode as an input and the ouput are the streets that are in the given postcode using some apis that use GSM.
My tactic is as follows:
I need to get the relation Id of the district. For Example 1991416 is the relation id for the third district in Vienna - Austria. It's provided by the nominatim api: http://nominatim.openstreetmap.org/details.php?place_id=158947085
Put the id in this api url: http://polygons.openstreetmap.fr/get_wkt.py?id=1991416&params=0
After downloading the polygon I can put the gathered polygon in this query on the overpass api
(
way
(poly: "polygone data")
["highway"~"^(primary|secondary|tertiary|residential)$"]
["name"];
);
out geom;
And this gives me the streets of the searched district. My two problems with this solution are
1. that it takes quite a time, because asking three different APIs per request isn't that easy on ressources and
2. I don't know how to gather the relation Id from step one automatically. When I enter a Nominatim query like http:// nominatim.openstreetmap.org/search?format=json&country=austria&postalcode=1030 I just get various point in the district, but not the relation id of the searched district in order to get the desired polygone.
So my questions are if someone can tell my how I can get the relation_Id in order to do the mentioned workflow or if there is another, maybe better way to work this issue out.
Thank you for your help!
Best Regards
Daniel
You can simplify your approach quite a bit, down to a single Overpass API call, assuming you define some relevant tags to match the relation in question. In particular, you don't have to resort to using poly at all, i.e. there's no need to convert a relation to a list of lat/lon pairs. Nowadays the concept of an area can be used instead to query for certain objects in a polygon defined by a way or relation. Please check out the documentation for more details on areas.
To get the matching area for relation 1991416, I have used postal_code=1030 and boundary=administrative as filter criteria. Using that area you can then search for ways in this specific polygon:
//uncomment the following line, if you need csv output
//[out:csv(::id, ::type, name)];
//adjust area to your needs, filter critera are the same as for relations
area[postal_code=1030][boundary=administrative]->.a;
// Alternative: {{geocodeArea:name}} -> see
// http://wiki.openstreetmap.org/wiki/Overpass_turbo/Extended_Overpass_Queries
way(area.a)["highway"~"^(primary|secondary|tertiary|residential)$"]["name"];
(._;>;);out meta;
// just for checking if we're looking at the right area
rel(pivot.a);out geom;
Try it on overpass turbo link: http://overpass-turbo.eu/s/6uN
Note: not all ways/relations have a corresponding area, i.e. some area generation rules apply (see wiki page above). For your particular use case you should be ok, however.