Track recalculation?
-
So I created a route on the web with lots of shaping points, then today when I opened the route on iOS app, it asked whether I wanted to navigate by Route or Track - I chose track.
It started navigating to the start of the route/track, and then gave me turn by turn instructions - all good so far.
Then I decided to deviate from the route/track, and took a different turning. There was no re-routing, which is what I expected, but annoyingly kept repeatedly presenting an error “could not calculate route” - Is this expected?
I would’ve thought for a track navigation there is no re-routing and that once you deviate, it’s up to the the rider to course correct and get back on the track?
-
So I created a route on the web with lots of shaping points, then today when I opened the route on iOS app, it asked whether I wanted to navigate by Route or Track - I chose track.
It started navigating to the start of the route/track, and then gave me turn by turn instructions - all good so far.
Then I decided to deviate from the route/track, and took a different turning. There was no re-routing, which is what I expected, but annoyingly kept repeatedly presenting an error “could not calculate route” - Is this expected?
I would’ve thought for a track navigation there is no re-routing and that once you deviate, it’s up to the the rider to course correct and get back on the track?
@Rajp track navigation also includes active rerouting back to the track. It attempts to preserve as much as the original track as possible.
Could you let me know what app version / travelmode you were using?
-
@Rajp track navigation also includes active rerouting back to the track. It attempts to preserve as much as the original track as possible.
Could you let me know what app version / travelmode you were using?
@Corjan-Meijerink App version: 4.0.8 - 244; Travel Mode: Motorcycle (the best mode to travel by
) -
@Corjan-Meijerink App version: 4.0.8 - 244; Travel Mode: Motorcycle (the best mode to travel by
)@Rajp Thanks for sharing and definitely agree!
The 4.1.0 update contains improvements for this too!
