-
-
Notifications
You must be signed in to change notification settings - Fork 359
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
Possible ambiguous description of the tactile pavement quest (crossings) #5173
Comments
See #3407 It is apparently referring to the ends of the crosswalk, despite being redundant to the kerb nodes, and even though it's tagging the crossing node, not the crossing way. IMO the crossing node should never have I don't think we're ever going to get any better explanation or change on this issue. |
@pkoby wrote:
I think we could improve the sentence and explain which sides are meant.
I there's a road with tagged sidewalks, how would you map curbs? This only works if you completely map the sidewalks as separate path. That's not a feasible amount of work for just tagging if there are tactile markings on the crossing. |
"Does this crosswalk have tactile paving on both sides?" seems pretty clear to me. That une_abeille had to explicity write in the diary entry that it should not mean what the wording in this app suggests but instead another thing is actually also an indicator for me that the wording is already clear.
What is your suggestion then to improve the wording? What would even be the problem with the current wording? |
From #3407 (comment)
"Sides" could mean sides of the street, where the ends of the crosswalk are, or sides of the crosswalk, e.g. along the length of it. "Ends" should have no other meaning. |
So you say "ends" is better than "sides"? |
Yes. |
Done, thanks |
There seems to be some room for confusions regarding tactile pavements on crossings, stemming from a vage osm Wiki article about it.
Currently StreetComplete is searching for
highway=crossing
nodes and asks if it should add yes/no totactile_paving
.However, there are crossings which feature tactile pavings along the crossing itself. So for this the same tag (
tactile_paving=yes/no
) is used. But on the actual way across the road, tagged withhighway=footway
andfootway=crossing
.As StreetComplete is only showing a pin and asks "on both sides?" there's no clear way to differentiate between both cases for the end user.
This lead one user, who misunderstood this, to explicitly explain this feature wrongly in a diary entry to other users, which probably lead to a lot of wrongly mapped data by this user:
Diary entry
I think this should be rephrased to be crystal clear what is and is not meant by this quest, to avoid such issues in the future.
Versions affected:
All until 53.3 (at least)
The text was updated successfully, but these errors were encountered: