-
-
Notifications
You must be signed in to change notification settings - Fork 359
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
quest for missing addr:street #213
Comments
Now designed in a way that it can be used for other quests as well, i.e. for #213
I would like to mention that this quest would make sense for my current mapping efforts in Austria as well. So if you implement it, please don't restrict it only to Poland :) |
Same in France :) |
The quest will not be limited to certain countries but limited to house number 1,2(,3,4). |
Hmm, I guess this is better than restricting it to Poland, I still wish I could turn it on independent of housenumbers. |
|
Ah, very nice, thanks rugk. |
Also note that some mapping communities use relations instead of addr:street. Thanks. |
In same cases the you can interpolate the addr:street using the street next to the housenumber. At housenumbers on intersections it is difficult to automate it. Streetcomplete should also ask for the addr:street with a short list of the named roads next to building, including option "none of them" for creating a note. |
Looking at it again: my plan is to reuse add road name quest interface, it even has (a bit hidden, I noticed it only now) option to select nearby road name. |
One tricky part: one should exclude addresses with addr:place addresses and include only addresses with named road nearby, In places without named roads addr:place is used instead. In such cases addr:place may be easily added using armchair editing and quest is not necessary. Given that there may be incorrectly named road nearby or road from separate settlement with named roads there should be also option "this address has no named road" allowing to add addr:place. See for example https://www.openstreetmap.org/node/5037711319 found by http://overpass-turbo.eu/s/vT6 |
My plan is to
Still, it is necessary to provide option "This address is not assigned to a named road, settlement name is used instead" that will allow to set "addr:place". Both addr:street and addr:place should have suggestion pool populated by nearby streets and places (or maybe nearby addr:street and addr:place)? helper query used to verify whatever I missed YA valid tagging scheme: http://overpass-turbo.eu/s/xJA |
Don't forget conscription numbers, street numbers and house names.
And this is the only option if only a conscription number is specified. No idea about conscription+streetnumber, would need to look into the wiki for how it is exactly.
Would make sense, but not required for a PR to be accepted. The suggestion pool for street names is already there. The one for place names would need to be implemented. |
@matkoniecz I don't think that it's a good idea to add redundant data to each building. Places should be defined by boundaries not by tags. |
@RubenKelevra Are you speaking about addr:place? In that case - where are regions without street names that do not add addr:place? How they mark addresses where addr:street is not necessary? |
@matkoniecz yep, I usually tag Someone here imported a huge amount of data, tagging each building with a postal code and city name, which makes no sense. I go ahead check of all buildings have the same postal code, tag it on the street and remove the city and postal code on the buildings. |
Only on buildings that a) have address b) address has no And I would do it only in areas where it is established tagging (so far I only checked address tagging standards in Poland where this scheme is used). Do you know how other places handle addresses in areas without street names? |
@matkoniecz alright, this sounds better. :)
Well, I came across many small suburbs in my area which has just a name like "Sonne", where basically 2 or 3 backroads meet. The address is than just "Sonne 3" or similar, while they are spread around those 2 or 3 streets. So the suburb is added to the street name and the addr:city is just the name of the city which this suburb belongs. EDIT: You can see this example here: https://www.openstreetmap.org/node/81709172 Those streets to south-west and north-east got a name attached, which isn't really a name on a streetname-sign. The street got officially no name. |
Current state research (done):
coding:
helper query used to verify whatever I missed YA valid tagging scheme: http://overpass-turbo.eu/s/xJA I am planning to make first version covering only Polish tagging and working only in Poland - it will be useful to catch problems and to pacify bot complaining about edits adding only part of address (affects people solving house number quest in Street Complete). JOSM requires Test cases: |
BTW, if it interpolates a street name from a nearby street and is really sure that this is the right street (I.e. there is no other street nearby), it should pre-enter/fill that name into the input, so the user only has to confirm the street number. |
I plan to do something similar to road name quest with easy reuse of nearby names. I run into an implementation issue: My plan was to display "What is the street of this address?" quest title, with text box. To handle case where there is no street name and After selecting it user would enter place name into text field. But it turns out that there is no good way to change the "What is the street of this address?" quest title to something like "In which settlement this address is located?". I thought about adding place name in popup, so the now outdated title would not confuse people. |
The title also does also not change for any other quest, for example the housenumber quest when selecting that there is no number but a name. The answer-UI simply changes. That has never been a problem. The input field could have a label, like Maybe, the input field for the place name could look different from the street input field. I propose a blue sign with white frame for the street name and a white sign with a black frame for the place name - or maybe even this |
Note: The quest may only be asked for addresses with missing street names that are not part of a associatedStreet relation or similar. |
associatedStreet is already covered in test version of quest, do you know about any similar relations that also should cause exclusion? |
@westnordost What you think about icon for this quest? I though about taking "What is the name of this road" and changing background to one use by a housenumber quest. Are you maybe interested in making a completely new icon? I am getting close to finishing this one (as part of finishing various half-done PRs and branches), in dev version it is currently using place name icon that is not really suitable. |
There is already an icon. Perhaps or is not exported yet
Am 7. Dezember 2019 11:37:42 MEZ schrieb Mateusz Konieczny <notifications@github.com>:
…
@westnordost What you think about icon for this quest? I though about
taking "What is the name of this road" and changing background to one
use by a housenumber quest.
Are you maybe interested in making a completely new icon?
I am getting close to finishing this one (as part of finishing various
half-done PRs and branches), in dev version it is currently using place
name icon that is not really suitable.
|
Oh right - |
I am a bit frustrated by working on the interface. I started this quest basing it on I got rid of The first working version had simple text fields copied from place name quest as input, with suggestion dropdown floating in some random place in line below, what would need to be fixed. I wanted to have a nicer interface, either reusing elements from AddRoadName layout or from AddHousename layout. Sadly, it turns out that both layouts rely on I can look for a superior replacement of no longer maintained But I think that I prefer to go back to a simple text fields copied from place name quest and solve just dropdown button issue. |
I am not entirely sure I understand the problem. Why do you need a non-TextView within the How / why should the interface be any different from the add road name interface? |
I'm very interested in getting this quest up and running. I've looked at @matkoniecz |
I've not looked at it yet. Requirements are:
But anyway, you could open a PR and I will look it through. I know that @matkoniecz currently has a lot to do, so I think you would do him a favor if you / we grabbed his work and completed it. |
As everyone can see above, I've opened a WIP pull-request to work on this, and made some changes already based upon how I found it handles out surveying. In particular, I've
I still need to look into @westnordost's comments above and see how I can go with them. |
In France (but not only) we use |
Can you give example of edit where unwanted data was added? I am pretty sure that I implemented filtering out
In such cases tagging address as tags is AFAIK also perfectly fine. Or is there some area where community decided to deprecate PS Note that comments in closed issues can be easily missed, if SC is causing some issues - it is always better to create new issue rather than comment in closed one (obviously it is not applying if problem is fixed already, but not yet released) |
yes, you did: |
@HolgerJeromin thanks for the clarification. |
Top comment is what was initially proposed (I was unaware about this relation at that time). #213 (comment) is more recent and includes note about associatedStreet I will add one more note that this comments are historic and to look at current code |
NOTE: all below may refer to state of quest during implementation and may be now outdated.
implementation state: #213 (comment)
As discussed in #205 at least for some regions (for example Poland) it makes sense to have quest asking about missing addr:street.
To make quests less complicated it should not be done as part of existing "add house number" quest.
Note that it would be preferable to ask question about addr:street immediately after solving housenumber quest, so overpass query finding quests target should not be in form "addr:housenumber without add:street", but rather the same as one finding missing house numbers.
Given that this quest apparently makes sense only is some regions (where addr:street is both likely to not be obvious and available to surveyor) it is preferable to add
mentioned in #188 (comment) before adding this quest (or at least quest filter, with this one disabled by default).
The text was updated successfully, but these errors were encountered: