Navigation Offline
I use Locus Map pro a few months for track recording and it works fine.
With navigation there are some problems.
Navigating a track works well when looking on the screen but while I walk mostly between 7 - 8 hours ( 40 km)
it is impossible to keep the screen on ( battery).
Also I live on the border between Belguim and the Netherlands and I go many times in other countries, so I avoid
being online ( via data and roaming) on all the time.
Now I want to use Locus as guidance of recorded or imported (gpx) tracks only by audio and offline.
So I installed Brouter ,put the navigation data source in the settings of Locus on " BRouter" and downloaded the right tiles of the map.
Now the problem :
On the screen no problem.
Verbally: even when the road turns slightly left or right the app says : turn left or right (even there is no crossing or junction). On a real junction or crossing of roads the app says nothing if I have to go straight on ( shows right on: that is ok ).
So it is difficult to determine verbally if it is a false turn( no crossing) or a real turn that I have to take( crossing of roads).
Is this improvable so I can navigate 100% only by voice ??
Some other questions:
1) Is there a difference ( in navigation ) in maps downloaded from Locus or other sources.
2) Is there a difference ( in navigation ) in recorded tracks with Locus or recorded with other sources ( Garmin devices or imported from sites of friends ?)
3) What is the best way to navigate : On or Offline.
I hope anyone can solve this problem.
The same question
Hi Rene,
if you are navigated along a pre-prepared route imported from somewhere or drawn by yourself, all navigating voice commands are generated by Locus based on the route direction changes. Locus can't read maps, it can only read the GPX line that doesn't contain information about intersections - only direction of the route.
If you want to be informed about intersections no matter if you are changing direction on them, use the BRouter and "Navigate to" feature - it generates both the route and voice commands because it works with a database of route network connected by nods, intersections, not just a line.
Hi Rene,
if you are navigated along a pre-prepared route imported from somewhere or drawn by yourself, all navigating voice commands are generated by Locus based on the route direction changes. Locus can't read maps, it can only read the GPX line that doesn't contain information about intersections - only direction of the route.
If you want to be informed about intersections no matter if you are changing direction on them, use the BRouter and "Navigate to" feature - it generates both the route and voice commands because it works with a database of route network connected by nods, intersections, not just a line.
Ah sorry, I forgot the other questions:
1) Locus doesn't navigate by maps - navigation works through routing engines that work with routing data, NOT MAPS. Routing data (network of nods created by intersections connected by roads of various priority and properties) can vary from maps and various routing engines can work with different routing datasets. Even those routers working with the same datasets can calculate different routes because they are differently programmed. Locus can work with BRouter, Graphhopper (both offline), MapQuest, Yours and OSRM (online)
2) navigation along recorded tracks(routes) from Locus and other sources is the same as Locus is the application that generates the navigation commands - according to the shape of the route as has been mentioned in the previous post
3) it depends on your preferences. In a car I prefer offline BRouter so as not to waste my FUP. On bike I use guidance along my own planned (drawn) routes which are always offline.
Ah sorry, I forgot the other questions:
1) Locus doesn't navigate by maps - navigation works through routing engines that work with routing data, NOT MAPS. Routing data (network of nods created by intersections connected by roads of various priority and properties) can vary from maps and various routing engines can work with different routing datasets. Even those routers working with the same datasets can calculate different routes because they are differently programmed. Locus can work with BRouter, Graphhopper (both offline), MapQuest, Yours and OSRM (online)
2) navigation along recorded tracks(routes) from Locus and other sources is the same as Locus is the application that generates the navigation commands - according to the shape of the route as has been mentioned in the previous post
3) it depends on your preferences. In a car I prefer offline BRouter so as not to waste my FUP. On bike I use guidance along my own planned (drawn) routes which are always offline.
Replies have been locked on this page!