Route recalculation doesn't account for the time necessary to recalculate #10190

New issue

Open

opened 2025-02-03 05:25:21 +00:00 by AtmosphericIgnition · 0 comments

AtmosphericIgnition commented

2025-02-03 05:25:21 +00:00

(Migrated from github.com)

⚠ Have you searched for similar, already existing issues?
Yes

Describe the issue
When I'm driving, and miss the turn the navigation wants me to take, the app starts recalculating a new route. This recalculation doesn't account for the speed the car is moving, so when the app finishes the calculation, I'm already way past the turn it wanted me to take, resulting in another recalculation, which often just ends up doing the same thing, making it impossible to get a new route, unless I stop, or slow down significantly. This issue is probably present in all navigation modes, but is probably only noticeable while driving because of the high speed.

Steps to reproduce

Use navigation
Miss turn
See the app recalculate a new route
Get a route which asks to make a turn you already passed.
See this process continue in a cycle until the spacing between possible turns increases enough for the app to make the calculation in time, or you slow down.

Expected behaviour
A recalculated route should account for the time it takes to calculate it, display it, and give the driver enough time to react.

Screenshots
Video of the issue. In this video, I continue straight, instead of turning, because the navigation is asking me to take a route through a residential neighborhood, instead of the main road I'm already on (that is a separate issue I run into). The app then takes time to recalculate another route through the next street, but by the time the new route shows up, I'm already well past that street. At the end of the video, when I stop at an intersection, you can see the map twitching as I described in #10128.

System information:

Operating system and its version: Android 15 - GrapheneOS
Organic Maps version: 2025.01.28
Device Model: Pixel 8 Pro

Additional context

⚠ Have you searched for similar, already existing issues? Yes **Describe the issue** When I'm driving, and miss the turn the navigation wants me to take, the app starts recalculating a new route. This recalculation doesn't account for the speed the car is moving, so when the app finishes the calculation, I'm already way past the turn it wanted me to take, resulting in another recalculation, which often just ends up doing the same thing, making it impossible to get a new route, unless I stop, or slow down significantly. This issue is probably present in all navigation modes, but is probably only noticeable while driving because of the high speed. **Steps to reproduce** 1. Use navigation 2. Miss turn 3. See the app recalculate a new route 4. Get a route which asks to make a turn you already passed. 5. See this process continue in a cycle until the spacing between possible turns increases enough for the app to make the calculation in time, or you slow down. **Expected behaviour** A recalculated route should account for the time it takes to calculate it, display it, and give the driver enough time to react. **Screenshots** [Video](https://youtu.be/_wMhsyDyteM) of the issue. In this video, I continue straight, instead of turning, because the navigation is asking me to take a route through a residential neighborhood, instead of the main road I'm already on (that is a separate issue I run into). The app then takes time to recalculate another route through the next street, but by the time the new route shows up, I'm already well past that street. At the end of the video, when I stop at an intersection, you can see the map twitching as I described in #10128. **System information:** - Operating system and its version: Android 15 - GrapheneOS - Organic Maps version: 2025.01.28 - Device Model: Pixel 8 Pro **Additional context**

👍 2

This repo is archived. You cannot comment on issues.