-
-
Notifications
You must be signed in to change notification settings - Fork 358
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
Forced to enter (possibly) redundant information, suggesting new workflow for UI #1017
Comments
Are you aware that it is possible to change priority of quests in settings and disable unwanted ones? For example I disabled cycleway quests, as in my region cycleways are well mapped and I consider "none on left, none on right" x several hundred (thousands?) times as boring. |
I didnt know about sorting them but I did know about disable. But thats what I mean with "tweak the app". Sometimes I come across a road that HAS a cycleway - and then I have to enable that quest in order to see if is a current quest or not - AND make sure that that quest isnt hidden by some other quest. Just tell me that "this road has possible quests" and let me pick which one i want to do. |
This is a reasonable feature request, but iirc correctly it has been requested before. I think there should be a ticket for that somewhere, if not, it is in my head. The reason why it cannot be done right now is because it would require implementing changes closely related to the map rendering. However, any features regarding the map rendering are deferred indefinitely as long as the future of the map rendering library tangram-es is not clear yet. |
Regarding tagging "no", @matkoniecz hit the nail with posting the FAQ entry. |
I see the FAQ makes specific cases on this topic, and I would say that one can make arguments for both sides about the bike lanes. |
and
Indeed, there is. I found it: #124 It still waits for to be implemented… 😄 |
Yes. I imagined just one icon on the map that opens a menu-ish list or dropdown (one way or another) to pick the quest you wish to resolve. |
If you have another suggestion which was not yet suggested in #124 you should post it there because this issue here has been already closed. |
I have an issue with how StreetComplete gives you quests. Specifically regarding cycleways.
The issue I am raising is that StreetComplete is currently a contributor in adding "cycleway:both=no". This type of information can be defined as either implicit or unknown, but that definition depends on the commonality of yes vs. no. If there is a 50-50 split between yes and no the implicit answer is "unknown", if it is 90-10 the implicit is no.
In the case of bike lanes I would suggest that the ratio of roads WITH bike lanes is in vast minority and that all roads should be considered to NOT have bike lanes unless stated otherwise.
Adding "no"-tags to things is bad practice for most things, like "oneway=no", "boat=no" or on the reverse side "motor_vehicle=yes" on major roads.
Now to my issue with StreetComplete as an app. The way the app works right now is to show you the quests you have enabled in sequence. You have to do one quest in order to get the next one. This means that if you want to set something like road surface or lit you have to do the bike lanes first (I dont know the specific order but this is an example). That means you either have to go through the "I dont know, leave not, yes/no" ordeal or in the case of bike lanes say "no".
I would suggest that each item WITH quests to them should have an icon "this has quests" and let the user click that and pick which quest to do. That way house numbers dont block opening hours, road speeds dont block road surface - etc. It would simply be more handy.
That would make it easier to map while moving. Even while walking it can take longer to hide quests and tweak the app than it takes to walk the street, and quite impossible if you are in a car (or on a train - which I have tried).
tl;dr - let the user pick which quest to do on each item rather than have them in sequence, this will avoid unnecessary tagging and notes and allow a faster UI while mapping while moving.
The text was updated successfully, but these errors were encountered: