Closed scaidermern closed 8 years ago
I've got the same issue with and without gpx navigation. I also tested with and without the native library and I still get the issue.
To reproduce on the version from the play store (2.3.5 2016-04-28):
You should get this:
I noted that when going through this roundabout from a different street or going to a different street, I do not get the issue. I also checked the roundabout definition in OSM and it seems ok (I'm not familiar with OSM) (https://www.openstreetmap.org/#map=19/48.74635/-3.46617)
In "shortest route" mode, the problem does not occur on this roundabout.
I have observed this issue in real life during a trip in Sweden. Complete roundabout is one issue. Another is leaving the autoway rounding a roundabout next to the road and the continue on the autoway. (80km /h road).
Another i met is leaving the autoway entering a small village and leave the village on the other side to enter the same autoway again there. (Note the detour was considerable longer then the router on the autoway, and 40Km/h in vilages).
Fast route is enabled, as well as avoid softroads toll-roads and ferries. I think i saw a message once that native was not usable on my phone.
Another is leaving the autoway rounding a roundabout next to the road and the continue on the autoway. (80km /h road).
Another i met is leaving the autoway entering a small village and leave the village on the other side to enter the same autoway again there. (Note the detour was considerable longer then the router on the autoway, and 40Km/h in vilages).
These are separate issues and belong into a separate bug report. If possible include examples for these routes.
Fixed
I couldn't find the right words for the title but the screenshot says it all:
This can be reproduced (using the latest nightly 2.4.0#12934D, probably also using the stable version):
Now OsmAnd should calculate the route shown in the screenshots.
Note that this does only occur when trying to use the GPX track for navigation. Regular navigation doesn't produce this error:
Also note that the mentioned GPX track does not pass this roundabout. OsmAnd produces this strange route while trying to navigate to the GPX track.