Closed sjakobi closed 2 years ago
Hmm, I'm failing to reproduce the issue in a different browser. I suspect the result set may have been cached from an earlier query. Does this seem plausible? What would be a good way to prevent this issue?
Your query is bad, by adding [covered=yes] you’re including rather than excluding nodes with such tagging.
As this is more of a how-to question, maybe try one of the community help sites instead.
Your query is bad, by adding [covered=yes] you’re including rather than excluding nodes with such tagging.
The unexpected nodes don't even have a covered
field, so I think they ought to be filtered out?!
Anyway, I can't reproduce the issue any more, so I'll close this.
Thanks for this great tool, in any case! :)
https://overpass-turbo.eu/s/1mdI returns several nodes that I meant to remove by specifying
[covered=yes]
, e.g.Is my query bad or might these results indicate a bug in the app?