@Mark-Davies-0 I’m a CoPilot user as well and I think, CoPilot should use the most common GPX data format instead of her own and rarely used .trp format.

@Guzzist Thank you for clarifying that, Your comment interested me so I looked it up a little more on wikipedia and found this: ". While driving at higher speeds is not punishable, the increased risk induced by higher speeds (erhöhte Betriebsgefahr) may result in partial liability for damages. Moreover, the law forbids travel at speeds that would extend the vehicle's minimum halting distance beyond the driver's line of sight (Sicherheitsabstand).[16] On all German roads, there are speed limits for trucks, buses, cars towing trailers, and small motorised vehicles (Mopeds, etc.)." Someone also told me that German insurers start holding you liable at speeds over 160 km/h. I'm not sure how accurate that is. Regardless, I might think twice now about going over 200.

@Guzzist Thank you for your suggestion, will add it to the suggestion list. From a design perspective I have to say though that I really dislike how steep and complex the basecamp data looks. While I will directly agree that it'd be important for people who like such complexity to be able to view this, I will most certainly try to improve the visual presentation of this. Especially in an app it's important to view things as efficiently as possible. Perhaps a solution would be to be able to download or open a data-pdf for a more in depth look. Your general point: lunch pauses should not be included in total duraction and averages, is of course correct.

@Ian-Syphas Hi Ian, of course I don't know the specific device you have, but I can give a general explanation that could explain this. on many satnavs calculations are still done on-board using locally available sat-nav data. Online services such as MRA Navigation, Waze, Google etc. all use live updated traffic data. The frequency of data updates plays a large role in the difference in travel time. For example, if the computer uses "guesswork" based on average delays etc. you could get a wholly different outcome than with a computer that uses live information. In general, the latest estimate from online services is the most accurate. As @Nick-Carthew pointed out, your satnav will update accordingly while en-route.

@Kevin-Russell said in Moving waypoints: ... just reverse the whole route? As Gold-Member, you may open a route, select "toolkit" in menue and then select "Google maps", or "HERE maps". Then open menue again, select "toolkit" and then "reverse". Result is a down to top arder of waypoints. Good Idea, to copy at first your original route and do the change in the copy. After doing reverse action, check exact position of WP by zooming in. If route is at multi track street (Highway), may move WP to correct side of tracks. At least, compare distance of original with reverse route.

@Timo-Martosatiman-MRA thanks for the answer, now I know at least the background.

@Mr-Mark-Melbourne Hi Mark, with a MRA Gold Lifetime subscription you get permanent access to all premium features on the MRA Routeplanner. As Nick indicated, I'm unaware of it currently publicly being on offer. As for MRA Navigation, we simply can't offer a lifetime offer on this product anymore because of the way the licences for mapping and navigation SDK's are contracted. Using our inhouse knowledge to re-develop such features at this time would be a deviation from our core development task (MRA Routeplanner, where in a must-do scenario many features could be ported over to open source or low cost licences), we also have significantly less knowledge currently inhouse for such tasks. While I understand that this might certainly not convince you to switch to a monthly/yearly subscription, I hope my explanation has at least provided some understanding as to why things are this way. In addition to this, the All-in-One package contains all current and future MRA products (such as MRA Video) and as such has to be subscription-based by its very nature. Kind regards, Timo

Hi Petri, What exactly do you mean by "drive through and non drive through"?

@Nick-Carthew thank you for the hint, I know about. But is not the solution, I'm looking for Verry often, I leave my planned route for a short side trip, then let my Navi find the way back to main route. In this case, route on paper is not helpful.

@Drabslab, @Michel-van-Hagen-MRA-Founder I fully agree with you And I know verry well, a Company needs to earn money. Also it's not an easy job, to balance, price and features of a product. By the way, I believe the prices for MRA product are not expensive Another tip: an official roadmap with detailed next features or fixes will be highly appreciated. No matter, if sort of sequence will change from time to time (agile aproach). If there will be a possibility, I will be happy to support developers (for free) because I believe on MRA. Kind regards Rainer

That is completely correct @Nick-Carthew

@Nick-Carthew-RouteXpert @Nick-Carthew-RouteXpert said in poi: @cliff-cockle Problem solved. Thankyou regards cliff

@MTC-TET-Club Hallo Erik, voor zover ik weet staat deze niet op de planning, maar ik zal eens navragen of uitnodigingen die niet geaccepteerd worden, automatisch verwijderd kunnen worden.

@MTC-TET-Club Hallo Erik, nee nog niet, alle capaciteit wordt in MRA video gestoken, zodat deze gelanceerd kan worden.

@Reinhard-32 danke

@Nick-Carthew-RouteXpert Thanks for the reply. I guess my take from what you've just said is that it is the Route Navigation algorithms which make up the journey time in the Itinerary, not the Myroute app and thus it would be difficult to implement I get that. I would dispute the too many variables to be useful comment. Bear in mind that I'm not talking about dynamic timings whilst riding most Nav apps are pretty good at ETA's and you learn with experience I'm talking about what is, for me at least, one of the primary differentiators of MRA. Ease of Route Planning for use on a variety of devices. Its the easiest to use and most versatile route creation tool I've found, by a country mile. I would argue that for route planning and producing an itinerary these variables, think Fuel stops, Photo Opportunities, Cafes, Restaurants, Museums Etc take up a significant part of the day, especially with a large group or a "sightseeing" type of trip. Route planning without taking these variables into account only produces a useless itinerary!. The current process is iterative - create a rough route and planed stops. Manually allow for the variables above, realise that the planned stops don't work together. Modify the route and/or or stops, recalculate. Repeat until we have a route that arrives at museums when they are open, and planned food breaks and final destination at about the "right" time. If MRA used the journey time data from the nav app but enabled users to allow for these waypoint variables to produce a detailed Itinerary with modified timings when creating the route, it would significantly simplify this process, and produce a reasonable itinerary first time every time. I would consider that to be useful to me and presumably others too.

@Nick-Carthew-RouteXpert Thanks Nick, Just seems that HereMap does some odd routing choices as opposed to Google Maps. If the offer of route planning on Google Maps is made on the mapping choice its a shame it doesnt transfer onto mobile devices. Thanks again