The problem is currently discussed here:

https://github.com/osmandapp/OsmAnd/issues/22964

Looking at the history, this crossroad was already correctly (from the logical / navigational perspective) mapped 2 times and 2 times broken again.

OMG man, it was already correct, with splits AFTER the crossroad. Now the splits are part of the turns and all navigations are broken.

I'd highly suggest to 1) recreate the proper turn angle or 2) revert this change

Hi. Sry for wait time, i have work ...

What?
The emergency vehicles do not use/need any map, they can drive according to the situation, even in opposite ways.

"You are not mapping for logic, but for look. " thay is wrong, I have mapped that for logic. You can fix the map or you can fix all the navigators/routers out there to support lanes navigation ...

"may give you wrong instructions" - wrong instruction would be to exit at the ramp point(s there are 2). You should start exiting sooner before it still possible.

Also the lane mapping example on wiki (Motorway_with_lanes_and_destinations) has a problem for higway exit - the junction is mappet at the split point and also shall be mapped before the last possible exit point which is before the full line. Consequently this cannot be used on higway exit.
Example: osm.org/node/2836078
The junction is placed before the full line. With your logic it would be misplaced on osm.org/node/2977985210 (150m too late, that's about 5 seconds)

For the turn lanes: the explicit right turn is here for navigation in case somebody gets overexcited and straightens the turn that is is no longer a turn.
none;right or through;right should mean the same

Hi. Seriously what is wrong? You can map without problem a forest over scrub/grass/farmland, scrub over grass. It is a scrub that grows on grass, etc... We do that over years, it is perfectly correct.
Using multipoly in these trivial cases is overcomplicated.

:D
a to parkovisko vpravo zmizlo?

Servus. Toto je co za nezmysel?

nice ;)

Servus. Nieco zle na predchadzajucom changesete?

Hi, isn't the 'destination' rather for the next way?
osm.org/way/25279491

Hi all.
A note: mapy.cz renders lots of things badly (e.g. bridge areas, guideposts...). I'd consider it as a bug in mapy.cz. See the discussion in the note:

osm.org/note/4091245

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 osm.org/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.

;)