Osmand does exit at the right point. -> nope, you have to "pre-exit" at the junction point

it is still possible in reality to change vehicle to the rightmost lane to take the exit. -> nope, that is illegal and dangerous. Full line is a barrier to respect.

There is nothing wrong mapping this way. In some states (NL or DK i think) people map individual lanes. There is nothing wrong mapping also for logic, not only look, map is also used for navigation.

GPS is not precise enough to distinguish in which lane you are currently driving (especially at 130kph) -> lane yes, the exit point will be missed . You have to exit first to the side lane and then exit. The exit point is marked with junction point.

Hi. Now it is more correct. The full line creates a separate barrier for the whole junction. So technically this junction is equivalent to the junction with barriers.
Old design would also not work for most navigations (osmand, organic maps, osrm, valhalla, ...)
For example just the 1st exit would be incorrectly at node/12919238473 :
https://osmand.net/map/navigate/?start=48.588414,18.902358&end=48.590667,18.895074&profile=car#18/48.58935/18.89884

even worse when exiting south.
The links north and south are logically only connected ot the side lanes(links), and not to the main road.

Hello?

ok we fixed it. plz be more careful next time ;)

I've changed the link to highway, should solve nav. issues.
Please consider also the map logic before changing tags/geometry ;)

Hi. This is a split ↖↗.
So either we add turn lanes or change both highways to highway or slink. Otherwise the righ split will be interpreted as exit and the left part as abolutely nothing.

;)

Zdravim. Toto je co za divoky changeset?

node/2802996387

node/2430303154

node/2685257493

Nedava to absolutne zmysel.

note/4733659

Tracked here

Wtf man? You removed the whole block of buildings.

Dunno what data consumer want to do with it. They have to use unicode anyway and if they want to process the text only, they have to filter the text in advance anyway (e.g. removing slashes, backslashes, triple dots, en/em-dashes ...)

yeah.
BTW i've already changed it ;)

For the turns: the slight right turn was missing completely, and the indicated straight, which is slight left (in real view) worked somehow wrongly. It can be re-corrected to the indicated direction as I think it was the right turn working incorrectly ....

This is the (pretty crappy) way osm maps lanes. "lanes" counts for lanes where a 2-tracked vehicles (cars, buses, ...).
For me it looks correct now, see:
osm.wiki/Lanes

"""
Pay attention to the value of the lanes=* key. The number of lanes is referred to the lanes available to the traffic using the main highway=* key, in this example and also by definition of lanes=* key motorized traffic, what excludes bicycle lanes.
"""

Hi. I mark the directions for bicycle with bike 🚲 symbol. This is useful on mixed guideposts (bikes+hiking). Also for bike route numbers, like "🚲45" (bike route 45)

No skor to vyzera ako normalny rodinny dom

Hi again. As indicated on destination=*#Value

it is much preferable to use the actual destination "as somebody (including navigation) would speak to you"

"St." can be read as "street", "sankt", "saint", "es tee" ... you name it. Destination in this case "Sankt Gallen" whi is the ... actual destination. What is written on the sign or on map of the official city is "St. Gallen". Similarly another example would be "Bruck a/d L." or "Bruck a/d Leitha" or "Br, a.d. Leitha" means "Bruck an der Leitha" as destination

Oh, hi. Looks like forgotten over xmas :|