-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Attach to the roads" ignores waypoints #20126
Comments
The bug was not reproduced. To reproduce the issue, import the provided GPX file, attach it to the road, and set the threshold distance to 10 meters. Then, attempt to build the navigation. This should result in waypoints being considered in the navigation process without skipping any track sections. Please try updating the app or check out our beta version using this link: OsmAnd Nightly and Beta Builds. OsmAnd~ 4.8.0#2533m, released: 2024-06-19 |
Thanks! I don't understand what you mean by first attaching to the road and then building the navigation. After attaching to the road, the navigation is ready, and the Start button appears. I've already tested on the latest stable release, perhaps this is fixed in the beta. |
OK. Fresh reinstall of OsmAnd 4.8, the only difference I see is Attach to the roads seems to be faster. |
Think I've figured it out. There is an option between starting from the closest waypoint or the first, and this is reset after attaching to the roads. But it seems I can just readjust it after without affecting the result. Thank you for your help! |
Description
Hi! On an imported GPX file, after selecting "Attach to the roads", it simply ignores many waypoints.
Things that don't help:
Sample:
Steps to reproduce
Use "Attach to the roads" on an imported GPX route route.gpx.txt, on a fresh install of OsmAnd+.
Actual result
Many waypoints that were being correctly routed in the GPX track are now ignored.
Expected result
Only attach to the roads, without removing any of the roads included in the GPX file.
Your Environment (required)
The text was updated successfully, but these errors were encountered: