Hi Guy, As for your first suggestion it's already in the works. We too want to have beautiful height-profiles in our routes! Stay tuned, it'll be one of the closer updates. As for the second suggestion I'll add it to the list. However, it'll be off in the future as we're currently having a vote for the future features of MyRoute-app. This is based on initiatives by the MRA team but also by the MRA community. Kind regards, Timo

Thanks for the info. As i saw, i have to set it explicitly every time a start the navigation of a route. It would be nice to have a global setting for that, or MyRouteApp switches automatically when a route is started.

Hi @Craig-4. It will tell you to turn around or you can select to skip that route point and any others that you may have missed.

Hi Craig, This depends on the payment provider you chose, but in general, yes, most subscriptions automatically renew. Kind regards, Timo

@Craig-4 Not claiming that this is the best way, but this is how I do it: Route end point: I put mly end points on the road fairly close to my destination (read: hotel). This way I am sure that routing will have stopped when I arrive which avoids a few annoying things with my GPS. Route starting point: never at the hotel because then the GPS may miss it and keeps sednign you back. Very often, I put my route starting point on the first main road outside the city where I stay. That may be several kilometers away from the hotel. This way I can give my GPS the freedom to calculate the optimal route to get out of the city and pick up my route when the odds of having a roadblock are minimal. Your second problem. Your GPS may be doing the correct thing. It is calculating the most efficient way to go to nearest point, and in many cases this does mean turning around.

@Craig-4 That’s still possible. Use the Here map as the base map to plan on and switch on the Google overlay map.

Nice idea! I've added it to the suggestions.

@Emile-3 Any questions - just ask

@Cambell-Evans Now I have new/more information. You may do it with your Garmin device to compare. I created a route on PC with MRA. Then I exported that Route by USB connection as GPX 1.1 to my Garmin396. Result: route in Garmin396 has only "shaping points". If I start navigation, ther is only a starting and an end point. Navi shows me only distance and time to target (end) point. If I exported the same MRA route by USB connection as GPX 1.0 to my Garmin396. Result: route in Garmin396 has real way points. If I start navigation, there are all way points and Navi shows me distance and time to next waypoint as well as distance and time to target (end) point.

@Michelotti-Maurizio Also a nice one on the great suggestion list

@Stephen-l-Weber i was just about to ask the same question in here. I read the notification but didnt really understand the impact. now i know...

You can of course us 1.0 which gives you waypoints, then once the route is in the Nav, you can change waypoints to shaping points or visa versa from within the Nav.

@Nick-Carthew avoid un^paved roads is all ways marked. But I put in fact a waypoint on a un-paved road. So TTR told me (d d is also to avoid un-paved roads) by the start I would come to a un-paved road, I ignored the message and had to ride the un-paved road. Never mind, is here in switzerland no hassel.

@Jeffrey-Kogler Thank you for that compliment and thank you for explaining the ways that MRA is currently already beneficial to you. I'm happy to see that you think the routeplanner offers a smooth and simple experience (as the UI designer, this is of course the best compliment I can get).

@Gary-France Hi Gary, thank you for the feedback, I keep the following rule: 1 1/2 hour, maximum 2 hours drive and then a stop for coffee, lunch etc. For each stop I also add a POI to the route, not as a route point, but as a POI. These are then shown in the Garmin Zumos as "Green Heart". I also use the track as the basis for my routes, I have the Zumo calculate the route based on the track and I then make the track visible in my Zumo as a "white line". For very long journeys, I cut the route in stages, the points where we stop for coffee, lunch are then the end point of one stage and the starting point of the next stage. Then you also have the end time visible in your Zumo when you reach the end point. But if you make a choice, you should use what works best for you. I made everything in Basecamp and MRA for 1 season, and my choice was quickly made after that year. No more Basecamp for me.

I'm wondering because in MRA Navigation App there is in settings menue a selectable option, to set WP automatically on a street. But in MRA, I'm missing this option!

@Guzzist said in Favorites en point of interest: @Drabslab I like your suggestion, but currently, I still prefer a "real" sat nav device. Smartphone is today still not 100% equivalent. In consequence, Waypoints, Favorites and POIs of MRA should be most as possible able to correspond with other sat nav devices. @Guzzist Me too, i would nto dream of using a smartphone on a motorcycle, I have a TomTom rider 400. But that does not prevent upgrading the web interface of MRA, and ensuring that "my" MRA points of interest can be used as waypoints in a route, or are downloaded to my satnav as points of destination

@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.