This object is in archive!
Route Navigation Car Mode
Solved
As a cyclist I like to get GPX routes from various places on the web, which I happily follow using the RFLKT Addon.
However, Locus always starts the navigation in "Car Mode" (German Voice, don't know if this is the actual translation).
Today, I nearly ended on the Autobahn (freeway), which would suck big time.
Locus wouldn't want to navigate me over the bike-only paths that where present in the GPX.
It would be really great if I can select what transportation mode the navigation system should use, prior to setting off, similar to what you can already do when computing A->B type instructions.
For completeness, I use BRouter for my offline navigation.
Thanks!
The same problem 
Good day Jens,
it was quite a while since I wrote this part of code, so I wasn't sure. Sorry for confusion - currently, if "type of compute" (car, bike, ...) is not defined in track, like in your case when track was imported from plain GPX file, Locus always use "Car - fast" mode!
Currently there is no workaround. I was thinking quite a long time about it. I have something in my mind, but it may take a long till it will be realized. So I was looking for some alternative and not so complicated solution.
Best I was able to do for now, is small symbol on "recalculate" icon, that show current type that will be used for recalculation
And new option on this button - "long click" to display option where you may choose how you want to recalculate a track
It is not yet perfect, mainly because long click on a bike may be sometimes a problem, but at least we have now a working solution to choose, how to recompute a tracks no matter of it's source.
Believe it will works fine.
Thanks for "kick" I needed to make this feature happen and let me know if it works fine for you. Next version is planned on Monday/Tuesday of next week.
Good day Jens,
it was quite a while since I wrote this part of code, so I wasn't sure. Sorry for confusion - currently, if "type of compute" (car, bike, ...) is not defined in track, like in your case when track was imported from plain GPX file, Locus always use "Car - fast" mode!
Currently there is no workaround. I was thinking quite a long time about it. I have something in my mind, but it may take a long till it will be realized. So I was looking for some alternative and not so complicated solution.
Best I was able to do for now, is small symbol on "recalculate" icon, that show current type that will be used for recalculation
And new option on this button - "long click" to display option where you may choose how you want to recalculate a track
It is not yet perfect, mainly because long click on a bike may be sometimes a problem, but at least we have now a working solution to choose, how to recompute a tracks no matter of it's source.
Believe it will works fine.
Thanks for "kick" I needed to make this feature happen and let me know if it works fine for you. Next version is planned on Monday/Tuesday of next week.
Good day Jens,
even if you hear something about "car" from Locus after start, internally there are no such "car mode" for now. It just mean, that imported GPX file do not have defined type of navigation so Locus say "car", nothing more. Fact that Locus navigated you on freeway means, that you imported GPX, started navigation along it, but keep enabled "auto-recalculate" so Locus probably took last point of imported track and last used navigation mode (car) and computed track for it. Main problem I see here is this auto-recalculation, which should be disabled for such cases. Otherwise it makes no sense to import and use any GPX, it should be then enough, just to pick a target point and start "Navigate to", result will be same.
So my suggest: for navigation along imported GPX tracks, do not forget to turn of "auto-recalculate" and you will be fine.
We have a plan to create some navigation profiles, so it should be then possible to define how Locus should recalculate track (if as "car-fast, bike-fast, etc.), but it is not possible for now.
Hope this helps you.
Good day Jens,
even if you hear something about "car" from Locus after start, internally there are no such "car mode" for now. It just mean, that imported GPX file do not have defined type of navigation so Locus say "car", nothing more. Fact that Locus navigated you on freeway means, that you imported GPX, started navigation along it, but keep enabled "auto-recalculate" so Locus probably took last point of imported track and last used navigation mode (car) and computed track for it. Main problem I see here is this auto-recalculation, which should be disabled for such cases. Otherwise it makes no sense to import and use any GPX, it should be then enough, just to pick a target point and start "Navigate to", result will be same.
So my suggest: for navigation along imported GPX tracks, do not forget to turn of "auto-recalculate" and you will be fine.
We have a plan to create some navigation profiles, so it should be then possible to define how Locus should recalculate track (if as "car-fast, bike-fast, etc.), but it is not possible for now.
Hope this helps you.
Hi,
this auto-recalculation is sth. I really value, e.g. when taking a detour and getting back onto the original route.
I just wish I could set the profile used for recalculation.
If I understood correctly this is something you plan?
And regarding your guess that locus used the last navigation mode. I rarely(never) use car mode, so is this just a guess or can I set the the mode specifically as a workaround?
Thx.
Hi,
this auto-recalculation is sth. I really value, e.g. when taking a detour and getting back onto the original route.
I just wish I could set the profile used for recalculation.
If I understood correctly this is something you plan?
And regarding your guess that locus used the last navigation mode. I rarely(never) use car mode, so is this just a guess or can I set the the mode specifically as a workaround?
Thx.
Good day Jens,
it was quite a while since I wrote this part of code, so I wasn't sure. Sorry for confusion - currently, if "type of compute" (car, bike, ...) is not defined in track, like in your case when track was imported from plain GPX file, Locus always use "Car - fast" mode!
Currently there is no workaround. I was thinking quite a long time about it. I have something in my mind, but it may take a long till it will be realized. So I was looking for some alternative and not so complicated solution.
Best I was able to do for now, is small symbol on "recalculate" icon, that show current type that will be used for recalculation
And new option on this button - "long click" to display option where you may choose how you want to recalculate a track
It is not yet perfect, mainly because long click on a bike may be sometimes a problem, but at least we have now a working solution to choose, how to recompute a tracks no matter of it's source.
Believe it will works fine.
Thanks for "kick" I needed to make this feature happen and let me know if it works fine for you. Next version is planned on Monday/Tuesday of next week.
Good day Jens,
it was quite a while since I wrote this part of code, so I wasn't sure. Sorry for confusion - currently, if "type of compute" (car, bike, ...) is not defined in track, like in your case when track was imported from plain GPX file, Locus always use "Car - fast" mode!
Currently there is no workaround. I was thinking quite a long time about it. I have something in my mind, but it may take a long till it will be realized. So I was looking for some alternative and not so complicated solution.
Best I was able to do for now, is small symbol on "recalculate" icon, that show current type that will be used for recalculation
And new option on this button - "long click" to display option where you may choose how you want to recalculate a track
It is not yet perfect, mainly because long click on a bike may be sometimes a problem, but at least we have now a working solution to choose, how to recompute a tracks no matter of it's source.
Believe it will works fine.
Thanks for "kick" I needed to make this feature happen and let me know if it works fine for you. Next version is planned on Monday/Tuesday of next week.
Replies have been locked on this page!