"Route as Track" wird nicht wie geplant navigiert
-
@Martin-Wilcke : Hey Martin,
versuche es mal mit der GuRu Maps - App, nach etwas einarbeiten kannst Du dem Track knallhart folgen bzw. die Route wählen … geht auch sehr gut mit der Remotek One zusammen zu bedienen. VG
-
@Martin-Wilcke : Hey Martin,
versuche es mal mit der GuRu Maps - App, nach etwas einarbeiten kannst Du dem Track knallhart folgen bzw. die Route wählen … geht auch sehr gut mit der Remotek One zusammen zu bedienen. VG
@Hubert-Thoring
Danke für den Tipp!Es gibt einige gute Trackplanung-Apps, hauptsächlich aus dem Bereich hiking & biking, die auch Planungen für Motorrad/Auto ermöglichen. Hier ist Locus Maps mein Favorit; unter anderem auch deshalb, weil es einen recht guten WebPlaner bietet.
MRA ist für mich eine klassische Routenplanungs-App, also eher in Konkurrenz zu Kurviger & Co.
-
I did not read the full thread and did not test anything concerning this, but want to give these tips:
- When a route that has the OSM (or TT) map set as basemap is opened in NN, it will always be opened as track, so there is no route recalculation on basis of the HERE map (but of course a track calculation is done, but distances between trackpoints cannot lead to these kind of differences).
- could it be possible when you still have the compare to HERE function active, a save from the webplanner leads to a route based on HERE instead of the basemap? Maybe that's the difference. I never saw anything like this, but I seldomly use compare functions. This might explain perhaps.
-
I did not read the full thread and did not test anything concerning this, but want to give these tips:
- When a route that has the OSM (or TT) map set as basemap is opened in NN, it will always be opened as track, so there is no route recalculation on basis of the HERE map (but of course a track calculation is done, but distances between trackpoints cannot lead to these kind of differences).
- could it be possible when you still have the compare to HERE function active, a save from the webplanner leads to a route based on HERE instead of the basemap? Maybe that's the difference. I never saw anything like this, but I seldomly use compare functions. This might explain perhaps.
Thanks for your hints!
It's not about comparing OSM and HERE or any other interaction between them; it's a pure OSM issue.
Here are three simple steps for a check:
-
open and use this route; the goal is to avoid the A7 Motorway
https://www.myrouteapp.com/en/social/route/12968571?mode=share -
turn on Toolkit > Curves > Average. The route line changes accordingly; however, if you open this route for navigation, the A7 is used anyway
-
turn off Curves > Average and set Avoid > Highway instead. This works as expected when opening for navigation
-
Thanks for your hints!
It's not about comparing OSM and HERE or any other interaction between them; it's a pure OSM issue.
Here are three simple steps for a check:
-
open and use this route; the goal is to avoid the A7 Motorway
https://www.myrouteapp.com/en/social/route/12968571?mode=share -
turn on Toolkit > Curves > Average. The route line changes accordingly; however, if you open this route for navigation, the A7 is used anyway
-
turn off Curves > Average and set Avoid > Highway instead. This works as expected when opening for navigation
@Martin-Wilcke, Yes I see what you mean... Funny thing is that when you use TomTom instead of OSM for your curvy route, things work as expected

-
-
I did not read the full thread and did not test anything concerning this, but want to give these tips:
- When a route that has the OSM (or TT) map set as basemap is opened in NN, it will always be opened as track, so there is no route recalculation on basis of the HERE map (but of course a track calculation is done, but distances between trackpoints cannot lead to these kind of differences).
- could it be possible when you still have the compare to HERE function active, a save from the webplanner leads to a route based on HERE instead of the basemap? Maybe that's the difference. I never saw anything like this, but I seldomly use compare functions. This might explain perhaps.
@Con-Hennekens said in "Route as Track" wird nicht wie geplant navigiert:
When a route that has the OSM (or TT) map set as basemap is opened in NN, it will always be opened as track, so there is no route recalculation on basis of the HERE map
There IS a route calculated with HERE based on and on top of the OSM route. It's one of the features I love about MRA: You can navigate an OSM and a HERE route at the same time and always choose which one to follow. Super handy if you want to navigate routes and tracks that aren't in HERE.
Here is another example, have a look at the white and blue lines:
https://www.myrouteapp.com/en/social/route/12990957?mode=share
