@Marinus-van-Deudekom That helps, thank you

@Eric-de-Swart said in Strange Route Issue:

@Angelo-Greco I have kind of the same. I can't get the route to go over the ferry between point 71 and 72.
I made the route by using the scenic route tool, to create a route, afterwards I made some changes.
Originally the route went over the ferry, but as I adjusted it (edit route, and ad waypoints) there's no way to get it over the ferry.

Position route point 71 at the ferry. Your eyes will tell you that you are about to take the ferry. When you pass route point 72, all will be good again.

@Cor-Theissling, jij navigeert met de app? Zet dan de kaart op Here in de routes die je plant. Dan verdwijnt dit probleem.

Hi, die Navi App reagiert anders auf plötzliche Sperrungen als die Web Planung.
Teilweise muss man die Verkehrsfunktion einschalten, um Sperrungen zu sehen.

@Corjan-Meijerink fast fix - thats almost at the speed of light 😂 👏

@Nick-Carthew thanks i will do!

@Cor-Theissling Even in een card-holder in de pc/laptop stoppen en een formatopdracht geven.

@Serge-4

Check the whole route and increase the via points to max 29

@Jörgen said in My choice is not taken!:

Traffic „on“ will not be stored as default, just the map that is used for route calculation. 🤷🏻‍♂️

With that I can live, but please do not force the Logistic map to be displayed (or any other). The user should know best, which map is best for him, so please waive the dependency between any vehicle type and specific map overlays!

HERE should just skip all ferry time schedules for inland ferries, and add a 10 minute duration time or even set it to zero. For preventing navigation over ferries there already are features available.

@Rob-Verhoeff Thanks Rob. That seems to have done the trick 🙂

@Tam-0 enjoy the ride and have fun

@Barb-Miller

I think I understand what you are asking:

MRA planner on website has an option for waypoints that is a "4x4 car". This option draws a straight line from this point to previous one. This is useful for offroad tracks or others than Mra map in use does not knows nothing about.

aac21a49-525a-4163-88d6-8f0f0e751437-image.png

In this route, point 4 has a straight line, because I know a secret track to use, but MRA not 🙂

This only works on planner, nor in Next.

Is this what you mean?

@Montorsi-Paolo-0 Could be it's simply not supported on Edge 😞

@Robert-Smith-2 I've had the same problem thuis week with my Windows laptop. When I reniewed the browser the problem was fixed.
I guess it had to do with the combination of server and my internet connection
Hope it's solved at your end. Sometimes machines just don't di what we want them to do

@Neil-Bartlett, I have seen the scrambling of waypoints often, I suspect especially Basecamp exports suffer from this, but I don't use that anymore so I cannot say for certain. MRA imports these WP's in the order they appear in the file. Some software seems to export them in a numbered order not following the same logic as MRA uses. WP10 can appear before WP2 in the ordering in the file. Usually it can easily be re-ordered using the left column.

Then there is the very common problem where the created route does not completely comply to the track. That is quite logical, because who knows what routing logic was used to create the track, and on which map it has been done. Did they use shortest or quickest, avoid toll roads, maye even traffic info interfered with the course of the track... You will have to add waypoints to make the route compliant to the track.

Usually I import both the track and the route. I then take a look at the waypoint info, to see if there is any sensible info in them. If they are just placed waypoints with no further extra info, I delete them all and start drawing my own route using self-placed waypoints.

@Nick-Carthew Gelukt. Dank u wel !

@King-06 menus changed indeed, but still very workable. Great topic find, this worked for me. 👏 👍

@Con-Hennekens Staat op Nederlands. Toch bedankt voor de tip!

Vielen Dank für eure Tipps und Info, mal sehen wie und ob ich das hinbekomme...😬

Frank