Exporting routes from MRA to CRN via the app

the woodster

Well-known member
UKGSer Subscriber
Joined
Nov 14, 2016
Messages
1,336
Reaction score
704
Location
Orpington, South East London
I am beginning to understand how to use this device and the app and had a much better experience running a 3.5 hour route into deepest Kent yesterday. They say that you can sometimes have too much information but I like to see how other people are coping with it, so trawl the two Facebook groups.

There is a lot on there that I will never need to know but pretty much everyone recommends exporting the MRA route to the app using the GPX 1.1 format. My question is which one?: the route/track/POI option or the Track/POI one? And why?

Thank you.
 
If you want the route, the track and the points of interest, download the former. If you don’t want the route, download the latter. Whether the points of interest display, is another matter entirely.

See which you prefer and use that.
 
If you want the route, the track and the points of interest, download the former. If you don’t want the route, download the latter. Whether the points of interest display, is another matter entirely.

See which you prefer and use that.
Thank you. And am I right in thinking that the route contains 'shaping points' in a kind of 'take me along this way but not precisely', sort of way and the track is a continuous line which must not be strayed off?
 
Thank you. And am I right in thinking that the route contains 'shaping points' in a kind of 'take me along this way but not precisely', sort of way and the track is a continuous line which must not be strayed off?

Sort of, yes.

All routes must have two fixed points, A (the start) and B (the end). These can be joined by the algorithm of an app, with no intervention by the rider. In other words, the algorithm chooses the roads in between. The roads in between are marked by many invisible points, ‘visible’ only to the gps device.

You can then have a route, again from A to B, where you (the rider) dictates the roads to be ridden between the two fixed points. You shape the route by inserting shaping points, placed on the roads that you want to pass along. The algorithm then fills in the gaps with invisible marks, which the device can read.

Tracks are (most commonly) recordings of where you have ridden, a trail of breadcrumbs if you like. But, they can also be a version of a route, too. In the latter, the app takes the route, looks at the line from A to B or from A to B, via points 1,2,3,4 and 5 and inserts maybe thousands of invisible points in between, again like a trail of breadcrumbs.

So, why have both? There are various reasons, but I guess the most common are:

Tracks are fixed, they will not alter if you go off route or, more truthfully, ‘off track’.

Tracks will not have any voice prompts in them, like “Turn left in 300 yards”. Some devices have no ability to relay voice instructions, so using a track makes good sense.

Some owners like to have a route displayed, to use its voice prompts and (maybe) allow recalculations, but also have the fixed track displayed at the same time. Not all devices are capable of showing this dual route-and-track display.

Some owners only ride off-road, where there are no roads for a route to follow. They must use a track, by default.
 
Sort of, yes.

All routes must have two fixed points, A (the start) and B (the end). These can be joined by the algorithm of an app, with no intervention by the rider. In other words, the algorithm chooses the roads in between. The roads in between are marked by many invisible points, ‘visible’ only to the gps device.

You can then have a route, again from A to B, where you (the rider) dictates the roads to be ridden between the two fixed points. You shape the route by inserting shaping points, placed on the roads that you want to pass along. The algorithm then fills in the gaps with invisible marks, which the device can read.

Tracks are (most commonly) recordings of where you have ridden, a trail of breadcrumbs if you like. But, they can also be a version of a route, too. In the latter, the app takes the route, looks at the line from A to B or from A to B, via points 1,2,3,4 and 5 and inserts maybe thousands of invisible points in between, again like a trail of breadcrumbs.

So, why have both? There are various reasons, but I guess the most common are:

Tracks are fixed, they will not alter if you go off route or, more truthfully, ‘off track’.

Tracks will not have any voice prompts in them, like “Turn left in 300 yards”. Some devices have no ability to relay voice instructions, so using a track makes good sense.

Some owners like to have a route displayed, to use its voice prompts and (maybe) allow recalculations, but also have the fixed track displayed at the same time. Not all devices are capable of showing this dual route-and-track display.

Some owners only ride off-road, where there are no roads for a route to follow. They must use a track, by default.
That's very helpful, Richard. Much appreciated. All the info in one post. I am trying to work out the differences in terminology between the BMW App/CRN and MRA mapping terms. I'd like to understand the impact of choices I make whilst writing a route in MRA on exporting it to CRA/CRN, if any.
 
No problem.

Rather like the ‘P’ in PC, they are (to some degree or another) ‘personal’. What makes sense to me, might be different to what makes sense to you. In other words, use everything in a way that works for you.

That said, there are some basic ‘rules’, particularly when it comes to route creation and / or preference settings and / or recalculation (if any) that it is arguably best to adhere to.

Not least, the best way to learn, is to use the thing.

The UKGSer forum is a pretty good resource for help, as is MyRoute’s forum. I don’t know if there is a forum or Facebook site for BMW’s app and navigation system. If there is, hopefully it is equally good and not just full of moaning numpties, who shouldn’t be allowed to own a motorcycle, let alone a GPS device.
 


Back
Top Bottom