Messages

Hello Menion,

once again on this topic. I had some time to look into it over the weekend and found some inconsistencies and, in my opinion, a bug.

First of all, thanks for the update 4.15.2 (impoved computation of uphill/downhill distance) - this is more realistic now.

I am still not completely happy with the new calculation of the elevations. In my opinion, ignoring elevation differences of up to 5 metres is too strict. In relatively flat regions such as Berlin and the surrounding area, too many actually existing inclines and declines are calculated out, and the result is then not very realistic. If I go on a cycling or jogging tour and have several short but distinctive inclines, which clearly require effort when running and can also be seen in the altitude graph, and the result then shows 0 metres of altitude, this is not ideal. 

In addition, there are sometimes strange results that make no sense from a purely mathematical point of view: A recorded track shows "Min altitude" 30 m, "Max. altitude" 66 m (a difference of 36 m), but only 30 m elevation gain is displayed. (Screenshot 1 and 2.) So 6 metres of altitude are "swallowed".

Then I noticed a faulty behaviour in the Track Analyzer, which might be a bug. A track section selected with the analyzer always shows exactly the same value for elevation gain and loss, even if it only goes uphill or downhill (screenshot 3 and 4). This can be reproduced everywhere.

(it's not even possible to multi-select and delete trackpoints!)

... or to embed multiple waypoints into a track at once.

I would like to add Management of Track Waypoints as No. 5.

Yes, please don't forget about this. There's a bunch of improvements needed here, many very basic (it's not even possible to multi-select and delete trackpoints!)

Thank you Menion.

I would like to add Management of Track Waypoints as No. 5.

As for now, when I plan my hiking trips, I use embedded waypoints, so that the track file is able to be sent to my trekking partner as a complete KML file. These embedded waypoints can't be managed properly. I would like to be able to search for them, display them in a certain radius around the cursor etc.

So my workaround is saving every embedded waypoint twice – within the track and as a "standalone" version in my points folder. This is more work for me, but also raises problems, like when I edit a point in the points folder, it doesn't change in the corresponding track and vice versa.

A second thing would be the improvement of data sharing (e.g. via shared folder).

Best, Lucas

Hi guys, nice bunch of ideas, thanks. So when I noted and analyzed all, seems that we have here four major categories

• better work with online/offline LoPoints
• robust search system
• dashboard improvements
• geocaching features

Where
2. search system is currently (already for a few months) in massive rework. During the next week or two will be in Beta a completely new online search. More about it later ...

LoPoints & Dashboard are very high on my priority list, so definitely something I would like to work on this year.

And geocaching ... good question. Will have to think a little more.

---

Other smaller tasks
- backup system: agree, I'll look at it soon
- 3D maps: huge amount of work that still does not worth it I believe
- recording statistics: I would love to see them too, but we are not the majority
- live tracking: I know, sorry @joeloc. This has to start with a rework of our old server and uniting it to a new web.locusmap.app site. I'll try to push it a little more.

Anything else serious?

The Lopoints system of temporary points. Awkward handling, allow predefine sets of categories etc.

Hi, ah I see. It is a problem on our server that does not send Gold subs item in case, user does not have enough LoCoins, we will fix it, thanks.

The system of backups needs to recreate.... I need to find a time (week or rather too)...

If you work on it please add no-go area,too.

The system of backups needs to recreate. I wrote about it a few days ago (again). So use it as is. I need to find a time (week or rather too) and unite "settings" + "full" backups into a single system with options ...

maybe we need backup-presets.. just need to drop this joke

(sure, backup 'settings only' should to be closer to 'full' but without \data\database as some configurations are missing)

@Andrew, I guess Menion messed something up last time. Yes we discussed it, Menion added stuff I suggested (brouter profiles) to the full backup, but accidentally? removed from the config only backup.
How check? Look into the backup zip in <see path in screenshot, Android 10>. Screenshot: data folder inside of zip.

I have general questions:

a) Any difference to the available OAM Mapsforge V5 maps?
b) When will they be in the store?
c) Are they still exclusively used for e. g. retrieving the city name (for track naming)?

I noticed having more *.db of the same area (one is from asamm, the other from OAM) is not ideal. When I display Lopints Offline via the "Map-screen content" it displays many points twice because of the two databases.

Hi,

by the end of March I will need a new subscription and my LoCoins stack up. I know "Payment via Locoins" has been worked on, but I do not find anything related in the software. So, will it be possible? How?

thx

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.

Yes, I agree, but everyone uses his device as he sees fit, in my case:
I start recording with Locus and only use the phone to take pictures or at crossroads when I have to choose which way to go, so during any excursion Locus is only active for a few minutes.
I prefer to turn it on for a few seconds and thanks to the high contrast of the icons I can see all the details even in full light, changing these settings in my case would be worse.
The copyright symbol could be less shiny (it's only there as a requirement) and that wouldn't be a problem, but the other icons the way I use them shouldn't be changed.

In addition, the displays have timers that first reduce the brightness and then turn off the display to avoid this type of problem, just set a timer that suits your needs.

Perhaps the problem arises for those who use Locus as a navigator in the car and want to leave it always active. If this is the problem, it would be useful to tie the brightness of the icons to a profile for example for use in the car.

[by length and not by distance?]

May I remind you guys kindly about OPs question? 😁

"Is it possible to sort search results of tracks by length and not by distance?"

I think it would be great if we could sort search results, by everything that makes sense. (Length of track, Name, Creation time, Distance from map center etc etc)

I was a bit unclear. Results of course were sorted, but user cannot apply another kind of sorting.