Messages

There is more options on how to improve Presets. I'm still playing in my mind with two
- remember state before applying preset and allow restoring the previous state (already used in the navigation!)
- change the whole concept that you will be always in one active! preset (profile) and will just switch between them

I'm just not sure if I want to spend quite a lot of time with the second option (that I like more) ...

@menion - although I am very happy with existing presets, I think the 2nd option is

• conceptually easier to understand
• so easier to document
• less error prone > less upset users, less support
• has inherent restore-previous-state mechanism

but agree with time involved.

conceptually Vertical Dilution of Precision (VDOP) is well described but after a bit of searching I couldn't find any method of obtaining within Android

I've had a few forum discussions about the initial inaccuracy of vertical elevation over the years i.e. before the phone has had sufficient time to stabilize the GPS (one from 2017). In the attached screen cap the real elevation should remain about 50m +/- 5m but clearly the track recording was started when the vertical accuracy was +/-1500m. Crazy & stupid. It appears the GPGGA NMEA "sentence" has a Horizontal Dilution of Precision field (HDOP) but no Vertical Dilution of Precision that could be used to avoid such silliness. Is there another way the device/ Android/ GPS/ Locus could calculate the accuracy of its vertical elevation & prevent recording until a certain threshold was (optionally) achieved? Sorry @menion, you may have already answered in 2017 but thought this particular chart was quite amusing ;-)

https://web.locusmap.app/en/?loc=55.13538:-001.91726:Capheaton&lat=55.135518&lng=-1.916320&z=16

@Jethro10 I have no answer sorry, only a question for @menion regards your URL query string parameters ?loc and :Capheaton. I've not seen those before. ?loc appears redundant.

https://web.locusmap.app/en/?lat=55.135491&lng=-1.917747&z=16 appears to display an identical map, so am just curious.

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

Not possible, no regex

@tapio - see attached - I haven't tested but regex is mentioned.

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

These paths are 3 meters wide asphalted cycleways. These ways are also shown as cycle network in the velo view but without a way behind it. So i think something must be wrong.

@Saturo confirm what metadata is stored in OpenStreetMap for the cycleway; that is the important detail rather than the physical reality; it is quite easy for any user to update OSM details

Thoughts on the compass needle button? It's still white. I'm undecided.

good point but I'm also undecided

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

changing presets with linked dashboards still works for me in the latest beta

I regularly check my battery consumption. I have track recording every 50m. All other features disabled. Display rarely on, with 6s timeout. Flight mode. Percent reduction approx. 3%/hr with no obvious change between LM3 & 4.

"Fine-tune" terminology. Why? I guess to distinguish from Route Planner. But imo it's a weird choice. After all, it is a track editor. And e. v. I don't expect split/merge under fine-tune.

there was some discussion a few weeks ago, but maybe you missed it?

if you have a built-in pressure sensor/ barometer, this can improve accuracy too; try your tests with a different app but you may likely find the same issues

Hmm.  "Repair" suggests the track is broken or invalid.  May I suggest "Adjust" or "Modify", or even "Fine-tune"?  (I assume "Edit" is already taken by a different function, right?  I haven't looked at the beta.)

@Viajero Perdido - good point - I did actually wonder (worry) whether my route was broken when I first read this new "repair" menu item. I like "Fine-tune" even better, but maybe too long? And "Adjust" or "Modify" could apply equally to the Route Editor? It is rather difficult area to keep everyone happy.