As a new user, I encountered a routing issue on my first planned route.
The app avoids routing through the Eurasia Tunnel (Avrasya Tüneli) in Istanbul, Turkey even when the tunnel itself is explicitly selected as a waypoint. I’ve included a sample route link below where this happens:
Despite selecting the tunnel as a waypoint, the route is automatically recalculated to avoid it.
I suspect this may be caused by outdated map data or motorcycle access restrictions that were not updated after the tunnel reopened to motorcycles in 2022.
I hope this issue can be resolved before my 7-day trial expires, as I would very much like to become a full user and continue using the app. I’ll be following any updates on this.
I think @boldtrn or someone from the Kurviger team would need to have a look at this. There are lot of tags in the tunnel - I am not sure which one is the algorithm avoiding.
Motorcycles appear to be allowed.
Meanwhile, you could use one or more beelines to “tunnel” through the tunnel : https://kurv.gr/qFfd4
You are right - the tunnel was opened for motorcycles in 2022:
But there have been 6 roads leading from / to the tunnel still tagged with “motorcycle=no”. so lets try to fix that - perhaps we can do that without help of the Kurviger experts .
I changed the tagging, searching with overpass turbo there seem to be no further blocking items:
Usually it takes a few days until Kurviger router will update the changes of OSM tagging - but you can check that also after your free trial expired, because you do not need any subscription for route planning on website (to check just click on your route link above in any browser without logging into your account).
If you are interested in, you can do such changes of OSM tagging yourself also - Kurviger usually updates the changes of OSM tagging automatically within a few days.
Thanks a lot for taking the time to investigate and fix the OSM data
When I opened a new OSM account and checked OSM, the motorcycle=no tags had already been removed thanks to your edits. I only added motorcycle=yes on the related access roads as a small precaution.
Also thanks to @t00thl355 for pointing the topic into the right direction.
If Kurviger regularly refreshes its OSM data, this should sort itself out within the next few days. I’ll be waiting.
I wasn’t aware before that OSM edits were this accessible, good learning experience on my side as well.
Thanks again to both of you for the effort and quick support
Kurviger is continuously refreshing OSM data, the transfer takes 2-3 days - there is a timestamp at the bottom of the settings menu, which tells you when was the last transfer.
Please do not! As you can see on several roads I removed those obsolete tags before yesterday.
Several highway types have default setting, I linked them yesterday in my change comments:
You should not set this tags additionally, because that reduces clarity, consumes memory unnecessarily, might decrease speed of routing and in worst case cause problems.
I recommend to do some trainings (probably they have been recommended to you when creating an OSM account), also reading OSM documentation about basics is very helpful.
Die verwenden unterschiedliche Routing-Algorithmen und werten unterschiedliche Tags aus.
Es wäre praktisch, wenn man mit einem Shaping-Point das Routing erzwingen könnte, indem der Router die Tags ignoriert und einfach die Wege folgt. Das würde auch die Offroad-Navigation etwas vereinfachen. Anstatt das Routing zu verweigern, könnte Kurviger dann ensprechende Warnungen ausgeben, warum die Route möglicherweise nicht abgefahren werden kann. Dann kann sich jeder überlegen, ob die Warnung stimmt oder nicht. Wer die Warnungen ignoriert und später vor dem Verbotsschild steht - selber schuld.
Das Problem sind ja scheinbar Motorradverbote, wenn OsmAnd das Routing für Autos bewertet, dann ist das schon richtig so, ist eben was anderes.
Das ist leider nicht so einfach und auch gar nicht unbedingt immer gewünscht. Beispiel: Fahrradweg neben der Straße, Wegpunkt liegt auf dem Fahrradweg (weil, grob gesetzt), Kurviger würde dann den Fahrradweg nutzen, da erzwungen. Das Problem ist bei Routenberechnung (nicht nur bei uns) geht das technisch nicht anders.
Genau. Aber da kämen entsprechende Warnungen ins Spiel, die dem Nutzer solche Stellen aufzeigen (Warnungen für andere Sachen gibt es bereit). Die Funktion “WPs auf Straße setzen” würde sie alle automatisch korrigieren können. Ja, ja… ich weiß - technisch gar nicht so einfach. Ich werfe gern ein paar Ideen mehr ein und schaue was davon Resonanz findet.
: 