@Con-Hennekens Thanks, Con. I've not really used the new approach enough to judge whether it's better. But I'm about to!

@Erdna I also use "route as track" navigation a lot. The main reason is the lack of a "curviness" option with HERE, so I use TT or OSM for planning instead. My routes have 3-5 VIAs and a handful of SPs, and I let the routing engine do its job. As all these roads are typically routable with HERE as well, there's hardly any difference when it comes to navigating the route (as track). And if so, it's easily manageable - the same applies to some erratic behaviour that occurs from time to time (very rarely). It may depend on the areas you're riding, but in my case, this works very well. Have a great riding season as well!

@MotorradTeam-Mannheim, Die Favorit Punkte werden sicherlich ein interessanter Punkt in dem zukünftigen großen Web-Planer-Update sein. Aber wann das allerdings zu sehen sein wird, ist noch nicht bekannt.

TomTom a une méthode de calcul différente de celle de Garmin, de sorte que les itinéraires ne correspondent pas toujours. Les routes sinueuses et les différences en altitude sont typiques de TomTom, mais la version Gold de MRA vous permet de choisir la méthode de calcul de TomTom. Vous pouvez également comparer l'itinéraire de TomTom avec celui de Here. S'ils sont différents, vous devez déplacer stratégiquement quelques points intermédiaires jusqu'à ce que les deux itinéraires correspondent. Dans la plupart des cas, cela fonctionne, mais parfois ce n'est pas le cas ! Dans ce cas, vous devez faire preuve d'un peu d'ingéniosité pour faire correspondre les deux calculs. Il arrive qu'un itinéraire soit inexistant pour l'un des deux ou que la sens de la circulation n'ait pas encore été ajusté. Les cartographes devraient également actualiser au maximum les informations récentes.

These calculations are not done with HERE @Lex.Kloet.RX Reporting them there, will not help. @Corrado-Miniati-0 please create a support ticket: myrouteapp.com/support and indicate where the issue occurred. Ideally recreate it with a route from the Routeplanner (select OSM map, set avoid options and show the wrong road is taken).

All very clear, many thanks for the feedback

To provide another curve

I you planned een scenic route, and you pickup one ( red, green or blue ), then you use it : waypoints appears ! Romove the waypoints where you want to choose BOCHTIG or/and HOOGTES in TomTom's way of calculation. At that moment you will see more turns and heights between to points !

Oui, j'ai déjà redémarré l'ordinateur, l'écran, mise à jour de l'ordinateur, ... Il me reste à voir le câble de liaison écran / ordinateur

Bouke bedankt voor je reactie, ik denk dat dat voor nu de beste manier is.

@Guzzist Thanks for your advice. I will look further into these options shortly.

@Brian-McG, that confirms my thought, thanks for looking it up. @ginogino said in MRA - weird "detour" created: During the journey, the app gives me a voice description of the waypoint so that I can take the right road. You mean the left road? Yeah, sometimes you must be creative.

A quick and dirty solution ist to declare this part to off-road. So it is a straight line and there is no walking/driving around. RT

Kijk eens op de site van JaVaWa, das iemand die best wel wat knowhow heedt van dit soort zaken: https://www.javawa.nl/ Ik heb het idee dat jet meer te maken heeft met de combi Garmin en Mac en niet zozeer MRA.

Thank you all for the help. I often take multi day rides with numerous routes fairly close together. I still think being able to join routes where you want to rather than at just the end or the beginning would be very useful.

Probleem wordt onderzocht!

OpenStreetMap is not a map-maker, it is your task to make the map. So, thank you to the guys, who made this work for all of us. Without being paid. RT

Just tried it out. My Safari Version 18.5 (20621.2.5.11.8) and macOS 15.5 (24F74) on Retina 5K, 27", 2020 does not show this issue. RT