Don't stop routing because of outdated maps

[mwerle]

Describe the idea

Use existing offline maps for routing even if they are "outdated".

Especially if those maps were used to calculate the original route anyway!

---

Recently (OsmAnd 4.8.6, possibly a version or two earlier), I've had situations where my routing stops. The route disappears and refuses to recalculate, often after passing through a tunnel or missing a turn.

Looking at the routing tab, "Details", the cause is listed as "Missing or Outdated Maps". The route calculated just fine prior to setting off, and clicking on "use offline maps" (sorry, I can't remember the exact UI wording) it again recalculates fine. The device I am using is offline (no internet connection), so I have no idea how it suddenly decides that some maps are "outdated". When I do update the maps, I update all of them at once so they should all be from the same time.

IMHO, there is absolutely NO REASON EVER for OsmAnd to :

1. automatically stop displaying a calculated route unless it is immediately replaced with another route. (ie, recalculate the route in the background so the driver can attempt to get onto the old route manually in the meantime)
2. refuse to recalculate using old maps - using old maps is better than no route at all!

Stopping routing part-way through a trip can cause significant difficulties, especially on a motorcycle.

Expected behaviour

Routes continue to be displayed and/or recalculated using the offline maps on the device.

This should be the default, but if, due to legal requirements in the US or whatever it is necessary to stop routing and have this manual override to resume routing, at least please make this an option so people do not need to stop in order to re-enable routing.

Alternatives you've considered

Using an alternative product.

No real workaround apart from finding somewhere safe to stop (not always possible on highways in Japan) and forcing the App to recalculate using the offline maps which it thinks are "outdated" for some reason.

Context

OsmAnd 4.8.6 on Android 13 using offline maps for Japan.

---

Also, semi-relatedly, when GPS signal is lost, OsmAnd often "jumps" to a location nearly 6000km away. I don't know if this is the default for OsmAnd, or the phone's / Android's location service. Again, this should not happen, ideally the location should be interpolated based on the last known velocity and time until signal is regained, or the location should stay on the last known good location if the new location reported by Android is patently absurd (middle of the ocean thousands of kilometers away)

---

Thanks to all the developers for an overall amazing product!

[dmpr0]

Hi! Could you please provide example route?

[Guylby]

For the loss of routing at the end of tunnels this may be related to #20485
I've also experienced this loss of routing numerous times with the deviation of itinerary of more than 5000kms when gps signal is reconnected after exiting tunnels

[mwerle]

Hi! Could you please provide example route?

So it happened again, tonight, roughly in the circled area, while I was guiding a friend home (we were on two motorcycles with an intercom, her first time riding and didn't have her own navigation solution yet). No loss of signal as far as I could tell, no tunnels. Just in-between glancing at my phone, the route was suddenly gone. At an incredibly inopportune moment as the sharp left-hander there is to avoid going the wrong way into a one-way section of road. As I was late directing her and she was overwhelmed with everything she actually entered the one-way section. The destination was still selected.

This time there was no option to ignore old maps - I had to completely dismiss the route, re-select the destination, and have OsmAnd recalculate the route.

Here's the planned route:

And here's the track, the point of interest is around 21:21:10:
20241012-211040.zip

This is starting to be a big issue. OsmAnd also, for some unfathomable reason, wanted me to download a russian map.. as I was on the bike I did not note down the exact region it wanted.

Again, please note that I use OsmAnd completely offline; I occasionally update the maps when at home, but generally just use it offline. I don't recall this issue a year or so ago, this is a fairly recent occurrence.

[yuriiurshuliak]

We've implemented fixes for it. Please try using our nightly build and let us know if the problem persists: https://osmand.net/docs/versions/nightly_versions#nightly-builds

[vshcherb]

Reason that routing stopped is not directly clear cause it shouldn't behave like that. Routing doesn't check outdated maps, it checks inconsistent maps. If you managed to start routing initially, recalculation should work same way. The issue might be with jumping GPS signal however in your file I didn't find anything strange.
We will simulate with your track to see what's going on

[yuriiurshuliak]

Unfortunately, I am unable to import your file 20241012-211040.zip, as the application shows an error when attempting to open it. Could you please check the file and provide it again?

OsmAnd~ 4.9.0#3527m, released: 2024-10-23

[mwerle]

Unfortunately, I am unable to import your file 20241012-211040.zip, as the application shows an error when attempting to open it. Could you please check the file and provide it again?

I just downloaded it, extracted it, and could open it with "Viking" and "GpxSee" applications.

I'm not sure what's wrong with it that you can't open it? There are some extensions at the beginning of the file, maybe your application doesn't ignore those? I deleted the extensions, can you try the following?

20241012-211040 (1).zip