@Timo-Martosatiman-MRA It seems a little ‘opportunistic’ of you to interpret my comments on the ‘new look’ as favouring it over the current UI! All I’ve seen of the former are the images above - hardly a fair comparison. And doubly opportunistic given my ink blot analogy: Well chosen text labels on hovering on an icon are equally valid and important in either case. You could make the icon for changing the waypoint type pretty much anything, a stylised burger for instance (such that no-one would have a clue from the graphic), as long as the accompanying text is explicit, at which point all users are certain of function. Thus my referring to ‘tinkering around the edges’… I see the new look as being of very little consequence either way.

I take your point regarding the two MRA components being distinct from the development perspective. I wish you would consider my viewpoint of them being absolutely essential to one another nonetheless. Combined, they are a potential release from poor route planning environments and the expense and built in obsolescence of dedicated devices, but only when both work reliably… We both know that really isn’t so in relation to one element… And that, for me, is a deal breaker.

Over 3 months on and still on iOS v.1.0.30 which is itself 5 months old. Where is this rapidly mythical seeming ‘major revamp’? Because I have had to give up with Navigation as it stands which, for my purposes, makes the whole MRA offering a rather worthless ‘investment’.

I have to say that this seems like yet more tinkering around the edges when there are far more fundamental matters that badly need tackling - particularly with regard to the Navigation app, which I have currently had to stop using due to its endless, ever changing, and in at least one instance downright dangerous, issues.

However, I think the new icons look fine. But then I had no problem at all with the old ones. To me, far more important than their purpose being obvious simply by the graphic (this will inevitably be open to interpretation, as surely as ink blots in a Rorschach test or ambiguous images such as the well known 'wife/mother in-law and 'frog or horses head' drawings) is that the purpose is displayed as text on hovering on an icon.

To that end, I would suggest that on hovering on the 'change waypoint type' icon, the text states 'change to via' if it's currently a shaping point, and 'change to shaping' if it's currently a via.

Not that I'm aware of @George-Muller, but you can quickly drag items in the waypoints list to a new position.

This is not something I personally have any need or desire to do, so I certainly can’t speak from experience... However, MRA appear to state that photos can be added to TRACKS (which I don’t use), not routes. If so, that might be worth bearing in mind?

A quick look on the web isn’t very revealing but, looking at the features available on these Drivesmart devices, I think they probably are Android based, like the Zūmo XT. Garmin seem very cagey about revealing their adoption of the Android OS - I haven’t a clue why though (maybe not wanting to frighten off users of iOS?). If I’m right, then they should be able to use .gpx 1.1, but trying 1.0 might just sort you out (backwards compatibility).

Of course, thinking on, there is also the Zumo XT (GPX 1.1) option in MRA Connector’s ‘select your device’ dropdown. That has to be worth trying too. Maybe I should have thought of that as an option earlier, but I hope I’ll be forgiven as I’m still using a (apparently horrendously ancient) Zūmo 390 perfectly happily and with great reliability!Again, I haven’t a clue why the XT needs its own ‘special version’ of what is the global standard file type??? But then, Garmin should've been using 1.1 for many years yet chose to stick with 1.0 until very recently, so maybe they just think of themselves as a bit ‘special’!

I hope one, the other (or both) option gets you sorted out.

@Dietmar-Frensemeyer @Phil-Beharrell Try exporting from MRA as a .gpx 1.0 file, rather than 1.1.

Complete the questionnaire and send it???‍️