ETA destination != ETA last waypoint.
-
@Herman-Veldhuizen The easiest way for someone on this forum to help you is if you share your route. Make sure the privacy is set to public before sharing.
-
@Herman-Veldhuizen
You appear to have positioned all of the route points directly on bus stop symbols and not on the route track (black line). This can cause problems.
Personally, instead of positioning route points directly on top of the bus stops I would mark the bus stops with a POI and add information in the route point.
This has not answered your original question but I think it is a better solution for what you are trying to achieve.
-
Here is another example, at RP 105 the route wants to take you on a 15.5 km loop, ok, you wouldn't do this loop but the time and distance will be added to the route.
You could even add a photo to make it clear where the bus stop is.
Always willing to help if I can.
Triumph Tiger 1200 XRT called Tina.
MRA Navigation Next and SilverFox B8J bar buttons.
Quadlock wireless mount for IPhone 11.
Cardo Scala Packtalk Bold.
TomTom Rider 500. (In the cupboard now) -
Here is another example, at RP 105 the route wants to take you on a 15.5 km loop, ok, you wouldn't do this loop but the time and distance will be added to the route.
You could even add a photo to make it clear where the bus stop is.
@Nick-Carthew Yes the points are at bus stops. I can see that this can cause problems sometimes. The waypoints are imported from the national stop database. I cannot add more shaping points as this would make the ETA box unusable. And moving waypoints isn't really a good solution for thousands of stops.
It would be really great if we had a bus mode such that the app would also navigate through roads on bus stations as this would fix most of the problems (also 105).The ETA mismatch is still interesting. Maybe related to 91 where the app takes the ferry to turn me around. Or the map type. Saw a warning at some time that the route was created with OSM while the navigation uses Here. I will try to see what happens if the same maps are used. I was unaware that there was a map type mismatch.
-
@Nick-Carthew Yes the points are at bus stops. I can see that this can cause problems sometimes. The waypoints are imported from the national stop database. I cannot add more shaping points as this would make the ETA box unusable. And moving waypoints isn't really a good solution for thousands of stops.
It would be really great if we had a bus mode such that the app would also navigate through roads on bus stations as this would fix most of the problems (also 105).The ETA mismatch is still interesting. Maybe related to 91 where the app takes the ferry to turn me around. Or the map type. Saw a warning at some time that the route was created with OSM while the navigation uses Here. I will try to see what happens if the same maps are used. I was unaware that there was a map type mismatch.
@Herman-Veldhuizen In fact using car mode instead of truck mode already 'fixes' a few issues like the one at stop 91 and 105.
-
Are you navigating as route or track?
-
Are you navigating as route or track?
@Corjan-Meijerink I think that I was navigating as track.
-
@Corjan-Meijerink I think that I was navigating as track.
@Herman-Veldhuizen cool!
When navigating as track some approximations are made due to the nature of the track. Waypoints aren't part of the track but are snapped to approximations near the track.
The end of the route is easy, that's just the end
Everything in between is more complex.If you'd navigatie the route as actual route I firmly believe ETA destination == ETA last waypoint
Fun fact, I experienced a minor issue like this while working on some stuff today and improved the approximation algorithm a bit which resolved the issue I was having. My guess is that your issue might be resolved by this too. You'd need to wait for the next update to discover that.
Do feel free to let me know here if the issue disappears when navigating as route.
-
@Herman-Veldhuizen cool!
When navigating as track some approximations are made due to the nature of the track. Waypoints aren't part of the track but are snapped to approximations near the track.
The end of the route is easy, that's just the end
Everything in between is more complex.If you'd navigatie the route as actual route I firmly believe ETA destination == ETA last waypoint
Fun fact, I experienced a minor issue like this while working on some stuff today and improved the approximation algorithm a bit which resolved the issue I was having. My guess is that your issue might be resolved by this too. You'd need to wait for the next update to discover that.
Do feel free to let me know here if the issue disappears when navigating as route.
@Corjan-Meijerink ok cool. I live close to this route somewhere halfway (was testing the app while being passenger in the bus) and just now restarted the navigation in route mode. Indeed then the ETA's are matching. No need to hurry to release any fix for this.
-
@Corjan-Meijerink ok cool. I live close to this route somewhere halfway (was testing the app while being passenger in the bus) and just now restarted the navigation in route mode. Indeed then the ETA's are matching. No need to hurry to release any fix for this.
@Herman-Veldhuizen Thanks for letting me know!
