Maybe @Corjan-Meijerink can give an authoritative answer straight from the horse’s mouth on the use of the motorcycle profile, both in planning mode and navigation mode (some of us only use MRA for planning).
It’s important to know if we shouldn’t be using these modes, and if it is the case then it needs to be made more prominent to stop new users being unaware and having a really bad experience. You can see from the original post in this thread that the new user has gone back to the Nav VI because of a bad experience. That’s not good if the root cause is something that was known about but poorly communicated.
Hallo,
Please look at,
Toolkit / Avoid / Unpaved Roads
These settings must be readjusted for each new route, Why?
@Dae-0 said in This is routing incorrectly isn't it?!?:
Maybe @Corjan-Meijerink can give an authoritative answer straight from the horse’s mouth on the use of the motorcycle profile, both in planning mode and navigation mode (some of us only use MRA for planning).
I happen to know that @Corjan-Meijerink uses the motorbike profile almost exclusively himself. The motorbike profile is there because it is included in the HERE SDK. Maybe Corjan cares to elaborate?
Roads exist that are closed for 4 wheels, but are open for 2 wheels.
Closures with this sign are not closed for motorbikes. I can only assume the motorbike profile takes that into account correctly.
@Tim-Watson said in This is routing incorrectly isn't it?!?:
Can you explain what these problems with the motorcycle profile have been?
There was a problem with showing the wrong exit at roundabouts that appeared to be exclusively for the motorbike profile. I understand that this has been solved for some time already.
Also there is an ongoing problem where route optimization as "shortest" instead of "quickest" is not available for the motorbike profile. That is mainly a problem if you want to go over scheduled ferries. In that case it is advised to switch to car profile and the "shortest route" optimization.
I am not affiliated with MyRoute-App. The help I am offering is entirely voluntary.
I am just an enthusiastic user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
@Con-Hennekens this is what I mean @Con-Hennekens the bike profile doesn’t look at the closed roads for bikes. I Hope @Corjan-Meijerink will give his final verdict so we can close this part of the subject 
@Dae-0 said in This is routing incorrectly isn't it?!?:
You can see from the original post in this thread that the new user has gone back to the Nav VI because of a bad experience. That’s not good if the root cause is something that was known about but poorly communicated.
That for sure is true. However it is known that almost no one reads such a documentation. Most people just ask questions on the forum, and many users are here to help 
Concerning @Tim-Watson his bad experience, it is very likely that probably unintentional some skipping buttons were pressed. A VIA point (hand symbol) does not get skipped automatically. Therefore it is good info whether the problem reoccurs. If it does, it is best to submit a support ticket, so the devs can ask for logs to check what's wrong.
@Marinus-van-Deudekom said in This is routing incorrectly isn't it?!?:
the bike profile doesn’t look at the closed roads for bikes.
Can you substantiate that with an example? It would be very good to know, and to mention to HERE.
I am not affiliated with MyRoute-App. The help I am offering is entirely voluntary.
I am just an enthusiastic user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
@Con-Hennekens yes I can
Making an route for my RouteXpert training I couldn’t find why a street was impossible to drive trough with the OSM. Looking at the situation Sith streetview I discovered that thé Riad was closed for bikes. Here and TomTom didn’t have that problem. Changing to the bike profile didn’t change anything. So for once OSM was right.
Other example if you want to cross a river by ferry. Most of the times the bike profile will lead to a non ferry crossing of the river where when using the car profile you can cross the river by ferry
@Marinus-van-Deudekom said in This is routing incorrectly isn't it?!?:
Making an route for my RouteXpert training I couldn’t find why a street was impossible to drive trough with the OSM. Looking at the situation Sith streetview I discovered that thé Riad was closed for bikes. Here and TomTom didn’t have that problem. Changing to the bike profile didn’t change anything. So for once OSM was right.
Yes, but that does not proof that the motorbike profile does not honor the car-only closure correctly. It more like proofs that HERE and TomTom are unaware (yet) of the bike-closure. Did you check that with HERE and TomTom?
Other example if you want to cross a river by ferry. Most of the times the bike profile will lead to a non ferry crossing of the river where when using the car profile you can cross the river by ferry
I already explained that above, and this is also no proof of the motorbike profile to disregard roads that are open for bikes but not for cars.
I am not affiliated with MyRoute-App. The help I am offering is entirely voluntary.
I am just an enthusiastic user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
@Tim-Watson said in This is routing incorrectly isn't it?!?:
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.
Why is using the Chigee a disaster?
@Tim-Watson said in This is routing incorrectly isn't it?!?:
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.
Why is using the Chigee a disaster?
