-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow querying by object area/way length #464
Comments
I believe we already have an issue for this, so marking as duplicate of #237. Not sure what you mean by area “length”. Care to elaborate? |
I thought about two cases: way is closed, filtering by area is available and second: way is not closed and length is available |
A closed way doesn’t necessarily imply an area in an Overpass sense, e.g. if there’s no name tag... there are dedicated rules for area creation. |
Future syntax for non-closed ways with a certain min length will look as follows:
Check out the following example: http://overpass-turbo.eu/s/wGT As there's really nothing left to do here, kindly request to close this issue. Thanks! |
Thanks! Is it feasible to allow filtering by size (area) of closed way - like buildings, lakes etc? |
I don't recall if Roland already implemented such a function for area sizes, will cross check. |
Usecase example: finding mistagging like https://www.openstreetmap.org/way/222795099#map=19/52.51666/13.41946&layers=N or excluding them in program processing OSM data (I wanted to add this functionality in StreetComplete).
The text was updated successfully, but these errors were encountered: