Messages

auto-pause system, so consider it as a "Beta" feature that simply needs some testing and time ...

I haven't tested further; it wasn't working reliably or at all, so will need more that just testing & time. Is there some visual indication when auto-pause is active? This would help in any further testing.

@menion - although certainly not thorough or extensive testing yet, but the changes you have made for xDOP filtering for vertical accuracy in track recording has resulted in improvements for me. It is hard to be sure of course, but I mostly take my phone inside with track recording still enabled as a small test, and mostly I don't see huge errors in vertical position anymore. So thanks!

John, maybe I'm too quick - the Voluntary Locus.zip\Voluntary\changelog.txt latest "Recent Changes Dec 2021" - I don't see any more recent changes?

GPS points deviate somewhere inside a 10m radius, speed between 0 and 1km/h, nothing unusual IMO.

@Tapio sometimes hugely more if poor GPS signal and/or at startup

There's some papers out there, Locus would IMO benefit from movement detection

there is at least 1 popular help topic (many votes) for using movement detection using internal accelerometer but I can't find it. @menion has said a few times it is the best way to fix this situation.

Hm, interesting... Maybe Menion can simulate the issue?

@luce FWIW my settings:

• bottom function panel: partial auto-hide
• side function panel: auto-hide
• panel hiding timeout: 99,999

In 4.11.1.3, the side panel can't be displayed any more by double clicking (setting = hide automatically)

@luce - it's still working for me

I had forgotten Locus Map Web allows charting the GPS Accuracy. When I view the accuracy of latest reported walk/ sit inside building vs. time, it is (now) quite clear where the inaccuracy is - nice feature. In addition to xDOP there could be hysteresis rather than a fixed threshold i.e. record (as now) once a desired accuracy is reached/ disable once a worse threshold is crossed, and only reenable once a better threshold is crossed.

https://web.locusmap.app/en/?shared_track=NzY4ZjAxMDUtOTFmZi00MjY1LTkzMzMtNzA4OTY4NWRmODlhOjg1MjU5MWYyLTUxNTAtNGFjMS05N2NmLTYxNWVlNjk2NjMyZQ..
You cannot view this attachment.

Also as mentioned in a few posts a few weeks ago - auto-start of track recording is problematic if the GPS vertical position is not yet accurate, for example when the GPS is first enabled. Attached is an even more dramatic example than the previous post. Unless you manually edit the track & delete a few initial points, the elevation chart is useless.

I reported this bug a long time ago - on a large map download the progress bar may get stuck @ "99% | 1 items remains". You can wait as long as you like but it never got to 100% complete until I closed the Notification Centre panel then opened it again. It probably only happens rarely.

you probably find only 0.01% of users use Presets, so far bigger fish to fry; maybe there are analytics behind the scenes to justify development in certain areas

Andrew Why do you think so? I think Locus Presets needs. Without them I can not even imagine using locus.

@Žajdlík Josef - LM4 5M+ downloads, LM3 probably even more, but just a few regular beta users in this forum. I agree with you Presets are a great power-user feature but it would be interesting to see how many out of 10M+ Locus users are aware of & use this feature. I'm just trying to say with limited developer resources there are possibly more important areas to develop that would give more bang-for-your-buck for more users.

In this review of 6 best navigation apps for bicycle touring https://wobblyride.com/2022/03/29/best-navigation-apps-for-bicycle-touring/ sadly IMHO Locus is not mentioned. I have experimented with all other 6 apps (long time ago) and settled on LM as the best. I would suggest every LM user who reads the review, adds a comment to promote LM and provide wider exposure.

Indeed but my needs are just simpler. It's hard to touch the right button while riding.
For me a placeholder which does nothing, just to separate the active ones would be helpful.

@CabrioTourer - indeed x 2 - I've have similar ideas in multiple help topics over years (including dummy "placeholder" button) but not enough votes. Although more work (for @Menion), being able to space out buttons in a custom dashboard (including Zoom buttons) would give you ultimate user-control of placement. Thinking further ahead, these custom dashboards may even be shared via Cloud Sync, and templates available from the Locus store.

@menion - regards 4.10.0.9 beta

• "support for com.mg.raintoday" - how to test?
• "improved own icon in Live tracking" - see 1st attached - icon is painted before the track so mostly hidden; I recall months back suggesting icon is painted over track for better visibility & you agreed? maybe
• bottom saved track info panel - top of 2-row track name is truncated; may be a recent issue - see 2nd attached; I don't recall this happening before

just in case any of you beta users missed this comment from @menion https://help.locusmap.eu/topic/28029-v4-gui-improvement-by-offering-more-freedom-of-panel-placement#comment-115823 (29th June, currently 2nd to last comment in thread) just imagine the possibilities of laying out all your own buttons & other GUI objects on a fully custom dashboard - wouldn't that be awesome

The dark compass button was really a problem with the current red rose. Because of this, I've left it white for now.

@menion - no worries, unlike Zoom buttons, I don't have any strong feeling with compass button

No one has commented on the change of Zoom button color in 4.10.0.8. I like it - consistent with other buttons & better contrast, but being such a big visual change I'm hoping there isn't a user backlash & reversion to original color scheme

The problem I see is that Locus creates the points just by guessing.

@CabrioTourer - agree; but still better than no points

So with this feauture I have no control where and how many shaping points are created.

agree; Brouter - no control over where, but at least allows you to decide on show many

how could an app make an intelligent decision where to place auto-shaping-points?

Maybe I completely misunderstand the usage of this feauture.

I think you understand correctly, well same as my understanding at least

as @0709 says many times, preserving the shaping points within any exported/ imported GPX would be a worthwhile improvement too