-
-
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
unsolved quests, buildings without number #1052
Comments
Although this issue is written more concise and to the point, it is a duplicate of #351. |
Query currently excludes buildings with addr:housename tag, this building has only name tag https://www.openstreetmap.org/way/103360633 Maybe
|
I think
Hmm, in my opinion, not. Names might be i.e. (translated from German)
All of these have actual house numbers. Especially for the case that there is a certain amenity in a building (only), it will definitely have a name. "House names" as addresses are a thing mostly on the British Isles, as far as I know (don't remember if it is Ireland, Scotland or what) |
What about quests that can't be solved in the programmed way? For example there is this house (https://www.openstreetmap.org/way/103360633) that actually does not have a house number. Its also stated so on its homepage http://haus1-berlin.de/ (Waterloo Ufer o.Nr. (Nähe U1/ Hallesches Tor) 10961 Berlin).
I can of course just remove the quest on my device with "cant say", but because it is not possible to set a number here, it would be great to dismiss the quest completely for streetcomplete. Otherwise, people will stumble about this again and again.
But actually, that would need to set up an extra database, or to put special notes to the object or anything like that. Aside from that, no one knows if there might be a housenumber for this house in the future, but thats a very special case.
I think beside that example there will always be other cases where it is not possible to solve a problem like its intended by the quest programming, I would appreciate if there would be a more general option than just removing the quest from my personal view.
The text was updated successfully, but these errors were encountered: