Route Color doesn't change after skipping Waypoint
-
wrote on 28 Feb 2023, 23:42 last edited by
I created a route with a wrong first VIA Point, to test skipping WP in HERE Map.
Skipping this wrong VP1 ->everything's ok.
Skipping WP 2 and WP 3, Route Color should be white instead of blue.
After Skipping WP 4 color changes to right white color. Why not before? And MRA finds a new Route to come to WP 5. ok.
But the new route in blue is over VP 1, which was skipped first?
Is this correct?
I just realize, that there is actually no chance to solve this situation, because all other roads are dead ends or filled with skipped waypoints. MRA solved the situation by driving over the VP1. Shouldn't there have been an error here? I notice by myself that this is really a freaky theoretical situation, so it is not a high priority. Sorry.Greetings
Ronni
-
I created a route with a wrong first VIA Point, to test skipping WP in HERE Map.
Skipping this wrong VP1 ->everything's ok.
Skipping WP 2 and WP 3, Route Color should be white instead of blue.
After Skipping WP 4 color changes to right white color. Why not before? And MRA finds a new Route to come to WP 5. ok.
But the new route in blue is over VP 1, which was skipped first?
Is this correct?
I just realize, that there is actually no chance to solve this situation, because all other roads are dead ends or filled with skipped waypoints. MRA solved the situation by driving over the VP1. Shouldn't there have been an error here? I notice by myself that this is really a freaky theoretical situation, so it is not a high priority. Sorry.Greetings
RonniThanks for your questions @Ronni!
This is actually expected behavior.
The original route is shown as white. If the calculated route overlaps the original line, you won't see the white line.So what happened here?
- Skipping WP1, route takes the turn right. You'll only see the white part of the original route going to WP1
- Skipping WP2, still means the fastest route to WP3 is past WP2. So the calculated route will match the original part after skipping WP2.
- Skipping WP3, same story as above!
- Skipping WP4, now means the app wants to navigate you as fast as possible to WP5. This apparently is a whole different route! The calculated route (blue) differs significantly from the original (white). This is shown correctly.
So in summary: all works as expected
Hope this clarifies what happens.Best,
Corjan -
I created a route with a wrong first VIA Point, to test skipping WP in HERE Map.
Skipping this wrong VP1 ->everything's ok.
Skipping WP 2 and WP 3, Route Color should be white instead of blue.
After Skipping WP 4 color changes to right white color. Why not before? And MRA finds a new Route to come to WP 5. ok.
But the new route in blue is over VP 1, which was skipped first?
Is this correct?
I just realize, that there is actually no chance to solve this situation, because all other roads are dead ends or filled with skipped waypoints. MRA solved the situation by driving over the VP1. Shouldn't there have been an error here? I notice by myself that this is really a freaky theoretical situation, so it is not a high priority. Sorry.Greetings
RonniAlpha testerwrote on 1 Mar 2023, 08:53 last edited by Con Hennekens 3 Jan 2023, 09:01@Ronni, Skipping a WP is by no means a method to avoid it. So a route through a WP being skipped will very often go through the skipped WP if it's in the same direction.
-
@Ronni, Skipping a WP is by no means a method to avoid it. So a route through a WP being skipped will very often go through the skipped WP if it's in the same direction.
@Con-Hennekens Correct!
-
I created a route with a wrong first VIA Point, to test skipping WP in HERE Map.
Skipping this wrong VP1 ->everything's ok.
Skipping WP 2 and WP 3, Route Color should be white instead of blue.
After Skipping WP 4 color changes to right white color. Why not before? And MRA finds a new Route to come to WP 5. ok.
But the new route in blue is over VP 1, which was skipped first?
Is this correct?
I just realize, that there is actually no chance to solve this situation, because all other roads are dead ends or filled with skipped waypoints. MRA solved the situation by driving over the VP1. Shouldn't there have been an error here? I notice by myself that this is really a freaky theoretical situation, so it is not a high priority. Sorry.Greetings
Ronniwrote on 1 Mar 2023, 08:59 last edited by@Ronni The route after skipping wp4 doesn't actually include vp1 as part of the route, i.e. you can't skip vp1 again to get a different result. It just so happens that the fastest route from your current location to wp5 is calculated to go past vp1.
-
Thanks for your questions @Ronni!
This is actually expected behavior.
The original route is shown as white. If the calculated route overlaps the original line, you won't see the white line.So what happened here?
- Skipping WP1, route takes the turn right. You'll only see the white part of the original route going to WP1
- Skipping WP2, still means the fastest route to WP3 is past WP2. So the calculated route will match the original part after skipping WP2.
- Skipping WP3, same story as above!
- Skipping WP4, now means the app wants to navigate you as fast as possible to WP5. This apparently is a whole different route! The calculated route (blue) differs significantly from the original (white). This is shown correctly.
So in summary: all works as expected
Hope this clarifies what happens.Best,
Corjanwrote on 1 Mar 2023, 12:01 last edited by@Corjan-Meijerink said in Route Color doesn't change after skipping Waypoint:
Hope this clarifies what happens.
Honestly, it took me a minute to understand, cause i didn't knew this behaviour before.
Everything is fine now.@Con-Hennekens
@Herko-ter-Horst
@Corjan-MeijerinkThank you all for your precise explanations.
Greetings
Ronni