> The tagging scheme we used is not for rendering purposes, but for a better representation of the movement of vehicles on the roads.

This phrase has "rendering" in the title as it is the most common issue, but applies also to all other intentional misrepresenting data to achieve better effects for a specific data consumer.

It would cover also mapping fake separate carriageways.

> The problem with the actual wiki is that the merging angle is at the discretion of the user editing the data. My method is systematic and always works, and also follow the real movement of the vehicles using the merging: just start the merging as soon as the continuous lane changes to dashed line and connect it as soon as the dashed line finishes.

yes, existing method has a bit of subjectivity and is not ideal for your desired use of OSM data

but it is more or less standard (though it is not rigidly followed in some cases, which do not apply here)

Though your method has the same "not always the same angle" problem and has fundamental issue of redefining widely used method.

OSM tagging has many silly parts, but unilaterally redefining how things are done and expecting others that they will be obedient is not helpful at all

next fixing lanes incorrectly mapped as a separate carriageways in this area is in changeset/120498153

I have not checked other nearby junctions whether data is broken also there

to be more specific it removes invalid data which mapped lane as a separate carriageway

are there any similarly broken junctions? how widely this editing was applied?

@ChaireMobiliteKaligrafy Has anyone ordered you to make this edits or paid for them? If yes, note osm.wiki/Organised_Editing_Guidelines

data partially unbroken in changeset/120497870

> See this image: https://ibb.co/bJGdFpX, can you tell me which white line (which angle) would be suitable for the merging here?
> See this image instead: https://ibb.co/VYwzs6c

two rightside one are clearly invalid and it breaks geometry

mapping presented on that image is also wrong and as explained by you is a case of blatant tagging for renderer

> for better representation for autonomous vehicles and routing

introducing incorrect data to aid specific data consumer is not acceptable and should be reverted, see osm.wiki/w/index.php?title=Incorrect_tagging_for_the_renderer

jak dasz radę to popraw!

Ja nie zrobię edycji, bo nie jestem w stanie zweryfikować tego

utwirzyłem na razie note/3162531 (do zakmnięcia po edycji) by o tym pamiętać

Czyli park też jest tak naprawdę mniejszy niż zaznaczony obszar?

which specific source was used here?

Please mention specific sources rather than linking list of all possible sources

which specific source was used here?

Please mention specific sources rather than linking list of all possible sources

which specific source was used here?

Please mention specific sources rather than linking list of all possible sources

which specific source was used here?

Please mention specific sources rather than linking list of all possible sources

which specific source was used here?

Please mention specific sources rather than linking list of all possible sources

@PopeyePopcord what was your source for this edit?

Uzasadnienie podane w opisie edycji jest wadliwe.

Klasyfikacja w OSM nie jest kopiowaniem klasyfikacji urzędniczej czy stanu drogi.

Hej, jedna poprawka: nazwy szlaku nie dajemy na drogach/ścieżkach które się na niego składają.

Are you sure that Concrete Oak is name of this tree?

See note/3156047

Zerkniesz na note/3149362 ?

Czy to rzeczywiście publicznie dostępna droga dla samochodów