Navigation from recorded/imported file

As the name suggests, I'm a 95% hiker.

I use both Locus Map 4 Gold and Komoot.

I'm very satisfied with Locus because of its many (sometimes too many) settings and other features.

Komoot is a kind of “Facebook “ for hikers : Photo’s, comments, likes…...and simple.

Over the past few years, I've recorded (With Locus and Komoot ) and saved many hikes to hike again in a different season or in the opposite direction.

After trying out various hikes, I've concluded that Komoot navigates much better (especially verbally) than Locus Map. Komoot provides more detailed and varied commands, such as "at the next junction, turn left, right," "follow this road for 120 meters," "at the next opportunity, turn left, turn right." Locus usually just says, "after xx... m, left or right."

I mainly hike in the woods where there are many paths.

With Locus, I often have to look at the screen, but with Komoot, much less.

In fact, Komoot can even navigate a track recorded with Locus Map better than Locus Map itself. I have presented this problem (!) twice to Locus.

The answer:

Locus Map can navigate accurately only planned routes because it knows from the map where the intersections are. When it navigates a recorded track, it knows only the track line - in this case, Locus Map generates the navigation commands according to the track's shape - where the track turns right, Locus Map adds a command "turn right", and it doesn't matter if there is an intersection or not. When the track goes straight, even across an intersection, Locus Map adds nothing because it doesn't see it.

I replanned a walk ( same as I recorded before with the Locus app on the phone ) with the webplanner, and the navigation commands where indeed much better.

Buth of course, I don't intend to plan every walk again with the Locus web planner.

Reply to the second email:

As I mentioned before, navigating a recorded track is always less accurate because Locus Map renders the navigation commands according to the shape of the track line, not according to the intersections. The recorded track doesn't contain information about intersections. The intersections are included in the routing data from which planned routes are generated. Therefore, voice navigation is always more accurate with planned routes.

Komoot offers an option to snap a recorded track to routing data and thus "replan" the route in the background, which adds navigation commands to the right places. In Locus Map, we are still waiting for this solution. You can vote for it: https://help.locusmap.eu/topic/navigation-from-track.

So if I understand correctly, the strength of Komoot navigation is that it recalculates the route during navigation of any track (recorded or imported), making navigation much more accurate.

Locus Map should also be able to do this if it wants to be a full-fledged navigation app.

Feedback is appreciated.