-
-
Notifications
You must be signed in to change notification settings - Fork 364
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
Show the house numbers in all house-related quests #1971
Comments
I admit that it would be useful, even with housenumbers visible on the map I sometimes did cancel-look at map-restart quest. Though it would increase workload for translators. |
At least the English word "house number" exists as a separate item in POEditor (label_housenumber). Couldn't this be reused? Alternatively, the house number in parantheses should be sufficient (or would this be too confusing for some users)? The cycling cat |
In light of them missing from the map (currently), this would be an enhancement. |
The info could be added in the same place where the info about the level of a feature is placed and always for every quest if the housenumber/name/streetnumber/etc. info is available. Then, the wordings of the quests that currently contain the housenumber in the question can be removed because that info is available just below the question. Example: #1270 (comment) What do you think? |
I really, really like this solution. |
Then I shall merge it |
A suggestion:
Always show the house numbers (if available) as part of the quests which relate to houses (house type, roof shape, number of stories and so on). A house number is typically very short (1-3 digits plus 0-2 extensions like letters and special characters) and gives the user more certainty that he is tagging the right building, especially in regions with many similar looking houses and/or bad sat reception.
This would also help mitigate issue #1939 (but there would be no need to remove this feature once #1939 is fixed IMHO).
The cycling cat
The text was updated successfully, but these errors were encountered: