Terribly wrong time estimation after re-calculation of route when following a GPX

[mdykierek]

Description

When riding a bike along preloaded track the route sometimes gets recalculated. The reported remaining distance is correct, but the time is completely off. e.g. for 30 km ride says 2 minutes.

Steps to reproduce

1. Load a GPX track
2. Follow more or less accurately the route
3. Listen to voice prompts or watch the ETA on screen (will add a screenshot next time I catch it).

Actual result

Wrong ETA.

Expected result

Somewhat correct remaining time reported.

Your Environment

OsmAnd Version: Osmand+ 4.4.7 Android/iOS version: Android 11 Device model: Mi 9T Pro

[DmitryAlexei]

Do you use Attach to the roads option? After attaching your track to the roads (choose bicycle profile), you will get more precise information about your route, including ETA. This is especially important when using for cycling the track recorded in a car profile.

For better result, you can also enter your average speed in the default speeds section of the navigation settings.

[mdykierek]

I'll check suggested options. However, 30 km in 2 minutes is like 900 km/hour so I don't think I can make it on a bicycle. The speed settings I have are Min=5, Default=10, Max=33. I will nail it. The most common scenario for me as of now is "draw" a track on brouter.de, import, ride, get lost ;), get back on track. When getting back on track, I get these 1 minute, 8 minutes on long distances.

[Zirochkabila]

@mdykierek Have you checked the behavior with the latest OsmAnd updates?

[mdykierek]

I tend to be exact when filling the reports. All the data is there. As far as I know the currently available "customer" version is 4.4.7 and this is what I use and wrote in the bug. Not trying a non-production version. Happened to me with both live updated (Silesia, Poland) and regular offline (Zilina, Slovakia) on latest maps at the moment of occurrence. Allow a couple of days and I will give a screenshots + info on the options recommended by DmitryAlexei.

[mdykierek]

Here are the screens. 13 km in less than a minute ~800 km/h. The trigger this time was ~100 m shortcut due to some excess bushes and tall grass I had to avoid. ETA on map view is gone.

[Zirochkabila]

@mdykierek I can't reproduce it - have you checked the ETA on a track created with OsmAnd? Perhaps it's the track you're using - please send it to us to check. You can upgrade to 4.5.1 from 30.05.2023 version

[mdykierek]

Here are the tracks. I think there are at least 2 different on-line tools the tracks experience the same behavior. The one that screens come from starts and ends in Ruda Śląska. I do not see 4.5.1 on Google Play. I don't see it on osmand.net downloads either. gpx1.zip gpx2.zip Even if the root cause is in both tracks, it doesn't seem right to report under 1 minute for 13 km. I recall another bug for car profile I reported for certain place in Finland. I'll try to find it. And #15062 it is.

[Zirochkabila]

@mdykierek Version 4.5.2 is available in the Play Store for beta testers. Version 4.5.3 will be available within two days Version 4.5.0 is the nightly version and can be downloaded here https://osmand.net/docs/versions/nightly_versions I checked again, on the night version for 19.06 - the route and time are calculated correctly. You need to attach the track to the road.

https://github.com/osmandapp/OsmAnd/assets/104760013/349d7770-2cd5-4f27-b84d-b87d251d1562

[mdykierek]

1. I'll check it when RTM is in Play Store. Using OsmAnd way too often to get into new Beta trouble.
2. The ETA usually is OK at the beginning. It breaks under way, when route gets re-calculated. When riding off-road (MTB, forests etc), the attach to road seems to give weird results, will try it more and provide details.
3. Yesterday went a track made with OsmAnd and maaaan it was weird. It was as bad as it gets. It was announcing waypoints mixed with destination e.g. in 200m you will pass waypoint, then in 50 m you will reach your destination and all this was at 2nd and 3rd waypoint of like 8. I'll try it more and report if intermittent.

[euphi]

I remember that I also had this issue, but did't noticed it in the last weeks (using > 4.1.x versions). (But also volume was low most of the time and I had a look at the ETA not that often).

Before, I was wondering about strange (way too fast) ETA announcements, too. It only happened when following an imported GPX track. One hypothesis was that the bugs happens, if you are off track and osmand calculates a route back to track. The announced time then is the time to be back on track, not the time to arrive at the track's destination.

However, I never verified this hypothesis.