This is routing incorrectly isn't it?!?

[Tim Watson]

So I'm testing MRA via Android Auto on a Chigee AIO-5 (spoiler - what a disaster, back to the Nav6), and I created a test route that routes in a way I wouldn't expect.

Starting at 1, I'd expect it to route to 2, 3, 4 and then 5 which is a via point. No. It routes 1 to 2 to 3, and at the t-junction after 3 it turns left towards 6. What?! Auto skipping of waypoints was on, but my understanding is that it never skips via points, only shaping points. So why would it turn left after waypoint 3?

Am I misunderstanding something?

[Marinus van Deudekom]

@Tim-Watson Hi Tim
I guess that there's wrong in your route. If you will share that route here and set it to public we can have a look at it and help you out

[Tim Watson]

@Marinus-van-Deudekom Thanks.

https://www.myrouteapp.com/en/social/route/9756892?mode=share

[Marinus van Deudekom]

@Tim-Watson Hi Tim
Your shapingpoint 6 and especially your viapoint 5 are off the route. My guess is that due to the crossing in the route MRA couldn't determine the right path do therefore skipped viapoint 5 and calculated as it did.
Could you try it again with the points exactly on the route. To do so make sure you zoom in Max

[Tim Watson]

@Marinus-van-Deudekom I'll update the via point and try again. It won't be today as access to that location is now closed, but I'll do it early next week.

However, because I actually wanted to go to the via point 5 on today's test ride, I had to pull over, run the app on my phone (not android auto) and long-press 5 and tell it to start again from there. It then managed to successfully get to 5 by skipping all the preceeding waypoints. This didn't take it over that junction where the route crosses itself. So at the moment I'm not convinced the placement of 5 slightly off the road is relevant as MRA did manage to navigate there.

My gut feeling is that it got confused because the circular route crossed and it just figured it could get to the end of the route quicker by simply turning left. But that should be a no-no if it would skip a via point.

[Marinus van Deudekom]

@Tim-Watson Later this evening I'll look at it again on a pc. Maybe I van figure out what caused your trouble

[Stephen Rowland]

@Tim-Watson I notice on street view that your via point is on a gated road. Although you have been able to place the via point perhaps the algorithm thinks you cannot get to that point. The gate is closed when I look at the street view travelling the opposite way to your plan

[Tim Watson]

@Stephen-Rowland Hi Stephen. Yes, that's another little complication. The route I chose to get to the via point takes you on a public access road through the grounds of a stately home. During the day all those gates are open and you can get into the site one way and out the other, as you can see on the route. It's possible, as you say, that planning the route was not a problem but the navigation software baulks at it. When the software did go direct to point 5 I was already at a location where it went in via the "exit" on the planned route, right near the via point.

What I'll do is make a copy of this route and move the via point onto the road as Marinus suggested, but also make a further route that has a similar crossing of the paths but avoids going through the grounds of the stately home.

I'll update this thread early next week.

I was hoping to use MRA with Android Auto for a 750-mile ride this weekend, but its oddities with a 15-mile test route (along with locking solid and needing the phone rebooting) means I'm back to the Nav6, which is a big shame.

[Marinus van Deudekom]

@Tim-Watson Hi Tim
Took another glance at it with the PC and then I saw the light:
1: You've made the route with the motor profil on
2: I changed it to auto witch is the only type you can use at this moment with the Here maps. Then it became quit clear. The route that you wanted to go is beeing altered and giving you the route isues that you had.
3 solution: I added a couple of shaping points and that should do the trick.
It looks like this:

Here's the url to the route I've changed:
https://www.myrouteapp.com/route/open/9782354
If you have another testrun I think it will provide you want you wanted.
My comments in the first responce are nevertheless valid. You can see that I've placed the shaping and viapoint ON the route. Thus making shure the desired route is calculated.
make your routes with the auto profil on

[Tim Watson]

@Marinus-van-Deudekom Hey Marinus. Thanks very much for taking the time to have another look.

I'm not sure what you mean by the "motor profile". Do you mean the "Transport mode" on the "Start a new route" screen? Possible not, as I can't see an "Auto" option for this. Or do you mean "Auto" as in automobile as in "Car".

Apologies if I'm looking completely in the wrong place!!

If you do mean the problem is that I created the route as "Motorcycle" instead of "Car":

1. What is the difference? I've not seen anything in the MRA documentation to say why one would use one type over another
2. How does one change the profile for an existing route?
3. What did you see change with the route? When I use the bar at the bottom of the route planner to follow my original route, it goes the correct way

Thanks again for your time!!

[Marinus van Deudekom]

@Tim-Watson
Hi Tim if you change the settings that's what happens. The motorcycle profil is not usefull at this moment in time>
You can change is here

[Marinus van Deudekom]

@Tim-Watson If you change the transport mode in your route to car you can see yourself what happens.
then I added a couple of shapingpoints to force the route the way is was

[Marinus van Deudekom]

@Tim-Watson

[Tim Watson]

@Marinus-van-Deudekom Thank you!

Wow, by changing the Transport mode from Motorcycle to Car the route length instantly changed from 14.54 to 18.92 miles.

I'm really grateful you found that, and I look forward to testing it.

However, I'm intrigued why the devs put the Transport mode in, and allowed a default mode other than Car to be set in the user profile, when only the Car profile works with the only map supported by the app?

I can see the Transport mode changes something, but is it documented anywhere what is changing? I would expect this route to navigate the same by car, motorcycle or camel!

[Marinus van Deudekom]

@Tim-Watson That I don't know, my camel riding skills are close to none
Driving by car or motorcycle is the same as far as Here is concerned. The other profiles like motorhome actually have impact on the route.
For now just use the car profile and enjoy your rides

[Con Hennekens]

@Marinus-van-Deudekom said in This is routing incorrectly isn't it?!?:

My guess is that due to the crossing in the route MRA couldn't determine the right path do therefore skipped viapoint 5 and calculated as it did.

A VIA point is there to NOT be autoskipped. If a waypoint is too far off a road so that it cannot be reached, you will get a warning and the route wil not start at all. So I do not think that is it.

@Tim-Watson, do I understand correctly that you were navigating this route on your Nav6? In that case the device itself chooses how to navigate between waypoints. the (non?) logic to skip WP5 therefore is inherent to the device, not the route. It looks like a really small loop. Maybe there is some logic in the device to prevent those (usually unwanted) loops, I really cant say.

[Con Hennekens]

@Marinus-van-Deudekom said in This is routing incorrectly isn't it?!?:

1: You've made the route with the motor profil on
2: I changed it to auto witch is the only type you can use at this moment with the Here maps.

Although there have been some problems related to the Motorbike profile, it is absolutely untrue to says that it does not work with HERE maps. It is perfectly usable, even if there are circumstances in which it might be better to use CAR profile instead.

[Tim Watson]

@Con-Hennekens Hi. No, I used a Nav6 before this week, but this week am trying out MRA and a Chigee with Android Auto. It's not going very well. Back to the Nav6 for now.

[Tim Watson]

Although there have been some problems related to the Motorbike profile, it is absolutely untrue to says that it does not work with HERE maps. It is perfectly usable, even if there are circumstances in which it might be better to use CAR profile instead.

Can you explain what these problems with the motorcycle profile have been? I can't find anything that says which to use, or indeed which to avoid.

[Marinus van Deudekom]

@Con-Hennekens hoi @Con-Hennekens
The advice from the devs is not to use the profile. Like in Tim's case it causes problems that at completely unnecessary. I agree with the devs. Maybe you can explain what would be useful in the bike profile. I could guess like maybe road closures für bikes but I experienced that even that doesn't work at this time. What could be the advantage of that profile.