No-Go

Improving No-go Areas: Route Independence, Navigation Recalculation and Map-Based CreationI tested the No-go feature in Locus Map and found three issues that limit its usefulness when cycling.

1. No-go areas should not be tied exclusively to a single routeCurrently, when I add a No-go area during navigation, it appears to be associated with the active route. This is a significant limitation.

For example, if I discover a broken bridge or a closed forest road, I want the No-go area to remain on the map independently of the currently active route, similar to how No-go areas work in BRouter.

This would allow me to reuse the information when planning or navigating other routes.

A No-go area should be able to remain active indefinitely or expire on a date specified by the user. This would support both permanent restrictions and temporary obstacles.

2. Starting navigation should check the route against active No-go areasWhen I stop navigation and start it again, Locus does not automatically recalculate the route to account for an active No-go area.

It would be useful if Locus checked the route against all currently active No-go areas when navigation starts. If the route passes through one of these areas, Locus should offer to recalculate the route or do so automatically, according to the user's settings.

This would be particularly useful when resuming a ride after a break or restarting navigation later. Users should not have to remember to trigger route recalculation manually to account for a previously marked obstacle.

3. No-go areas should be addable directly from the map, without active navigationCurrently, it appears that adding a No-go area requires an active navigation session.

However, I may discover a closed road while browsing the map, planning a future ride, or reviewing a route without starting navigation.

It should be possible to mark a location as No-go directly on the map, set the transport mode, radius and optional expiration date, and then use that restriction when planning or navigating future routes.

Expected outcomeNo-go areas should function as independent map restrictions rather than objects tied exclusively to a particular route or navigation session.

They should be available when planning different routes, and starting navigation should take all currently active restrictions into account.

This would make the feature significantly more useful for cyclists dealing with obstacles such as broken bridges, flooded roads, fallen trees and impassable trails.

Thank you for considering these suggestions.
waldek