Affected key(s) (or tags) to be modified: step_count
Question asked: How many steps does this stair have?
Checklist for quest suggestions (see guidelines):
Element selection: [see this overpass-turbo query](
Affected key(s) (or tags) to be modified: step_count
Question asked: How many steps does this stair have?
Checklist for quest suggestions (see guidelines):
Element selection: see this overpass-turbo query
Metadata needed: I can't think of any
Proposed GUI: Doesn't require more than an integer input. Like the maxspeed quest, just without the traffic sign around.
Other answers:
conveying=yesRelated with #503
Speaking from my point of view, I would say that for steps with a huge amount of steps, it can be pretty annoying to count all steps and maybe even lead to put in fake or guessed data...
I hope that users disable a quest if they think it is to annoying to complete ...
This should be the normal case, but I think that we can't expect the user to do this... There are maybe even users who don't know at all how to disable a quest. And there might be people who see this app as a game and the one who answers the most questions "wins" :smile:
Is there method to query on overpass ways by length? From #503 it seems that this data may have some use mostly for very short steps. Also, it would be far more reasonable to count steps up to say 20.
Hmm, I am going to mark it as quest, but the discussion in #503 should be kept in mind before thinking about implementing this quest.
but I think that we can't expect the user to do this...
Then make it opt-in.
Maybe point out that the amount of steps should just be input if the step is straight, and not tilted on one side, leading to an uneven amount of steps over the width of the steps and also just insert the exact count of steps. :)
Given https://github.com/tyrasd/overpass-turbo/issues/364 it seems to be impossible to currently query by way length - as result there is no sane way to exclude extremely long steps (I would not consider filtering by length in StreetComplete itself as a good idea).
I find this is not a blocker. By the way, even if it were, StreetComplete could still query simply all steps and filter out by measuring the length of the ways itself.
Speaking of living in a city with an overwhelming amount of extreme long steps, I wouldn't hesitate to just walk them in one direction just counting the steps. Why not. :)
Yes, that's true.
That the user should rather skip a quest instead of completing it messily is a topic not only affecting this quest
But maybe there could be a note like "plaease enter the exact number of steps" but it shouldn't make the whole quest impossible ...
See https://github.com/drolbr/Overpass-API/issues/464#issuecomment-370218992 - in future it will be possible to filter ways by their length.
Still think a length filter is not necessary for this quest. IMHO the longer the steps are the more usefulness has the data added in the quest in general. It might be more important to know how much steps you need for a big than a short step. (except of very short steps, where this information is useful for wheelchair users etc.)
Did I miss an issue about adding the direction of steps? Which side is the "up" direction?
https://wiki.openstreetmap.org/wiki/Key:incline
Most occurrences of this tag are on steps (highway=steps), usually tagged with incline=up or incline=down.
Should I open a new issue?
Should I open a new issue?
Probably yes - seems to be not covered so far https://github.com/westnordost/StreetComplete/search?q=incline&type=Issues
At least as long as it fulfills requirements for quests, but it should not be a problem.
app/src/main/res/values/strings.xml:
typo in: "
=>many
corrected, thanks!
Most helpful comment
Then make it opt-in.