Shaping points and Via points
-
@Jörgen said in Shaping points and Via points:
The reason I’m asking is that the automatic skip feature didn’t work for me that way
If you primarily use shaping points for planning rather than navigation, try the "routes as track" navigation option and toggle "Use all waypoints" off.
You get rid of all SPs, a clean look and perfect focus on your VIAs.
I like this feature when I have a route with plenty of SPs just to nail it to a specific path (typically when I convert a route-track into a route).
@Martin-Wilcke I wish I could use MRA like that. I also would like to use shaping points just to shape the route and nothing more (no need to have ETA info for them). But the fact that via points are not skipped prevents me from doing this. Hopefully one day MRA can pick up the route when I am back on it again (meaning skip any point which is behind me).
-
@Martin-Wilcke I wish I could use MRA like that. I also would like to use shaping points just to shape the route and nothing more (no need to have ETA info for them). But the fact that via points are not skipped prevents me from doing this. Hopefully one day MRA can pick up the route when I am back on it again (meaning skip any point which is behind me).
@Herman-Veldhuizen said in Shaping points and Via points:
@Martin-Wilcke I wish I could use MRA like that. I also would like to use shaping points just to shape the route and nothing more (no need to have ETA info for them). But the fact that via points are not skipped prevents me from doing this. Hopefully one day MRA can pick up the route when I am back on it again (meaning skip any point which is behind me).
@Herman-Veldhuizen
Just use VIA only for start and finish and ride the route as track will solve your issue? -
@Herman-Veldhuizen said in Shaping points and Via points:
@Martin-Wilcke I wish I could use MRA like that. I also would like to use shaping points just to shape the route and nothing more (no need to have ETA info for them). But the fact that via points are not skipped prevents me from doing this. Hopefully one day MRA can pick up the route when I am back on it again (meaning skip any point which is behind me).
@Herman-Veldhuizen
Just use VIA only for start and finish and ride the route as track will solve your issue?@BertM No I need the ETA info to my waypoints which represent possible stops.
-
@BertM No I need the ETA info to my waypoints which represent possible stops.
@Herman-Veldhuizen said in Shaping points and Via points:
@BertM No I need the ETA info to my waypoints which represent possible stops.
ok, clear.
Never tried it, but does a 3rd VIA point not work in a track? -
@Herman-Veldhuizen said in Shaping points and Via points:
@BertM No I need the ETA info to my waypoints which represent possible stops.
ok, clear.
Never tried it, but does a 3rd VIA point not work in a track?@BertM You can get the ETA info for viapoints (hand icon) or for both viapoints and shaping points (droplet icon). How you navigate a route (route or route as track) makes currently no difference.
If you use shaping points for your possible stops they will eventually be skipped (still annoying to be sent back to the ones you missed and you will unfortunately also see the ETA for points which you added for the sole purpose to shape the route).
If you use via points for your possible stops then you can filter out the shaping points but the via points will never be skipped.
A number of people (and me) in this forum would like to see that the route can get priority over the points. They dont necessarily want to stop at each possible stop and expect the app to skip each point which is behind them on the route.
Most apps I know work that way. Apparently there is something missing in the HERE platform today to make this an option. -
@Herman-Veldhuizen
If you make the stops “possible” I get your point. -
@BertM You can get the ETA info for viapoints (hand icon) or for both viapoints and shaping points (droplet icon). How you navigate a route (route or route as track) makes currently no difference.
If you use shaping points for your possible stops they will eventually be skipped (still annoying to be sent back to the ones you missed and you will unfortunately also see the ETA for points which you added for the sole purpose to shape the route).
If you use via points for your possible stops then you can filter out the shaping points but the via points will never be skipped.
A number of people (and me) in this forum would like to see that the route can get priority over the points. They dont necessarily want to stop at each possible stop and expect the app to skip each point which is behind them on the route.
Most apps I know work that way. Apparently there is something missing in the HERE platform today to make this an option.I do remember a long discussion on your use case.
I'm fine with the current logic; however, I'd follow this view:
-
When navigating a track, your focus is on "the line". If you deviate, with auto-recalc turned on, the app will redirect you to the most logical point on the track without taking any particular points into account - there are none.
-
Navigating "route as track" is a bit of a hybrid, but it should follow the same pattern. All existing points (SPs and VIAs) will provide additional information (ETA) but will not affect your navigation and will therefore be skipped automatically.
-
If you want to consider VIAs (and SPs) when recalculating, you should navigate a route because it is its natural behaviour
-
-
I do remember a long discussion on your use case.
I'm fine with the current logic; however, I'd follow this view:
-
When navigating a track, your focus is on "the line". If you deviate, with auto-recalc turned on, the app will redirect you to the most logical point on the track without taking any particular points into account - there are none.
-
Navigating "route as track" is a bit of a hybrid, but it should follow the same pattern. All existing points (SPs and VIAs) will provide additional information (ETA) but will not affect your navigation and will therefore be skipped automatically.
-
If you want to consider VIAs (and SPs) when recalculating, you should navigate a route because it is its natural behaviour
@Martin-Wilcke Unfortunately this is not what I observe. I wish it did and i believe it worked like that for a short while when route as track was added.
ETA info to my (optional) waypoints are important for me. So I have never considered pure track navigation.
When I navigate my route as track the app DOES use the way points in my route to navigate. I suppose it tries to find a logical reentry point but it also sends me back to a waypoint. How many times it tries to send me back to a shaping point seems to depend on how far the next point is. -
-
@BertM You can get the ETA info for viapoints (hand icon) or for both viapoints and shaping points (droplet icon). How you navigate a route (route or route as track) makes currently no difference.
If you use shaping points for your possible stops they will eventually be skipped (still annoying to be sent back to the ones you missed and you will unfortunately also see the ETA for points which you added for the sole purpose to shape the route).
If you use via points for your possible stops then you can filter out the shaping points but the via points will never be skipped.
A number of people (and me) in this forum would like to see that the route can get priority over the points. They dont necessarily want to stop at each possible stop and expect the app to skip each point which is behind them on the route.
Most apps I know work that way. Apparently there is something missing in the HERE platform today to make this an option.@Herman-Veldhuizen said in Shaping points and Via points:
A number of people (and me) in this forum would like to see that the route can get priority over the points. They dont necessarily want to stop at each possible stop and expect the app to skip each point which is behind them on the route.
Most apps I know work that way. Apparently there is something missing in the HERE platform today to make this an option.That's correct, there is no way of knowing what point is "behind" you in a route, only the first targeted route point is relevant in the calculations. I am not sure how other apps work, but I do know that Garmins, when navigating a track, do "sense" if they are actually on the track and go from there (which also is not always the most desirable method).
What I would like to know is, considering your long standing (constructive!) critique and your claim that most apps work better in this regard, what it is that keeps you on MRA. It must have very strong advantages otherways
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ Motorola Thinkphone + MRA app -
@Martin-Wilcke Unfortunately this is not what I observe. I wish it did and i believe it worked like that for a short while when route as track was added.
ETA info to my (optional) waypoints are important for me. So I have never considered pure track navigation.
When I navigate my route as track the app DOES use the way points in my route to navigate. I suppose it tries to find a logical reentry point but it also sends me back to a waypoint. How many times it tries to send me back to a shaping point seems to depend on how far the next point is.@Herman-Veldhuizen said in Shaping points and Via points:
Unfortunately this is not what I observe.
My thoughts were meant as a suggestion for a change:
When navigating "Routes as tracks", all waypoints (SPs and VIAs) should be skipped automatically, as this is how track navigation works.
From a conceptual POV, it is "line priority over point priority".
-
@Herman-Veldhuizen said in Shaping points and Via points:
A number of people (and me) in this forum would like to see that the route can get priority over the points. They dont necessarily want to stop at each possible stop and expect the app to skip each point which is behind them on the route.
Most apps I know work that way. Apparently there is something missing in the HERE platform today to make this an option.That's correct, there is no way of knowing what point is "behind" you in a route, only the first targeted route point is relevant in the calculations. I am not sure how other apps work, but I do know that Garmins, when navigating a track, do "sense" if they are actually on the track and go from there (which also is not always the most desirable method).
What I would like to know is, considering your long standing (constructive!) critique and your claim that most apps work better in this regard, what it is that keeps you on MRA. It must have very strong advantages otherways
@Con-Hennekens Yes MRA has many good things. But thats maybe something for another topic. I might come over as somebody who complains a lot but I am impressed by how much work has been done and how the app develops. Kudos to the team!
One thing I want to mention is that MRA today is not only for bikers and I hope it stays like that. It's up to the team of coarse but I see big potential for other users like me. MRA could for example have the concept of a pluggable route library and offer it with a separate license. Companies could have their own internal library that way.
The issue that the route cannot be given the priority over the points is one which keeps popping up in this forum. I hope (and are convinced) that it will be possible one day. I dont have many issues with MRA but this one tops the list by far.
-
@Con-Hennekens Yes MRA has many good things. But thats maybe something for another topic. I might come over as somebody who complains a lot but I am impressed by how much work has been done and how the app develops. Kudos to the team!
One thing I want to mention is that MRA today is not only for bikers and I hope it stays like that. It's up to the team of coarse but I see big potential for other users like me. MRA could for example have the concept of a pluggable route library and offer it with a separate license. Companies could have their own internal library that way.
The issue that the route cannot be given the priority over the points is one which keeps popping up in this forum. I hope (and are convinced) that it will be possible one day. I dont have many issues with MRA but this one tops the list by far.
@Herman-Veldhuizen, by no means I meant to imply you being a complainer, hence the addition of the word "constructive!" as in "opbouwende kritiek" in Dutch. I think your way of usage is interesting for sure but probably not practised a lot, not by the target audience anyway. It could be a future expansion perhaps, but in that case indeed probably as an extra licence (more as a logistics solution). I don't think however that is something MRA is willing to spent time on at the moment. For sure not until the new web planner is live and bug free.
@Martin-Wilcke said in Shaping points and Via points:
When navigating "Routes as tracks", all waypoints (SPs and VIAs) should be skipped automatically, as this is how track navigation works.
That is a bit strange, since the one-and-only function of a VIA point is that it cannot be skipped automatically
. How track navigation works is without any route points at all.I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ Motorola Thinkphone + MRA app -
@Herman-Veldhuizen, by no means I meant to imply you being a complainer, hence the addition of the word "constructive!" as in "opbouwende kritiek" in Dutch. I think your way of usage is interesting for sure but probably not practised a lot, not by the target audience anyway. It could be a future expansion perhaps, but in that case indeed probably as an extra licence (more as a logistics solution). I don't think however that is something MRA is willing to spent time on at the moment. For sure not until the new web planner is live and bug free.
@Martin-Wilcke said in Shaping points and Via points:
When navigating "Routes as tracks", all waypoints (SPs and VIAs) should be skipped automatically, as this is how track navigation works.
That is a bit strange, since the one-and-only function of a VIA point is that it cannot be skipped automatically
. How track navigation works is without any route points at all.@Con-Hennekens In this topic (https://forum.myrouteapp.com/topic/9552/waypoint-skipping.-mra-vs-beeline) I made a test route in both MRA and Beeline. Both have bikers as their target audience. The behaviour of the apps are however very different when it comes to skipping points. I dont think that Beelines behaviour is odd.
-
i also looked at beeline. beeline is better is follow the plan you made. MRA is better to plan. MRA Next has many good point but also to many functions and some main function like how to deal with track and gpx file or skipping shaping point or follow the route when back on the route you planned are in my opinion not perfect. I hope in planning of future development.
-
@Herman-Veldhuizen, by no means I meant to imply you being a complainer, hence the addition of the word "constructive!" as in "opbouwende kritiek" in Dutch. I think your way of usage is interesting for sure but probably not practised a lot, not by the target audience anyway. It could be a future expansion perhaps, but in that case indeed probably as an extra licence (more as a logistics solution). I don't think however that is something MRA is willing to spent time on at the moment. For sure not until the new web planner is live and bug free.
@Martin-Wilcke said in Shaping points and Via points:
When navigating "Routes as tracks", all waypoints (SPs and VIAs) should be skipped automatically, as this is how track navigation works.
That is a bit strange, since the one-and-only function of a VIA point is that it cannot be skipped automatically
. How track navigation works is without any route points at all.@Con-Hennekens said in Shaping points and Via points:
since the one-and-only function of a VIA point is that it cannot be skipped automatically
Hence, my suggestion for a change.
When navigating a track, there are two common concepts to lead you back in case of a deviation:
-
to the point where you left the track
-
to the most logical point in the forward direction
There might be additional "points" (waypoints, POIs, whatever) along the track; however, they are informational only (may be announced) and do not influence the navigation.
This concept is becoming increasingly popular, and it would be a good idea to implement it in MRA as well.
-
