-
-
Notifications
You must be signed in to change notification settings - Fork 366
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
Barrier=gate - What is the available opening #5678
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
There is also Barriers are that explicitly tagged as Also, one issue I see with this suggestion is that there are loads of gates mapped, and many are not actually public. The gates however are often not marked as But in any case, I think this is a useful addition for a quest! |
I had wondered about another quest to establish the access of the barrier, and only those not tagged as private would go on to the question about width, but your answer is much better. I find the subject of barriers quite complex, and decided to try to keep it simple and deal with one item for the quest request. However, very similar, and perhaps could be included within this, could be;
I haven't included cycle_barrier=double or cycle barrier=triple, because I think they will need dealing with individually with diagrams and wording to individually suit. cycle_barrier=tilted is difficult because you need to define at what height(s) to take the width measurement. or perhaps keep it simple, deal with barrier=gate and then deal with each of the others, one at a time, with diagrams and text individual to the particular barrier? |
|
I've read the guide to contributing a quest and I would like to work on this quest. Let me know if this would cause problems, thanks. |
Cool, go ahead! |
I've started working on this, but am unsure if I should, at this stage, just deal with barrier=gate,, and add subsequent quests to deal with bollards, blocks, cycle_barriers. I have been trying to combine bollards, blocks, and some cycle_barriers, but think that the filters, strings and icons may be very confusing. |
As the type of element is already written below the question, the question should be worded generically, like "What's the maximum width here" or something. Maybe could even use the same string as for the street-maxwidth quest. The icon can be the same for gates, etc, e.g. a wall with an entrance or a gate plus a ruler. Regarding other elements, let's go with |
The icon could also be the wheelchair icon with a ruler, hinting at for whom this information might be useful and thus which width to use if there are different widths depending on the height. (I.e. take the minimum width, don't assume that people can wiggle through) |
* Check values in Form, * General check of files - although it builds, it will not run, * New icon needed at some point, * Need to filter out the gates etc which are on private roads etc - waiting until after the more general files are working first .. issue streetcomplete#5678 refers
…test on phone (emulator does not have streetmeasure, and won't seem to load it. streetcomplete#5678 refers Also still needs an icon.
"What is the available opening through this gateway"
To be applied to barrier=gate
tag to be added maxwidth:physical=
Checklist
Checklist for quest suggestions (see guidelines):
🚧 To be added tag is established and has a useful purpose
barrier=gate is common with over 5,000,000 instances https://taginfo.openstreetmap.org/tags/barrier=gate#overview
maxwidth:physical= has just over 2,800 instances https://taginfo.openstreetmap.org/keys/maxwidth:physical#overview. It's possible that mappers have used other tags such as maxwidth= ( the legal restriction on size ) with 50,000 uses https://taginfo.openstreetmap.org/keys/maxwidth#overview or width= with over 3,000,000 uses - not sure how many of these would refer to gates. But even with these figures there are many gates / gateways with no tag showing their available opening.
Without an indication of the gap available it's difficult to know if a particular item will fit through - this could be too narrow for a pram / pushchair to fit through or so wide that two buses can pass through together.
Adding a measurement of the available opening makes it possible to start to create navigation for such vehicles as electric wheelchairs, tricycles, hand powered cycles, larger electric vehicles for disabled users such as the Tramper mobility scooter https://www.tramper.co.uk/products/tramper
🤔 Any answer the user can give must have an equivalent tagging (Quest should not reappear to other users when solved by one)
Once the tag maxwidth:physical= is applied to the barrier=gate node or way, this particular quest is complete and should not show for other surveyors.
🐿️ Easily answerable by any pedestrian from the outside but a survey is necessary
A similar screen to that which appears for users solving the road width quest would be suitable - I've tested the StreetMeasure app using a tape measure, and with care measurements of 0.5 metres can be obtained quite accurately.
💤 Not an overwhelming percentage of quests have the same answer (No spam)
There's a lot of variations in gates!
🕓 Applies to a reasonable number of map data (Worth the effort)
Worldwide potential for over 5,000,000 items.
Notes
There appear to be many nodes and ways which have been tagged as 'barrier=gate', but there is actually more than one gate present - double gates are common across driveways, agricultural premises, and many other instances. To avoid confusion I suggest that the question refers to the gateway rather than the gate. The term 'opening' is easier for a non-mapper to understand, and indeed the maxwidth, width and maxwidth:physical descriptions seem to confuse many experienced mappers.
It may be that the gate already has a width= or maxwidth= tag - I leave it up to discussion as to how the quest should be filtered. Personally I'm happy to believe that a mapper who tagged width or maxwidth= means the width of the opening, and that is acceptable to me.
Within the er...... section there should be an option to show that the gate is no longer present.
The text was updated successfully, but these errors were encountered: