Skip to content
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

document intended usage add add reference implementation #2

Open
willtemperley opened this issue Aug 30, 2016 · 1 comment
Open

document intended usage add add reference implementation #2

willtemperley opened this issue Aug 30, 2016 · 1 comment
Labels

Comments

@willtemperley
Copy link

willtemperley commented Aug 30, 2016

Just looking at:
https://wiki.openstreetmap.org/wiki/Overpass_turbo/Polygon_Features

I'm wondering why area=no isn't simply blacklisted in polygon-features.json?

@tyrasd
Copy link
Owner

tyrasd commented Aug 31, 2016

That's because how this is set up, area!=no is a prerequisite before one can go on to check further tags (just like that a feature must be a closed way to start with). Note that all the cases in polygon-features.json are or-ed together. So we can't simply blacklist area=no there, because then if the object had at least one other area-ish tag (e.g. barrier=wall + area=no), it could falsely be classified as an area.

I admit that there should be at least some documentation about this in the readme, and possibly also a basic reference implementation.

@tyrasd tyrasd closed this as completed Nov 4, 2016
@tyrasd tyrasd reopened this Nov 4, 2016
@tyrasd tyrasd changed the title area=no document intended usage add add reference implementation Nov 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants