-
-
Notifications
You must be signed in to change notification settings - Fork 365
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
add location to buildings with negative layer from -1 to -5 #912
Comments
You could simplify the query to |
Well, in StreetComplete, one can use a simplified tag query syntax anyway: |
Hmm, don't understand this quest. So this is basically correcting a tagging mistake (only tagging layer=). Here something is tagged with |
I think it is needed, because without that location=underground tag, there will be underground train stations displayed as normal overground buildings on the map of SC... |
Yes.
At least for me at this moment it is not entirely clear. If that object is entirely underground, I would add also location=underground.
building:levels:underground=1 may be given to any object that has 1 level underground, not only ones entirely underground.
I would add it because it is useful tag explaining situation, not just because one particular data consumer relies on it. |
fixes streetcomplete#912 this a bit unusual quest help to fix one of common tagging mistakes main use of adding missing location=underground in case of SC is to skip this weird buildings in other quests
fixes streetcomplete#912 this a bit unusual quest help to fix one of common tagging mistakes main use of adding missing location=underground in case of SC is to skip this weird buildings in other quests
General
Affected tag(s) to be modified/added: location
Question asked: Is this building is existing and located underground?
Checklist
Checklist for quest suggestions (see guidelines):
Ideas for implementation
Element selection: http://overpass-turbo.eu/s/wv2
Metadata needed: no
Proposed GUI:
Related GUI:
Inspired by #907
The text was updated successfully, but these errors were encountered: