search

organicmaps / organicmaps

πŸƒ Organic Maps is a free Android & iOS offline maps app for travelers, tourists, hikers, and cyclists. It uses crowd-sourced OpenStreetMap data and is developed with love by MapsWithMe (MapsMe) founders and our community. No ads, no tracking, no data collection, no crapware. Please donate to support the development!
https://organicmaps.app
Apache License 2.0
9.48k stars 913 forks source link

addr2:street / addr2:housenumber support #771

Open neonxp opened 3 years ago

neonxp commented 3 years ago

Hi, guys! What is the situation with the dual addressing of corner houses in OM? As I understand it, there is no clear consensus in the OSM community on how to properly support it. But there is one option using the addr2:street / addr2:housenumber tags. It doesn't look like a great solution, but it's IMHO the best of the worst. And It would be great to see support in OM. In particular, in the search, on the object card and on the map itself in the form of a house numbers like "81/23" for case https://www.openstreetmap.org/way/71169981 fyi: https://wiki.openstreetmap.org/wiki/RU:Addresses#.D0.A3.D0.B3.D0.BB.D0.BE.D0.B2.D1.8B.D0.B5_.D0.B4.D0.BE.D0.BC.D0.B0

biodranik commented 3 years ago

@Zverik what do you think?

Zverik commented 3 years ago

addr2:street is not supported by any other software. addr:street2 is also very rare to be supported, although I think maps.me / organicmaps does support it. The correct way at multiple addressing is simply to create another addressed node inside a building.

upd: nope, addr:street2 is not supported by maps.me as well.

neonxp commented 3 years ago

Yes, I agree that tags are not supported by other software. At the moment, there is only a proposal: https://wiki.openstreetmap.org/wiki/RU:Proposed_features/AddrN.

The problem with the node inside a building is that it displays ugly (the red area in the screenshot). And, I'm sure, there are side effects associated with the fact that the polygon has its own address and it may not know about the existence of its other address on the node. Although logically both addresses are equal.

May be good way is display a double address through a slash (as in the green zone of the screenshot), if there is a node with an address in the polygon? And also have both addresses on the card?

IMG_8177

biodranik commented 3 years ago

Some addresses in Russia, for example, are using slashes, so it's a bad idea. Need to think about something better (use parentheses?)

natrius commented 3 years ago

Slashes are a bad idea. As far as i'm aware a lot of houses in austria do have two adresses on corners and we opted to just drop 2 adress nodes there because its easier for everyone. See this building https://www.openstreetmap.org/way/155053493 for example.

neonxp commented 3 years ago

Slash IMHO using often on double numbering of the corner houses. As on screenshot:

Π‘Π½ΠΈΠΌΠΎΠΊ экрана 2021-07-01 Π² 16 03 25

And I thought that it is good idea to display this house (and all like them) with slash like on address plate.

It seems that any solution will be good in which the house numbers will be neatly displayed next to each other and not at random points of the polygon. And if all the addresses are displayed in the house card and in the search.

RedAuburn commented 4 months ago

closing as not planned, it's standard practice that different addresses are mapped with either a node or internal area

biodranik commented 4 months ago

Closing it does not solve a proper address display when selecting a building or some feature inside this building.

In any way, our generator should detect that a building has two different addresses and properly process them, or even extract addr2: fields too, to provide better UX for end-users.