Important links
- blog post (http://www.locusmap.eu/news-version-3-44-0) about major version
- list of news (https://help.locusmap.eu/announcement/version-3-44-20-2-2020) of public versions
Versions
20. 2. 2020 - Locus 3.44.0
Quote from: Tom on February 20, 2020, 20:37:20
Hi Menion,
since I installed the beta 3.44.0RC3 my hardware buttons no longer work (in both the beta and the pro version). I guess that it is related to the move of the settings from the config file to the expert settings. I understand that the pro version can not work any longer, because the related section from the config file was removed. But the beta version should have the correct settings. At least I can see my hardware key definitions there (e.g. 46|96 for map center). However the key code 96 is not accepted. Any idea?
BR Tom
Hi Tom,
I've tried to move your topic to new post, but no success so at least added as "quote" above.
Suggest to check settings > Controlling > Map screen > Use hardware controllers ... is this enabled?
Quote from: menion on February 21, 2020, 15:47:34
Suggest to check settings > Controlling > Map screen > Use hardware controllers ... is this enabled?
You are right. In my beta the Use hardware controllers was disabled. So, the beta is working now again. Thanks for the hint.
It is no longer possible to have 4 function buttons in the top panel in Pro or Beta. Not sure how long ago this changed. settings > Controlling > Panels > Set function panels: 3 items in Top Panel list. Now drag item (button) from Right Panel list up to Top Panel list. Drag is refused & item is returned to Right Panel list. For me this means less effective use of the top panel. I guess in V4 this panel will be gone anyway which is a shame for view-only/ less commonly tapped items.
@Andrew Heard
in the recent version is a smaller change in the size of buttons that has an effect > there is not enough space for 4 buttons on your device. Anyway, this change will be reverted in the next bug-fix version.
Many problems with the current version 3.44.0
When I display points from a folder on the map and switch on the live map at the same time, when I click on a point, it no longer shows me which one of them is stored in the folder and which one affects the live map.
When importing a cache, it no longer shows me how many points are already stored in the folder when I select a folder.
If I have logged a cache, Locus will exit when I click the Back button.
Translated with www.DeepL.com/Translator (free version)
Quote from: menion on February 24, 2020, 13:02:38
@Andrew Heard
there is not enough space for 4 buttons on your device
@menion - thanks - there was/ is enough space! You can see from my screen capture I used to have 5 buttons across the top. For me function button(s) are a better use of this space than the info panel.
@flyingman_ch
thanks very much for reported bugs. The problem with a missing number of items in folders will be fixed in the next version (this week).
Unfortunately, I'm unable to simulate this "If I have logged a cache, Locus will exit when I click the Back button." problem. Does it happen with every cache you log? Immediately after you confirm the log?
@Andrew Heard
you will see in the next version if the change I made today helps. Anyway, you may agree that it looks really weird when you completely "covered" info panel with buttons :). Fortunately for you, in LM4 this won't happen :).
two new problems since the last update
1. from time to time the path to the vector maps which are on the external SD is missing. >screenshot
The last selected map is displayed, but map or theme change is not possible.
restarting the device solves the problem.
2. backup files of the automatic backup have a different size e.g.110 MB to 126 MB
The smaller file does not offer all restore functions and does not work > screenshot
Dunno if that's new in 3.44.0, but I can't add waypoints to existing tracks in my database any more. When clicking the "+" button I get the input dialog, but after "Save" (or is it "OK"?), nothing happened, the list of waypoints is still empty. Tried with several tracks, doesn't seem to be related to something specific.
@balloni55
these are really interesting problems. I'm quite sure, they are not related to the recent version, but just by accident, both appeared now. Quite complicated to solve without knowing how to simulate it. I'll be more carefully watching this.
Both are somehow related to work with the file-system, which is something I have to start work on as soon as possible (because of some breaking changes that unfortunately comes with Android 11 this year).
@slarti76
thanks, I got it. Bug-fix version is just in preparation ....
Thx for the update. Lovely toolbar size is back :).
Excessive word wrapping in cities, see attachment. Idk if it is because of VolUK theme or Locus. Edit: after a Locus restart not happening any more, weird. I think I have seen that behaviour some time ago.
@tapio There's nothing in the Voluntary themes that controls text splitting. I too have seen this behaviour some time ago and it appears to be something in MF4 rendering. MF4 does have the ability to split long text across multiple lines but it doesn't seem to happen in Locus, except very occasionally and usually incorrectly.
See https://forum.locusmap.eu/index.php?topic=6679.msg57254.msg#57254
Decreasing icons in the latest version has led to an unexpected phenomenon. Instead of the three icons in the top row, I now have four. See scr. Personally, it suits me, just take it for information.
Themes window while using "OpenAndroMap V4"
- 3 icons are grayed
- two of them are duplicates of Elevate and Elements
it is not possible to delete these duplicates after long click on this grayed icon
And for me, I found the Elevate theme greyed out when I switched to a v3 LoMap. Selecting it gave an orange toast error. However long tap allowed me to delete the ghost theme.
Sent from my moto g(6) plus using Tapatalk
Quote from: balloni55 on February 28, 2020, 07:34:29
Themes window while using "OpenAndroMap V4"
- 3 icons are grayed
..
Realised that too.
But this is due to a change of the theme-zips, where Tobias (delveloper of Elevate-theme) 'missed' to include Elements.png and Elevate.png, which have to be next to the .xmls in order to let Locus take them, guess so.
I had a look: happens first with Elevate 4.3.3.1 of 2019-09-30 - I am currently using the Elevate 4.4RC, same here.
Copy both pictures from Elevate4_Locus 4.3.2 of 2019-07-08 next to the .xmls and the pictures are shown 8)
Let us inform Tobias soon if he should not be here around..
Regarding my report, "Elevate" should not have appeared with v3 LoMaps as it is a v4 theme. The v3 theme, "Elevate LE" appears, correctly.
Sent from my moto g(6) plus using Tapatalk
Quote from: T-mo on February 28, 2020, 11:44:23
Quote from: balloni55 on February 28, 2020, 07:34:29
Themes window while using "OpenAndroMap V4"
- 3 icons are grayed
..
Copy both pictures from Elevate4_Locus 4.3.2 of 2019-07-08 next to the .xmls and the pictures are shown 8)
Thanks, now the icons are visible :)
@menion
the other problem remains, I still can't delete themes
Quote@flyingman_ch
thanks very much for reported bugs. The problem with a missing number of items in folders will be fixed in the next version (this week).
Unfortunately, I'm unable to simulate this "If I have logged a cache, Locus will exit when I click the Back button." problem. Does it happen with every cache you log? Immediately after you confirm the log?
Thanks, all ok.
Quote from: menion on February 26, 2020, 10:42:44
@slarti76
thanks, I got it. Bug-fix version is just in preparation ....
Confirmed, thx!
@balloni55
can't simulate problem with themes (all looks ok on my device and no greyed themes) so if you zip me whole "mapsVector/_themes" directory, it will be perfect, thanks!
Hello menion
problem with grayed icon is solved after i´ve copied icon.png to theme as described by @T-mo in #16
it was/is missing in theme download from OAM.
problem for now:
I still can't delete any theme by long click on "theme icon" > delete > delete, window loading apeare, end after a few seconds but theme is furthermore avilable :-[
Thanks. No problem with a deletion on my side, so it won't be a problem with themes itself, but more a problem with the access of the Locus Map to your filesystem.
You most probably have a themes on the SD card thanks to the definition of "mapsVector" directory in the app settings right? May you just check if this directory is valid and maybe set it again in the settings before I did deeper into this issue? Thanks.
Quote from: menion on March 02, 2020, 13:26:30
You most probably have a themes on the SD card thanks to the definition of "mapsVector" directory in the app settings right?
exactly
QuoteMay you just check if this directory is valid
i think so, it´s possible for me to change themes as well as maps.
Quoteand maybe set it again in the settings
i´ve done it twice with no improvement
one thing that struck me:
when I rebuilt the path to ext SD/Lomap, after a restart all themes were available immediately, the maps were not available and I had to add them with the + button
Add them by "+" so as an "External maps" directly in "Map manager" screen? Hmm, this should not happen. If you correctly defined path to "mapsVector" directory in app settings and this directory really contains maps, then they have to be added automatically after the restart (or "refresh" done in map manager), definitely no not manually.
I've just tested it on the fresh install on SGS7, "mapsVector" set to SD card (/storage/xxxx-xxxx/LocusEx/mapsVector) and map and theme downloaded from OpenAndroMaps web correctly and also map was immediately available for usage. Weird.
Menion, if I import a GPX file with no name tag inside, Locus names the track with a number (here: 1584169770280). Maybe a unix timestamp. Is that new behaviour? I think, and I prefer, it used the filename without extension before. I already name the gpx files reasonably with date/time, so I'd love to use those.
Hello tapio,
just testing it and the app behave like this already. Share with me please one problematic file for test, thanks.
see attached - Locus Pro 3.44 @ startup - whole tile of map not displayed until I panned around quite a bit. I think it was an OpenAndroMap rather than LoMap. Fortunately I haven't seen this behavior before or since, but I thought I'd mention it.
Quote from: menion on March 17, 2020, 10:33:55just testing it and the app behave like this already. Share with me please one problematic file for test, thanks.
Attached a file here, cannot send attachment to you via pm. File is from GPSLogger Android App.
In the icon selection dialog, there it's possible to order the icons into section with a special file in the ZIP. I know that because I once redid the icon collection in the store (Menion, perhaps you remember).
Today I noticed that the sections are still there, but the section titles are gone. Don't know since when, but definitely in 3.44.2. Is there a reason or is that a bug?
Another thing, which I still think is a bug:
In the store, when I choose "Check for Updates", it will show me for which maps there are updates. However, this is only based on whether I bought the updates, not if my maps are up-to-date.
I have several phones, so when there are new LoMaps out, on one phone it will show me the updates. Then I buy the updates and download them, but on the other phones "Check for updates" doesn't show them anymore. Yes, I bought them now, but the maps on those phones are not updated, so I think they should be displayed there, too.
long click on "preset icon" in side panel / information > window appears "purchase locus...."
although PRO is running
@Andrew Heard
probably some problems with the auto-loading of maps.
@tapio
if you tap on the menu > more > import, then this imported file (track) has an incorrect name? May you please double-check it? Because I see no problem on my side, thanks.
@slarti76
missing section: hmm good observation. It seems to be a problem not directly in my code. I'll have to do something with it, thanks.
"Check for updates problem" may be a little more complicated. I'll discuss this with @Petr if we have something to do here.
@balloni55
ah, thanks :)
Quote from: menion on March 22, 2020, 09:53:16
@Andrew Heard
probably some problems with the auto-loading of maps.
Oh speaking of which... I see the opposite effect. I often have several OAM maps that *could* be chosen for the selected area - eg current and older for "home" - and Locus often decides to show both at the same time. Green areas get darker (rendered twice), trails get doubled if they've been edited between the versions. Manually selecting the map I want makes the other one go away.
I don't have an exact recipe to trigger this, but it's not uncommon.
I think this is a known issue if you have Automatic map loading turned on for offline vector maps. (Settings - Maps - Offline maps - LoMaps & other vector maps).
Sent from my moto g(6) plus using Tapatalk
Quote from: john_percy on March 22, 2020, 18:33:31
I think this is a known issue if you have Automatic map loading turned on for offline vector maps. (Settings - Maps - Offline maps - LoMaps & other vector maps).
thanks @john_percy - I had that setting enabled. The problem has only occurred once so unlikely to know if fixed.
Menion indeed, the file imports correctly, need to look closer, sorry.
Hello menion
inside folder of locus auto backup sometime .temp files are stored, i suspect they remain on a unsuccessful backup
Thanks balloni, you are correct, these are results of some failed backups. I've added it to "Backup improvements" todo list, thanks.
EDIT: To avoid redundant investigation, you may want to skip to findings in post #50.
------
The Route planner in the PRO Release 3.44.3 is reporting a straight line stats in spite of the route segment being calculated by the BRouter. I do not remember such a behaviour before.
I tried to calculate a cycle route Brno (S Moravia ) to Feldbach ( SE Austria ) by one of my profiles.
When I had calculated the route within the Locus route planner ( no intermediate via/shape points ), it reported distance 252 km and ascend above 8000 m, what seemed to be statistics of the straight line across all mountains and valleys along the line. ( screenshot )
When the route had been calculated directly via BRouter as an aftercheck, it reported the direct distance about 252 km, the true route distance about 350 km and the filtered ascend ( via 10m hysteresis filter ) cca 1100 m ( used to be cca 1/2 of the unfiltered ascend usually reported by Locus ).
But, when I saved the route calculated in the planner and displayed the saved route statistics, it provided the correct and expected about 350 km distance and about 2000 m total ascend. ( screenshot )
The same happened when I had formally divided route into several segments by converting few guidance points into shape points.
The route planner may easily confuse users during the planning.
Sorry for dark images, taken in reddish subzero night mode vision.
(https://uploads.tapatalk-cdn.com/20200327/d239c0040b6395a8e971c76b3b24bcf4.jpg)(https://uploads.tapatalk-cdn.com/20200327/8811f1b114dca7c544adc01ab004f819.jpg)
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
What is interesting, that the shorter route, very familiar to me, along car road 373 from the eastern part of Brno to the north to the village Benešov ( near Boskovice town ) , with help of few shape points, is evaluated correctly, some 48 km and about 900m.
But when I returned to re-evaluating the affected route Brno Feldbach, It was wrong again.
Similarly for Vienna-Feldbach. It has shown just about 4500 m, comparing to previous 8400m for Brno-Feldbach ( like If there had been huge mountains between Brno and Vienna, haha. It is a flat region ). When I moved start little to the west along Donau, the planner returned the ascend 9500m, as straight line goes through higher mountains there.
Few shape points little prolonged the straight line distance, and little decreased the crazy ascend, but not much.
All with Trekking-dry profile. Just reminding calculation directly in Brouter application provides proper distances and ascends, so do the statistics when the route is saved ( with expected 2:1 exception of Locus/BRouter ascends ). And finally, the Route planner draws the real BRouter route, not a straight line.
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Route planner, add green waypoints, save route, exit route planner. Tap this new track, enter route planner, no green waypoint there, it has not always been like this?
@tapio I did so as you described and the green shaping triangle points are still there, as usually. ( not related to stats issue).
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Same here, but there must be conditions where it forgets those points, see attachment. Only 2 points left on a complex track.
You may be right.
Similarly as there must be conditions when the route planner calculate stats properly as the route, and when just as a straight bee-line.
Perhaps is it related after all.
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Got it. When I change the profile setting while in planning mode, then it only saves start and ending green point.
EDIT. Hmmm. No, may also be the use of specific profiles. It loves to forget my points...
EDIT2: No. I have no clue why it happens.
I have tried not to touch navigation settings at all after launching the planner, but the same bee-line stats for Austria as before.
Perhaps it got itself infected in AT.
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Quote from: poutnikl on March 27, 2020, 02:05:03
The Route planner in the PRO Release 3.44.3 is reporting a straight line stats in spite of the route segment being calculated by the BRouter. I do not remember such a behaviour before.
@poutnikl - from my testing in Australia, all appears OK.
It seems I am tracking the stats issue down..
I was playing with the planner, having set the start and setting/unsetting the shaping point in various directions and distances.
I have noticed that at the moment I set the shaping point, it often, but not always, immediately displays straight line statistics bar when the route computation begins. But it seems does not affect the issue occurance, that happen in both cases.
But I have also realized, that for the particular direction and distance, the issue REPRODUCIBLY occurs above a critical straight distance, but does not occur below a critical distance.
For short enough segments, the stats reproducibly displays ( or updates itself to ) the true route stats.
For long enough segments, the stats reproducibly display ( or remain ) the straight line stats.
The critical straight distance value varies for my device and region typically between 70-90 km, so it may be related rather to the route computation time. For sparse road network it may be more.
If I add a short segment after the segment with wrong stats, it correctly updates the 1st segment partial stats for the totals. So e.g if I add 10 km long segment after (straight ) 100 km segment with wrong stats, the total distance stats may jump by e.g. 40 km.
So the work around is, after adding a long route segment, add ( and remove if not needed) a short segment to be sure stats are OK.
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Libor, thanks for the investigation. You are correct, I've found one parameter that has an influence on this and that caused, that tracks above around 100km were not correctly refreshed after the calculation is done. Thanks for the big help in discovering reason for this and sorry for extra work.
I'm glad I could help. :-)
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Quote from: menion on March 22, 2020, 09:53:16
@slarti76
missing section: hmm good observation. It seems to be a problem not directly in my code. I'll have to do something with it, thanks.
Confirmed working in latest beta.Just a tiny thing: At the bottom, a section "Various" is always shown, even if there are no icons. As far as i remember, this section, this was for icons that didn't have their own section.
I am not sure, but I have thought LocusMap Pro currently supports in-profile switches in external original (Arndt ) Brouter car-fast/eco profiles.
It does supports switches of Locus internal car profiles ( I guess my obsolete ones ), and my external bike profiles,
but does not support new kinematic BRouter car profiles.
Unless I have broken something, playing with the last alpha of LM4.
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
I must say the route planner seems to be seriously broken. I created a track with it. Just entered it, did not change the routing profile, added those green points, saved. Then tapped the saved track, "Route planner", see screenshot. Only 2 points. I use the latest beta.
Navigation with Via points problems
I did a bike roundtrip around a lake today. Locus 3.44.3 (beta not installed on that phone). I wanted to use Locus navigation, so at the starting point, I opened navigation, chose 3 via points to get me nicely around the lake, started navigation. Route looked good, but only for a few seconds, then suddenly it was only a few meters from here to the destination point. Obviously Locus recalculated and forgot the via points!
I checked the settings, got "Point priority" turned on.
Next I tried to plan the route in the Route Planner first, saved it, right-clicked on it and chose "Navigation". Same behaviour: Looks good for a few seconds, then Locus recalculated and the route was gone.
Another thing that happened during the trip:
Several times Locus just suddenly paused my recording! I couldn't see any obvious reason for it. Granted, another app was in foreground, but I did this many times before and never was a problem. Battery saving is off for Locus (and anyway, Locus was still running, just the recording paused).
Only thing that was different is that navigation was running, too (usually, when navigating, I have Locus in foreground). Perhaps a recalculation caused Locus to paused recording?
Edit: Additional Question:
Is there a way to, after starting the navigation, get to the list of via points again? Or start a new navigation with the same via points? I might be overlooking something, or that is part of the navigation improvements planned for LM4?
There is important to point out, that shaping points ( green triangles ) are not considered as viapoints ( blue squares ) in context of point priority route recalculation. Or, alternatively, they may be considered as non mandatory 2nd class viapoints.
Shaping points serve for tweaking the route between the true mandatory viapoints ( including the implicit viapoint destination ), but play no role in navigation along the route nor in route recalculation.
If route recalculation is manually or automatically triggered and if point priority route recalculation is set, then Locus Map calculates the route to next viapoint or to destination, if no next intermediate viapoint is set.
If destination happens to be just next to the start for round trips, and if no viapoint is set, just shaping points, then route recalculation by design finds just trivial shortcut route to destination, completely ignoring shaping points. Therefore, a round trip combined with point priority and shaping points is not the best idea.
If viapoints are set instead of some or all shaping points ( manually converted from shaping point, or set so automatically by planner settings ), then recalculation modifies route just toward the nearest viapoint or destination.
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
@slarti76
"Various" label > ah, thanks, fixed
Navigation problems:
- what you describe in the first paragraph: Locus works correctly.
"Point priority" search for next defined "Via point", which most probably was your destination. To have real via-points, you need a "blue rectangle" in route planner ( https://docs.locusmap.eu/doku.php?id=manual:user_guide:tracks:planning#add_via_points ).
For the round trips, I highly recommend "Route priority", that tries to stick you on the planned route.
EDIT: ah, just correctly commented by @pountikl, thanks!
Paused track recording
Never ever happen to me, do not know. Anyway Locus itself definitely does nothing like this. Isn't there any tasker you use for example that may do this? In case of any battery optimization when the system kill Locus completely, navigation will stop.
Additional question:
If you planned route in Route planner, you may simply open Route planner over specific route > context menu > Route planner. If you use "Navigate to" function, then exactly what you need is not possible, good point.
@poutnikl
not sure what exactly is a problem. In Locus BRouter settings screen is at the top, switch that change between internal profiles (yes, your older profiles or some user-defined) and profiles included in the BRouter itself.
@tapio
I'm playing with restoring previously planner route and for me, it works correctly. Are you able to create a short video (nice tool (https://play.google.com/store/apps/details?id=com.hecorat.screenrecorder.free) for this). Thanks.
@0709
good testing conditions with a vine :D
Sorry for missing something.
In version history I saw the point "Map content panel available in the Route planner". This sounds like a feature I missed some times.
I see no changes in Route planner and no option to enable/extend something which might be such a feature.
What does this mean?
Ah, sorry, this is news for Locus Map 4, not for the regular version.
EDIT: back, it's correctly only in LM4 Alpha version, isn't it? There should be a small icon directly above the centering button in the route planner.
Quote from: menion on April 05, 2020, 11:10:52
@poutnikl
not sure what exactly is a problem. In Locus BRouter settings screen is at the top, switch that change between internal profiles (yes, your older profiles or some user-defined) and profiles included in the BRouter itself.
Hm, strange. I have the switch ON all them time, having the available profile list divided into Locus and BRouter profile sections.
Whenever I choose Locus Car-Fast/Car-Eco profiles, the profile switches are there . Whenever I choose the Brouter profiles,they disappear. And I remember they worked once. It is not due the same name, as if I mod them under different name, the result is the same.
They currently use this:
# Use the following switches to change behaviour
assign avoid_toll = false # %avoid_toll% | Avoid paid roads | boolean
assign avoid_unpaved = false # %avoid_unpaved% | Avoid unpaved roads, if possible | boolean
assign avoid_motorways = false # %avoid_motorways% | Avoid motorways | boolean
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
So you have the switch turned off, you see at top title "BRouter profiles" and you expect that checkboxes at the bottom with parameters will be enabled, right?
This worked before? I can't imagine how to be true. With this option, Locus only offer a limited list of routing types where every only defines two parameters that are sent to BRouter service: type (motorcar | bicycle | foot) and "fast" (true | false). Locus Map does not load any routing file directly from the BRouter directory to analyze its content.
ON, not OFF. In fact I never use it OFF as you have shown above. I have attached the screenshot for the picture from Locus profiles (with options), and for the profile from external BRouter profiles ( without).
The issue persists even for EN US Locus+Android language settings. I had previously set the primary language in LocusMap PRO and in Android as CZ.
(https://uploads.tapatalk-cdn.com/20200405/aa4da73fe1ef4a5404d7b0f843c46d05.jpg)(https://uploads.tapatalk-cdn.com/20200405/0e0f85231075d62e9d9ac276e2d7f60a.jpg)
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Quote from: menion on April 05, 2020, 11:10:52
Navigation problems:
- what you describe in the first paragraph: Locus works correctly.
"Point priority" search for next defined "Via point", which most probably was your destination. To have real via-points, you need a "blue rectangle" in route planner ( https://docs.locusmap.eu/doku.php?id=manual:user_guide:tracks:planning#add_via_points ).
For the round trips, I highly recommend "Route priority", that tries to stick you on the planned route.
EDIT: ah, just correctly commented by @pountikl, thanks!
Ok, I do get it when I planned the route with the route planner. I will also try to remember to use Route Priority for this usecase next time.
But when I use the Navigation menu and add Via Points?! I mean, that's not intuitive, I'm sure everyone who adds a Via Point in the Navigation dialog expect Locus to always keep this Via Points. I mean, it's just like car navigation: I want to reach my hotel for the night, but on the way visit some sights. I don't want my navigation to skip sights because at some point the hotel is closer than the next sight.
QuotePaused track recording
Never ever happen to me, do not know. Anyway Locus itself definitely does nothing like this. Isn't there any tasker you use for example that may do this? In case of any battery optimization when the system kill Locus completely, navigation will stop.
Yeah, that's what I thought.
Anyway, I have to admit that I'm using Tasker, so it might have been some of my automatics there running wild. I will just keep an eye on it, whether it happens again. For now, ignore me ;)
QuoteAdditional question:
If you planned route in Route planner, you may simply open Route planner over specific route > context menu > Route planner. If you use "Navigate to" function, then exactly what you need is not possible, good point.
Ok, good to know.
Still, just to reiterate: Route Planner was only my desperate alternative attempt, because the Navigation Dialog didn't give me a usable result.
Quote from: slarti76 on April 05, 2020, 17:36:22
But when I use the Navigation menu and add Via Points?! I mean, that's not intuitive, I'm sure everyone who adds a Via Point in the Navigation dialog expect Locus to always keep this Via Points. I mean, it's just like car navigation: I want to reach my hotel for the night, but on the way visit some sights. I don't want my navigation to skip sights because at some point the hotel is closer than the next sight.
Update: I tried to recreate the problem, and couldn't! I have no idea what went wrong Saturday morning, I definitely tried several times, but now when I start navigation with Via Points, all is fine!
So, please just ignore me ;)
Ok, I'll just ask that one question again:
Is there a way to get up the list of Via Point used for the Navigation again or, once it started, they're gone? Thx and sorry for that...
@poutnikl
Ah, I probably finally understand. On my device, Locus Map no longer offers BRouter profiles, because BRouter directory is not in the root of internal memory.
So the last thing, may you please share here your profile from the BRouter directory that does not work as expected? To be sure we talk about same file. I'll check it, thanks.
It is possible, there is any new problem because I've added support for a few more parameters and also changed how these parameters are saved.
Btw. no feedback from anyone on this: now, every profile has own value for parameters, they are not shared across all of them. There was a discussion a long time ago about this, and I finally feel, that this may be more useful, mainly because more and more parameters come into play.
@slart76
as I wrote before: agree. Points defined in "Navigate to" as via-points, should be really considered as "via-points". I'll look at it.
EDIT: hmm based on the code, they should be used as regular via-points and also based on my sofa-testing, it works, interesting.
@menion
The car routing profiles are attached.
My BRouter data folder is on the internal memory root.(A10, internal storage only )
I am using Brouter version 1.6.1 from https://brouter.de/brouter/revisions.html
but currently on Google Play as well.
Be aware of 2 API versions of BRouter APK files in the zip package. API10 file is original fully functional API version, not allowed on Google Play anymore. The other, API28, has restricted access to Locus or OSMAnd favourites and has to be used via BRouter API only. As it does not affect average users, it is fine, but I like playing with standalone mode as well, so I use API10 version.
My external bicycle profiles work fine, using iswet and avoid_unpaved switches.
Here are the files...http://cloud.tapatalk.com/s/5e8adfe8e8081/car-eco.brf (http://cloud.tapatalk.com/s/5e8adfe8e8081/car-eco.brf)
http://cloud.tapatalk.com/s/5e8adff460339/car-fast.brf (http://cloud.tapatalk.com/s/5e8adff460339/car-fast.brf)
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
@menion @poutnikl
For me, using api10 version, latest Locus Pro and Locus alpha, and "main" brouter profiles downloaded from GitHub https://github.com/poutnikl/Brouter-profiles/releases I find the car profiles give the same 3 options as Locus built in profiles (highways, tolls, unpaved) but bike and foot don't give the"wet" option. Apparently quite the reverse of poutnikl's experience!
(I cleared my profiles2 folder before re-uploading the profiles.)
I assumed that in the new version of Locus there will be a similar profile setup option as in BRouterweb.
@john_percy
do the switches work for you for the attached brouter-dry profile ?
( screenshot in Czech localisation, but it works for me for EN as well )http://cloud.tapatalk.com/s/5e8b299544e58/Trekking-dry.brf (http://cloud.tapatalk.com/s/5e8b299544e58/Trekking-dry.brf)(https://uploads.tapatalk-cdn.com/20200406/bf5acef7520bbfa879f2b8f9ca66ec71.jpg)
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
@poutnikl
No options at all for me with that profile on either Locus Pro or alpha.
Quote from: john_percy on April 06, 2020, 15:42:45
@poutnikl
No options at all for me with that profile on either Locus Pro or alpha.
It is not clear to me from your previous post, if you tested car profiles from BRouter package or from my GitHub page ( which I consider obsoleted for cars, recommending BRouter profiles ).
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Quote from: john_percy on April 06, 2020, 12:49:23
@menion @poutnikl
... "main" brouter profiles downloaded from GitHub https://github.com/poutnikl/Brouter-profiles/releases ...
I used the profiles from "main" folder. These are presumably the ones you say are outdated.
Sent from my moto g(6) plus using Tapatalk
All 3 switches are present for me for my old car profiles, like in then my favourite Car-FastEco-Tollfree from 2017, in both last Pro and LM alpha.
( It had defaulted to no toll in case switches were not available )
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Quote from: menion on April 05, 2020, 11:10:52@tapio
I'm playing with restoring previously planner route and for me, it works correctly. Are you able to create a short video
I already created two, but of course it worked fine at that moment. Still a mystery to me.
Quote from: menion on April 06, 2020, 08:22:52
Btw. no feedback from anyone on this: now, every profile has own value for parameters, they are not shared across all of them. There was a discussion a long time ago about this, and I finally feel, that this may be more useful, mainly because more and more parameters come into play.
Definitely a reasonable change! As different profiles can have different sets of parameters, saving the settings globally makes no sense (anymore).
Quote from: poutnikl on April 07, 2020, 07:23:54
All 3 switches are present for me for my old car profiles, like in then my favourite Car-FastEco-Tollfree from 2017, in both last Pro and LM alpha.
( It had defaulted to no toll in case switches were not available )
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
The old car profiles have the Locus switches set to "0" whereas the new Brouter package has "false". That makes the difference.
Edit: Also, apologies, on retrying the "trekking dry" profile that @poutnikl uploaded a day or two ago, I _do_ get the two options. I don't know what I did wrong before.
Edit 2: ... But the profile doesn't work with Brouter 1.6.1 - orange toast complains about remote.brf.
@0709
I think we had discussion about "the first point as via", right? I'm not sure if this is a good idea, because it may block you like "strict" navigation on the first point.
---
Ah "0" vs "false", nice :). Currently, only 0/1 is supported. I think it may be improved, thanks.
I confirm the new Arndt's car profiles do have switches present if the switch defaults within the profile are changed from false to 0.
In fact I did know it, noticing this issue earlier, when I was playing with generating car variants from Arndt's profiles, or combining my dry/wet bicycle profile variants into a single profile via my Linux/bash script on Android/termux.
But I have completely forgot about that.
There were originally available just 0/1 values for BRouter profile logical expressions. True/false values were implemented later and are currently preferred in newer profiles for explicit clarity. So it would definitely good to support them.
Note that uploaded Trekking-dry does work on BRouter 1.6.1, I use it all the time, exactly the copy I have provided.
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
@poutnikl
After exhaustive tests I've discovered that I lost the line endings on your trekking-dry profile. Corrected that, navigation now works!
Quote from: john_percy on April 08, 2020, 20:13:01After exhaustive tests I've discovered that I lost the line endings on your trekking-dry profile. Corrected that, navigation now works!
What did you correct? If there's some kind of trouble maker in that code, I am interested in it. Because many of my profiles are derivates of Poutnikls.
EDIT, ah, that true/false 1/0 thing? Indeed, my profiles are full of true/false.
@poutnikl
When I tried to download from your link direct to my phone I got the profile displayed in a browser window. I selected all, copied and pasted into a blank document. That lost all the line endings.
After uninstalling and reinstalling Brouter and Locus I downloaded the profile again (correctly this time) and it worked.
Problems with BRouter profiles (0 vs false) should be fixed in recent Beta published on Google Play (or also in Locus Map 4 Alpha).
Thanks for true/false update.
Should Google Play still offer to update LM beta/free even if I have uninstalled it a week or 2 ago and installed LM4 alpha(as I understood these cannot stay together )?
I once did not pay attention, confirmed update and the LM free/beta overwrote the LM4 alpha.
I understand LM4 will be a successor of LM free and LM Classic of the LM pro. But, would not it better for alpha e.g. to have higher version number for the GP not to try to overwrite it ?
Or, have I explicitly unsubscribe from LM beta tester program ?
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
It is a little complicated and not always united (version numbers).
Anyway, I've just today published firstly Locus Map Free Beta on the Google Play and then Locus Map 4 Alpha here on the forum (so it has all fixes/changes of Beta as well).
Both versions have now the same version number, so if you installed LM4 Alpha, Beta should not overwrite it.
In the Alpha, in route planner, track length is always shown correctly. In stable, always the length of a straight line is reported. So that is fixed? Just recognised it... Brouter profiles are in data/brouter, in both stable and alpha.
It was fixed for LM4 alpha and LM3 beta. Stable LM3 free/pro have the bug yet, in my understanding.
Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Size of arrows in "guide to" line are smaler/with other geometry since last?? update
With LM4 they lock as usual
Setting in both cases are 200pix
@balloni55
Isn't it better now? :). What you see in LM Pro is incorrect result of too-long usage of Locus Map where some parameters incorrectly scaled. I've also moved the setup of the shape of this arrow into Expert settings, so you may modify it (even back to your LM Pro style, I may help with it).
QuoteI've also moved the setup of the shape of this arrow into Expert settings, so you may modify it
thanks, i´ll wait for the next update
another small issue
settings window of geocoded photos
Menion, you added the option for default POI icons. Should this maybe affect waypoints which are embedded in GPX? Locus picks a black dot as an icon... This is the waypoint format in my imported gpxes:
<wpt lat="51.00066" lon="7.00079"><ele>39</ele><time>2020-04-13T06:09:05Z</time><name><![CDATA[Stop: City]]></name><desc><![CDATA[2020-04-13 08:09:28 MESZ]]></desc></wpt>
@balloni55
hmm German language ... :). Thanks, I'll look at it.
@tapio
these last two comments (Willy and I) should be interesting for you.
> https://help.locusmap.eu/topic/configurable-default-waypoint-icon#comment-82640
Time for new version? Sure! Thanks guys ;)
(btw. balloni, the problem in geocoding photos is in my todo list)
Quote from: balloni55 on April 11, 2020, 12:58:37
Quote
another small issue
settings window of geocoded photos
solved with V3.45.1 thanks