-
-
Notifications
You must be signed in to change notification settings - Fork 362
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
What type of gate is this? (Ask for gate:type
for all barrier=gate
)
#4507
Comments
I like detailed OSM data and love to collect these specific information, but what is actually the useful purpose of the |
@legofahrrad If it is tagged correctly, a router should be able to better decide which mode of transport the gate is suitable for. In addition, this quest should also be able to improve tagging. |
I don't see a useful purpose for that either. To check if current data is correct is a weak argument. |
Also, linked wiki stating:
is not too reassuring (at the moment)... |
General
Affected tag(s) to be modified/added: gate:type
Question asked: What type of gate is this?
Checklist
Checklist for quest suggestions (see guidelines):
There are three different tagging styles available but I would say "gate:type" has been established with 16k uses compared to 2k and 0,5k uses for
gate
andgate_type
When it is a
barrier=gate
, then one of the answers should match. Otherwise it's not abarrier=gate
or leave a note.I want to leave this open yet, as I suspect it's like the shelter_type quest: too many possible answers and probably too difficult to distinguish them. (shelter_type quest #4428)
The answer will definitely come very often, as the tag is not very common yet, but there shouldn't be a barrier=gate on every corner either.
There are more then 4 million barrier=gate out there, but only ~ 20k have a specific "type of gate" tag.
Ideas for implementation
Element selection:
nodes with barrier=gate and (!gate:type or !gate_type or !gate) )
Proposed UI:
Same UI as in stile quest #3372
The text was updated successfully, but these errors were encountered: