@Con-Hennekens if I would have great secrets in it, I wouldn't have posted it, so "go your gang"

@Hubert-Thoring Über die App kann ich den folgenden Bildschirm aufrufen, der mich zum Routelab-Supportbereich führt. Aber dann müssen Sie eine Reihe unlogischer Aktionen ausführen. Das ist auf jeden Fall verbesserungswürdig. [image: 1710848173015-img_1995.jpeg] Wenn Sie von der App aus zu Routelab gehen, wählen Sie logischerweise unten rechts auf dem Bildschirm die Option <Hilfe benötigen>. Aber dann kommst du nicht zum Support. Wählen Sie die Lupe oben rechts auf dem Bildschirm aus und gehen Sie im nächsten Bildschirm zu <Benötigen Sie Hilfe>. Dort erhalten Sie die Auswahl <Support besuchen>.

Deze staat heel hoog op de takenlijst voor de website! Nu de 4.1.0 update uit is gaan we kijken welke taken voor de routeplanner worden opgepakt, dit is een zeer waarschijnlijke maar daar later meer over

@Hans-van-de-Ven-MRA-Master check!! Werkt. Ook op de telefoon.

@Richard-18 I understand your point, but sometimes it is really handy to have this custom avoidances thing in place. Depending on where you are riding, you might have more or lesse long term roodworks or road closures and deviation on very small routes where you don't get the information about them from any other source then your personal exprience. Riding a lot on ver small roads, I normally have no chance that a closure of one of these small roads is incorporated with some general traffic information, which normally knows about road closures. Here it is really handy to define a custom "no-go area" for your trips.

@Bud-0 Forgive me, I thought you were using the free basic account. The animation bar is fixed. It may receive an update to include a distance read-out or some other reincarnation after the planned overhaul of the route planner or it may get removed.

@Edwin_M the problem is not so much in the map material, but the differences in settings on your navigation device. I made an example of approximately 130km with a total of 4 points and used the segment calculation in OSM. Then had it recalculated in HERE map (copy route in MRA, change map, change agreed, intermediate points discarded and new intermediate points added) and I had to use 8 more points. It has an average of 1 point per 13 km. I think that's a bit too little anyway, but this route is OK in my Garmin (XT and 220). Even if you could create the winding route on a HERE map, your device will still choke on the task, because it does not know that algorithm and will calculate the fastest route from point to point. So, you just need the minimal support of multiple intermediate points.

@RetiredWingMan said in Timeline for snapshots of edits: sounds very complex Indeed. The Art is to make complex things simple @Corjan-Meijerink said in Timeline for snapshots of edits: Personally love the idea. I also know that this will be quite complex to make it intuitive. Thanks. I thought you were gonna say the programming is complex instead of the intitivity, so I guess that's a win already Maye, to make it less complex for the user, it can be limited to just one snapshot. Then it is more or less equal to the "Oopsy" button, but then to return to a previously defined stage in the planning. @Jörgen said in Timeline for snapshots of edits: Is this a kind of version of a route you want to organize? More something like "I want to go to Winterberg, but I don't know yet if I will go north or south to avoid das Ruhrgebiet". You can plot both, and decide later. @Jörgen said in Timeline for snapshots of edits: By the way, is it a coincidence that you have exactly my home area in the detail? Your and mine home area are not that far apart (Roermond area) No I just opened a random route to draw the mock-up on.

@Corrado-Miniati-0, I never use that function, but I agree it should NOT delete VIA points at all. They are VIA points for a reason.

@Jack-van-Tilburg Ja, dank je Jack. Ik weet dat ik in de linker kolom kan toevoegen. Maar zoals vermeld, ik zou de locatiezoeker ook willen gebruiken om te weten waar de plaats ligt. Dan beslis ik zelf hoe verder.

@Peter-Smits-0 Dat is per browser anders. Om dat te vinden moet je zoeken naar instellingen zoomniveau. Google is your friend

@Nomko-Nomden Ik was al klaar met de route en had de route gecorrigeerd in mydrive. Ik was wel benieuwd waarom ik soms een weg zonder verspering niet kon volgen. Inmiddels weet ik hoe ik er om heen kan werken. Bedankt in iedergeval!

@Robert-Jeffries, I like your suggestion on adding POI but I would also like the option to make all waypoints be Via points by default. Why would you want to do this? If you don't like auto-skipping just disable that in settings if you want all WPs to be announced just enable that in settings What is so special about VIA points that you would all WPs to be viapoints?

@Rob-Draaisma-0 [image: 1709101789168-giphy.gif]

@Jack-van-Tilburg said in The web planner needs some love & development?: Make a plan and stick to the plan. YES I think we all mean more or less the same... with different words @Peter-3b said in The web planner needs some love & development?: We need to support a variety of devices, tools & apps and better GPX support is the way to do that. which are all part of the eco system in my book

@Martin-Wilcke Thanks for the further info. Please feel free to share any Apps you use. I can see you are using QuoVadis X Standard, i'll check that out.

@Oliver-a : Ich mache es auch so, und teste das ganze immer mal zwischendurch. Aber eigentlich navigiere ich lieber mit der MRA-Navigation App … im BMW Cradel. Was fehlt, ist die finale Lösung Handrad = Multicontroler von MRA und dieses mit Carpe-iter BMW Connect HUB und das in meinem Fall für iOS , Carpe-iter arbeitet zurzeit noch dran, danach kann das MRA Team daran weiter arbeiten. [image: 1708414743423-img_0633.jpg]