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
Maxspeed quest : Ensure contributors choose between implicit and explicit maxspeeds before submitting #1085
Comments
I took the liberty of adding them here on github. The mockup as such looks good, only for implicit speed limits it is not that easy and IMO needs more explanation - in other words, in the "worst" case, the UI flow after having selected "implicit speed limit" would stay the same. What are the opinions of the other regulars here? |
Looks OK, though normal person may be surprised by "implicit speed limit" term (and maybe also by "living street"), but I see no way to avoid it. |
I agree that "implicit" could be more explicit :) When showing the urban/extra-urban choice the user should understand, but as @matkoniecz there could be better way to express that. Living street (translated) + the sign sound easy enough to understand imo. |
(If someone else wouldn't do this, this will probably not find its way into v6) |
Put some more thought into this (and started it on a private branch). A few comments:
|
What got us here is that if users are given a default, easy answer they will most likely ignore other answers (and they do). Making the user choose between 4 options slows down maybe the first one or two contributions, but will make sure that they makes a conscious decision between them, and not just doing as little as possible to validate the quest with incorrect data. Another example I've also started a private branch but I'm not used to Android development, so I didn't want to give any false hope by annoucing it. But since the issue is blocked on an external and open-ended task that will likely never be considered as complete, I will stop devoting time for it, except if we find another solution that is implementable in the near future. Should the quest be disabled for the time being ? As an aside : a road being designed as a "living street" does define a legal speed limit in a lot of coutries. |
That's why we have an option to select that. So what is actually blocking this issue? |
I second to the fact that while using streetcomplete for first time I have automatically filled 50kmh speed limit onto every urban road i came across. Only after some time i noticed there are other options to choose from. As a result of my experience As a translator I have rephrased the string in poeditor to be more precise about sign. In my czech language I have currently worded main quest question appearing after clicking on icon as something like that: This sounds very clearly i think. |
@StanislavTichy Sadly, even with this wording and the speed sign graphic, senior contributors make the mistake. That's why I opened this issue and pushed towards making the user choose between speed limit types and not assuming that they understood what type the default type is. |
With the current wording/UI many quest answers are incorrect in France, as often maxspeed is implicit and do not require maxspeed signs. However, as the UI is biased towards sign-based speed limits, both new and seasoned users are using the default choice without checking the "other options".
At least half of those ways shouldn't have maxspeed_type=sign, as 50 kph/kmh is the default speed limit in urban areas, so those ways don't have a sign.
I believe displaying both implicit and explicit maxspeeds choices equally would reduce errors, while not impeding input. Here is an UI mockup:
The text was updated successfully, but these errors were encountered: