* node/725431583

Here you created a turn on the road that was not there before? Under influence again?

* way/1458193336

Here you createad a left then right turn N-S direction. Intentional routing sabotage?

Hello
* Your change description does not make any sense nor helps anything to explain

Hi. So how on earth have you determined a new position of a single point node/11375996927 while changing some random "Some details on and near A1, CH" of a size of a state?

these 2 ways:
way/587643501
way/587643501

Hey, excellent job with that crossroad! It is rare to see somebody simplify a crossroad (until some smartass re-complicates it back...). I usually see the opposite which creates navigation hell.

Hi. There is no 140kmh here (node/6105470021)
Only end of limits, 2026-05-14

Also if you want to start some kind of edit wars, better discuss it first, otherwise if is a map+others work sabotage. All zoos in the world are mapped with attraction.

You could in same way start removing attractions from attraction (trill park)?
When I go an attraction park, I am looking for attractions, period.
You should distinguish enclosures (e.g. for usual animal keeping, quarantine ...) and attractions (like here) anyway. It is logical.
Also that you found one sentence in a text doesn't mean it is a holy Bibble. That is radicalism.
There are many more tags that are used slightly differently (like 'destination') that are used in a way that is more logical, because it works better.

add more, is same as in Murten ;) : changeset/181858488

hey, nice catch, thanks ;)

Hi.
Why did yo ufusion these 2 ways again?

way/587643501

way/1263640788

They were laboriously separated to represent what they should, and now they are again touching? Any reason?

They are same (aerial + panoramax). I went thru once also last weekend.
Turn lanes are OK: first two are left, next two are for straight. If you mean the markings, we can add lane marking tag too (turn lanes and lane markings are not the same stuff)

hi. Checking ...

Example foot:
osm.org/directions?engine=graphhopper_foot&route=46.786588%2C7.083585%3B46.785934%2C7.080104#map=19/46.785944/7.080574

bicycle broken too.

Hi.
WTH?
What is the point of your change? It was mapped and worked correctly already.
You broke the routing completely BTW.

PS: just for clarification: One should expect a keep-left / keep-right routing when goinf N->SW or N->SE, at that point. Which is what you physically see when there.

Change here:
changeset/177638131

will test that in few days when routers are updated ...
This creates an equal split at the cplit point node/13381120019

PS: there is no perfect solution for everything. I go for a kind of compromise between look and routing.

Hi. Sorry for late reply, I was a bit off after holiday :D

Nope, that 1st router is not working correctly neither (try the from N to SW or SE routes). Also like mostly none of the routes working right now.
There is nothing wrong arranging roads a bit to make more sense to computers. Especially you have to avoid phantom turns (i.e. create geometric turns where they are not) especially at crossroads with different types of roads.
Or, what I see most often, a major/minor road split when optically (like here) they seem to be same -> the less major road is treated as an exit (which is 50% a legitimate interpretation). The fix is to have temporarily same level of roads at the intersection ...

I'll try another simple fix.