You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Show along the route" feature, which is expected to display only POIs within a specified distance from the route. However, POIs are appearing everywhere on the map, regardless of their proximity to the route.
We have reproduced the bug using the following steps:
Open the OsmAnd app and select a car profile.
Build a navigation route but do not start it.
Go to Menu → Navigation → Settings → Show along the route and enable it.
Select a POI category (e.g., Cafes and restaurants) and set a distance limit (e.g., 100m).
Start navigation and zoom out on the map.
Actual result: POIs appear everywhere on the map, instead of only near the route. Expected result: POIs should be displayed only within the selected distance from the route.
We had it in the past, and it turns to be not practical.
Then we switched to display different style for POIs and it made only confusing. So show along the route is affecting widgets and list in the widget but not the map itself.
Anyway documentation needs to be updated if it's states different.
Description
When activating POIs along the route (https://osmand.net/docs/user/navigation/guidance/map-during-navigation#show-points-along-the-route) it is expected that only POIs are shown which are near the route, depending on the distance chosen by the user. Instead, POIs are shown everywhere on the map, even if they are far away from the route.
Steps to reproduce
Start a navigation and enable "Show along the route" for POIs (https://osmand.net/docs/user/navigation/guidance/map-during-navigation#show-points-along-the-route).
Actual result
The selected POIs are shown everywhere on the map. I've selected the POI category "Cafe and restaurant" and a distance of 50 m.
Expected result
The selected POIs are only shown when located close to the route.
Your Environment (required)
The text was updated successfully, but these errors were encountered: