Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - lor74cas

#16
Quote from: balloni55 on May 07, 2023, 19:32:19turn off GPS, so cursor position is used

I hope this is just a workaround, not by design.

When I'm standing in one place but the cursor is at another, my attention is at the other place, and I'd like the search / weather forecast / whatever to be at that location.  Just my opinion.
The following users thanked this post: lor74cas
#17
New online search:
When searching for a POI, e.g. a bank, the online search is sorting the results according to my current location, not according to the cursor's position. This makes it impossible to search something in a distant place.
The following users thanked this post: lor74cas
#18
Quote from: Menion on April 16, 2023, 07:55:48Btw. did anyone notice the "Altitude threshold" parameter in the track edit screen? I'm experimenting with this value. For now, this may be set only for single route. Automatically is used value 5, when using SRTM data it is equal to 3.

comparing elevation gain old / new (LM 4.15.0) method and different "Altitude threshold"
Settings are:
GPS & sensors -> Altitude manager ->
SETTINGS -> Use altitude offset -> ON
SETTINGS -> SRTM data -> Replace GPS values
SETTINGS -> Altitude filter -> light
OFFSET -> Automatic correction

Elevation gain:
km : Distance in km
VDO :  VDO bike computer barometric
SRTM : SRTM /LiDAR by Sonny LM 4.14.2   OLD computation of elevation values
At :   SRTM /LiDAR by Sonny LM 4.15.2.5 NEW computation of elevation values =Attitude threshold
Distance (uphill) and Distance (Downnhill) also changes but no value to compare to

km     VDO  SRTM  At=5  At=2  At=1
31,7   738   771   672   751   790
42,3   843   834   739   905  1019
19,7   515   482   432   491   515
64,8  1253  1191  1043  1191  1283
58,2  1030  1022   885  1038  1190
59,3  1061  1026   919  1050  1133
39,5   633   638   551   650   739
72,0  1425  1424  1292  1460  1542
56,8  1347  1283  1160  1296  1360
32,9   891   884   838   889   931


Neu deivice with pressure sensor
GPS & sensors -> Altitude manager ->
SETTINGS -> Use altitude offset -> OFF
SETTINGS -> Use pressure sensor -> ON
PRESSURE -> Altitunde -> Set manually at start

km    VDO At=5 At=2  At=1
14,8  421  365  403   428
14,8  402  349  397   415

It shoud be posible to set different "Attitude threshold" for different Altitude manager settings:
GPS, SRTM, pressure sensor
The following users thanked this post: lor74cas
#19
Fully agree, Andrew.
For the Web Planner, the cost impact is minimal (not so for the 1" downloads, though), so there is no justification to not use it.
"Consistently" (Web Planner versus App) being "wrong" is not a good idea, I think.
The following users thanked this post: lor74cas
#20
Ireland V1 - excellent timing for me Sonny - thanks! About to cycle tour over there.

If would be great if Locus Web used these DTMs for the route planner, say for Gold level users - certainly a premium feature.
The following users thanked this post: lor74cas
#21
Quote from: freischneider on March 20, 2023, 18:18:15For me it is so that Strava currently always shows more altitude than Locus. Yesterday I had in Locus 905 hm and in Strava 1022. Use the Current Beta
Small differences should already be taken into account. Only unrealistic jumps should be filtered out. E.g. 3 hm within 3 meters.
Here's a good read for a better understanding of why elevation gain calculation can vary drastically - there is no simple truth. It helped me a lot. Eg., "Choosing an elevation threshold" is a very relevant factor.

https://www.gpsvisualizer.com/tutorials/elevation_gain.html

Haha yeah, I only use Sonny's best hgt files. Last year I had to disappoint a friend of mine who proudly walked over a 1050m hill in Schwäbische Alb, which in fact was <1000m. Also a lot of hill elevations in OSM are rather drastically off (>50m at times), source may have been barometric measurement or lack of geoid model, I correct those attributes if I find them. Well, some data are pretty old.
The following users thanked this post: lor74cas
#22
Quote from: lor74cas on March 20, 2023, 16:34:51@lor74cas
...
because with the switch to android 13, I can't place them in the folder.
...

I just tested with x-plore on Android 13: even on EXT SD, this app can write to the private folders of /Android/data.
BTW: 1" alone is not delivering better results per se; only 1" plus LIDAR (Sonny's DTMs) will do.
The following users thanked this post: lor74cas
#23
Thanks for the route. It was a different one in the first post.

Anyway even here is also a clearly visible problem, so thanks. I think I've found one obvious problem (with the incorrect sum of the used distance for computing of the slope) and after the fix, I have these results (screen).

And now tell me ... is it wrong? Because here are the changes registered by the algo:

addElevationToStats, distance: 858.5077, elevation: 5.119999237060547
addElevationToStats, distance: 588.86194, elevation: -5.02999969482422
addElevationToStats, distance: 1270.1581, elevation: 5.179999084472655
addElevationToStats, distance: 411.74136, elevation: 5.209998779296875

It simply displays that after the first 858m, elevation change was finally above +-5m, then -5m after another 588m, etc. In the end, changes are so small, that distance up/down are simply = 0m! And I think it is correct.

App requires at least 2% slope change to be registered for up/down distance. So at least 2 metres change per 100m!

@Michael Bechtold
and here is the problem. I really do not want to have this parameter customizable. The main reason is to have exactly the same algorithm (results) on all three platforms. So track re-computed on the web after sync should be able to get identical results (that does not happen now).

@lor74cas
thanks. But it was worst before I believe  :). You may also find apps that will have a higher values...

The difference 14% is not bad. Anyway best is to get better results of altitude values instead of tuning algorithm that filter these values. So suggest checking the "replace of SRTM data" or "Pressure sensor" values in the Altitude manager.
The following users thanked this post: lor74cas
#24
Time for routing development is coming, I keep notes on this.
Quote from: lor74cas on March 10, 2023, 18:33:06I remember this
https://forum.locusmap.eu/index.php?topic=8235.msg69978#msg69978
2 months and 2 versions ago and still not solved.

I tried the openstreetmap planner and all the possible profiles (Valhalla, OSRM, GraphHopper) they allow passage on the military road while locus does not.

@Radim V
The following users thanked this post: lor74cas
#25
Quote from: joeloc on March 11, 2023, 15:32:02
Quote from: Žajdlík Josef on March 10, 2023, 10:16:41You will also need to improve search. It should work simultaneously in addresses and points.
I completely agree. Locus search is pure usability horror from last century. A proper search is ONE SINGLE TEXT FIELD that simply searches EVERYTHING at once and shows results as they come in.

Making me decide in advance on where I want to search is just wrong on every level imaginable.
Even worse is when I start typing, realize I got the wrong "place" to search in, change it, and the input field is cleared - why's that? Makes no sense and would be easy to fix...
The following users thanked this post: lor74cas
#26
I noticed the online/offline Lopoints are really small. If things are too small, maybe the elderly amongst us forgot their glasses, we can use Zoom Lock.

Shouldn't the Lopoint vector overlays scale according to the zoom lock? In my screenshot, the zoomlock zoom is at 300%.

You cannot view this attachment.
The following users thanked this post: lor74cas
#27
Locus Map / Re: [APP] - version 4.14.+ ( 1/2023 )
February 21, 2023, 12:41:47
Quote from: joeloc on February 21, 2023, 10:05:25@joeloc
Quotehmm nice main menu in display. And what you suggest? With Locus Map 4 you may hide everything except "Copyright" button. But this one will be in the next app version semi-transparent, so at least a little smaller problem.
I don't know a perfect solution... but Locus is responsible for destroying amoled displays for a long time now. It has by definition by far the longest screen on time at the brightest setting of any app. Putting some more thoughts into this is overdue.

Auto hiding the menu bars is obvious... but what about other elements? Like track recording icon? GPS icon? Scale?

Maybe a little transparency for these (80%?) could help, without causing too much usability trouble? A better but more complex solution might be to shift the whole UI around SLIGHTLY by a few pixels every day. Half a millimeter or something is hardly recognizable but will go a long way in protecting displays.

You cannot view this attachment.
I think they are exaggerating a bit here. Why do they always have the screen on ? Normally they are hiking or biking and look at the path. On Locus you look only if you need information. So the screen can stay off 70% of the time.
The following users thanked this post: lor74cas
#28
Hi all, thanks for reporting this problem! There is of course no "tram"=no_go. The reason why this is happening is the less common surface=chipseal tag. (I think there is no significant occurrence of this surface in Europe, not even creators of the original brouter considered it). Also handling of defaults used to be less than ideal in the car profiles. Today I reviewed surface handling in all car profiles (Publicly visible are just 2 profiles). After new tiles are produced, the change will eventually make it to the public environment - after testing internally (By us).   
The following users thanked this post: lor74cas
#29
Locus Map / Re: [APP] - version 4.14.+ ( 1/2023 )
January 27, 2023, 09:53:44
@baegas
to check VDOP value and why it does not refresh, I'll need from you recorded NMEA messages created in the time, the problem was visible. It may be done by enabling NMEA recorded in the Locus Map > settings > GPS & sensors > NMEA recording. Thanks.

@Andrew Heard
problem with the bottom panel > it is a work in progress. We are preparing an updated version of this panel that will hopefully help here.

@lor74cas
Weather is discussed mainly here on the help desk. Two points are solved now. "Yellow", hmm, I do not know. I may delete value by 3, but on the second side, app display 3-hours interval ...

@freischneider
trackpoint view - heh, probably because of two lines caused by the long track name right? :). Hmm, thanks.
The following users thanked this post: lor74cas
#30
Locus Map / Re: [APP] - version 4.14.+ ( 1/2023 )
January 18, 2023, 13:56:43
Hi to all. A little weird winter in most of Europe, not an ideal weather to some out-activity right? I was stuck on some really weird problems in the core of the Locus Map & Android & Gear watches etc. So this new version does not bring too many interesting news. Anyway new weather forecast & support for Garmin Varia radar should be usable additions. Enjoy it and winter as well  ;)
The following users thanked this post: lor74cas