Messages

Sorry for the objection, but your problem is not one. If Youtube shows you advertising, it has nothing to do with Locus.
And you don't have to click on the link. I have never even noticed the video, although I have often downloaded articles from the Locus store.

Inzwischen habe ich mich mal genauer mit den Presets befasst und ja, hier scheinen diese tatsächlich hilfreich zu sein. Die Möglichkeiten waren mir in der umfassenden Form bisher nicht bekannt.

Habe eins für OAM angelegt mit dem passend eingestellten Elevate Theme und ein zweites für LoMaps mit dem gewünschten internen Theme. Damit ist der schnelle Kartenwechsel inkl. Thenenwechsel möglich. Mal sehen, ob sich das so im Alltag bewährt.

Danke für eure Anregung diesbzgl.!

@ Gerhard: For me, the number of points was also not correct at first. After I have switched off all (with the new brush icon) and then have shown again several points, the number is now correct for me.

For me, the new solution is fine so far. The "brush" icon is clear enough.

Temporarily hidden tracks or points can always be recognised by the red icon at the top right of the map and can be shown there.

Very interesting! I came across this discussion by chance only a week ago.

I myself had noticed only a few weeks ago that Locus suddenly caused very high battery consumption, always when navigation and/or track recording was running. On day trips, a power bank had to be connected after only 3-4 hours.

Now we were hiking in the Liberec area (Czech Republic) for about 2 weeks. Very beautiful area by the way! Every day with track navigation along planned routes and track recording. Strangely enough, there were days when the battery lasted through the day without any problems, but on other days it was already empty after a few hours.

After reading this discussion I remembered that in March I had downloaded the 1" files of the elevation data (24.7 MB each) for the whole of Germany from Sonny, which coincides with the beginning of the high battery consumption.

These were not available for the Czech Republic, where I still have the small 3" files (2.7 MB). 

Now the region west of Liberec is still covered by the Sonny file N50E14.hgt, while those from the city and further east are covered by the 3" file N50E15.hgt. And indeed, it was the tours in the west (Ještěd Mountains, etc.) where the battery consumption was extremely high. In the eastern Jizera Mountains, the battery lasted the whole day.

I would never have thought that this could be the cause without these posts on the forum. I then replaced all the 1" files with the small 3" files and the battery consumption was normal again. Even with another hike in the N50E14 range. 😊


Translated with www.DeepL.com/Translator (free version)

...
What does this value do? It specifies a minimal change in the altitude when computing elevation up/down sums.
...

I find this new feature quite interesting. Whereas "minimal change in the altitude" is relative - moving the slider by a few metres can result in significant differences in elevation up/down sums.

I have tried a lower value (3 m) for tracks in flatter terrain and a higher value (5 m or more) in mountainous terrain - but in the end the function shows well how difficult the calculation of realistic elevation gain/loss is. Good solution to put the function in the Expert Settings. Thanks for the update!

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.

With the latest update to 4.13.2, the manual backup works again. And without rd5 files.
Thank you and Merry Christmas!

After updating to 4.13.1, a complete backup is no longer possible. See here.

Since the last update (4.13.1), the automatic backup no longer works. Backup is not created.

The manual backup (option 1: "Back up all") does not work. The orange message "Process unsuccessfull" appears.

Only the manual backup (option 2: "Back up settings only") works.

Currently, there is no possibility to create a complete backup. This is bad.

[Blog]

The last update (LM4) brought a change in the backup management. The backup zip files are now 4-5 times as large as before, which is due to the fact that now also the segments with the rd5 files are zipped.

User Niklas had already noted this in the Blog (entry 10.12.2022).

As a result, I now have backup files of about 1 GB in size, which significantly increases the upload time and unnecessarily takes up disk space. The rd5 segments do not need to be secured in my opinion.

I would therefore welcome to take them out of the backup again. If some users absolutely want to backup these segments as well, please do so as a selectable option.

Thanks.

Bei mir hat die Kalorienberechnung in Locus noch nie gepasst. Vor langer Zeit hatte ich das auch mal angefragt, aber da es mir aber nicht so wichtig ist, nicht weiter verfolgt.

Es gibt unzählige Onlinerechner im Netz, die bei Eingabe von Geschlecht, Gewicht, Streckenlänge und Zeit alle mehr oder weniger ähnliche realistische Werte ermitteln.

Bei Locus hingegen bekomme ich immer viel zu geringe Werte angezeigt, meist nur um die 50 bis 70 % des realistischen Verbrauchs (beim Joggen). Egal, es gibt wichtigeres.

Also ich kann auf der Karte einen Track anklicken, dann öffnen sich das Info-Fenster dazu. Darunter (ganz unten) sind in der grauen Leiste mehrere Werkzeugicons. Das zweite von rechts (Stiftsymbol) ermöglicht das Editieren und auch die Auswahl des Ordners. LM4

...
OK, we're renaming it to "Edit track". It is more generic than "repair" or "fine-tune" and the tool in which it is done is called "Track editor". Hopefully this will suit the majority.

I agree, "Edit track" for me is a better discription of this function.

I don't understand why "Routenplaner" was replaced by "Route neuberechnen."
For me this describes a function in navigation, but here it is no recalculation but a modification of an existing track.
Suggestion: Route ändern / editieren / modifizieren... Or rename it "Routenplaner" like it was before.

Ist ein Bug. Habe ich an anderer Stelle schon bemängelt und auch im helpdesk gemeldet.
Soll mit dem nächsten Update behoben werden.