Messages

Ich hatte eigentlich noch nie solche Probleme bei der Neuberechnung und auch keinen Abbruch der Navigation. Das hilft euch jetzt nicht weiter, aber könnte dafür sprechen, dass es nicht unbedingt an Locus liegt.

Ich plane zwar ganz überwiegend meine Touren mit der App, aber auch mit importierten gpx von Rother & Co. oder mit dem Webplaner erstellte Routen kann ich mich nicht an so große Schwierigkeiten erinnern.

Die Einstellungen für Endpunkt-, Strecken- und strikte Streckenpriorität bei der Neuberechnung sind euch sicher bekannt.

Dee große Vorteil von Locus ist ja manchmal auch ein Nachteil: es gibt so viele Einstellungsmöglichkeiten, dass man auch als langjähriger und erfahrener Nutzer nicht alle im Hinterkopf behält oder vollständig durchdringt. Stelle ich bei mir immer wieder mal fest. 🙂

^ Wow - die Infos zur tts-Bearbeitung habe ich jetzt erst so richtig registriert und gleich mal ausprobiert. Jetzt "sagt" Locus endlich "Die Navigation wird gestartet" und nicht "die Zielführung..." (die nutze ich so gut wie nie).
Mit "Träckabweichung" (mit ä) hört es sich ok an, allerdings bevorzuge ich weiterhin die Pieptöne.
"Weiter greadeaus" statt "folge dem Straßenverlauf" gefällt mir auch besser, vor allem zu Fuß.

Mal sehen, wie es sich in der Praxis bewährt. Bei Bedarf kann ich ja weitere Änderungen in der tts vornehmen.

In meinem Verzeichnis:  Android\data\menion.android.locus\files\Locus\data\tts
Finde ich original nur  en_latest.tts !
Ich habe nun auch de.tts dorthin kopiert - muss erst prüfen ob diese Datei dann wirklich benutzt wird.

War bei mir auch so. Die neue de.tts wird aber anscheinend problemlos verwendet. 

There is a problem with the round info arrow pointing to a found LoPoint when moving the map screen.

Easy to reproduce:

Search with the global search any location. City, restaurant, mountain, it doesn't matter.

Select the location from the results list. The map jumps there and the LoPoint icon is displayed (white with a blue border). The info panel for the point also appears at the bottom of the screen. See screenshot 1.

Move this down so that it disappears. The LoPoint icon remains. Correct.

Now move the map until the LoPoint is outside. A round indicator with an arrow and distance to the LoPoint appears at the edge of the screen. Correct. See screenshot 2.

Move the map back to the LoPoint. I would now like to remove the LoPoint icon. I select "clear map screen" and confirm. The LoPoint icon disappears. Perfect.

But: when I now move the map, this round information marker with arrow and distance to the removed LoPoint continues to appear permanently. It is not possible to get rid of it, except by closing and restarting Locus. Somehow the search result seems to remain in the cache.

@balloni:

Start POI Alert (auf deutsch Punktbenachrichtigung). You can find it in the main menu, if it is not already listed there, select it under "All functions". Not in the settings!

There you can now select "Mark as visited" at the bottom of the menu. The 3-dot menu next to the option allows you to list visited points and delete all markers. See screenshots.

- has anyone tried the new "Mark visited" option in the POI Alert? It was made for one small Czech team, but maybe it should be useful not just for them?

I tried it out today. Nice idea, works fine for me:

Visited points are marked with a green dot.

After stopping POI Alert the markers are gone, if you start POI Alert again, they are there again (until you remove them via the menu). Good.

Menu:

• Displaying/list visited points works correctly.
• Removing markers works correctly.

Visited points that are moved to another folder lose their markings. Maybe not so good.

What I have noticed is that once I have selected the next tracks, I can no longer select a filter.
For example, I select next tracks. After a few seconds I see the result. There I find MTB, hiking, skiing tracks. And also downloaded tracks that I have not recorded at all. Now I would like to filter for hiking only and recorded only.
But I can't do that. So I have to go back, first apply the filter and then next tracks again.

That also confused me at first. "Next tracks" and "next points" ARE (predefined) filters. The filter icon at the bottom is also greyed out when a quick filter is active. That's why it doesn't work.

It is also slowly becoming overly complex and somewhat confusing. Sorting, filters, quick filters... Some things can be combined, some can't, some settings are distributed. You have to learn the ropes and not everything is optimised.

Even if it is not mentioned in the changelog: Circles around points with radius in px now work.

I'm not into the search too much, but "nearest tracks" now lists track independent from their distance it seems.

What does "recorded" mean for Locus? Tracks with some insignificant number of trackpoints? no/1970 timestamps? Would be great if you could tell the algo.

Nearest tracks: now ALWAYS sorts around the GPS position and not the map centre. Bug. See two posts above.

"Last recorded": Clearly for me. Seems to work fine, only sorts actually recorded tracks by date and not planned routes. I no longer have "1970" tracks, so I can't test that.

Hi Menion, thanks, but sorry, the search in the library now has a bug:

The quick search buttons "nearest points/tracks" no longer work if "Cursor" is set as the source for searching. It seems to always sort to the gps position, no matter where the cursor/map center is. And that's really annoying, because I use this sorting the most. Now I have to go through the sorting menu and the filter in the bottom line until I get a fix, which is more cumbersome.

The new "last recorded" button is IMHO positioned very awkwardly in the first position. I have to scroll sideways to get to "nearest tracks". In addition, "last recorded" is pointless if you want to search for points or planned routes, another reason why it should not be placed at the front.

Better to position "last recorded" last or somewhere else. Or make the buttons narrower (perhaps just meaningful symbols without text) so that all three fit on the display without having to scroll.

fix: nearest points/tracks also display folders: doesn't work for me. No folders are displayed.
Edit: or do you mean the folder details for the points/tracks found? Then ok.

Good morning Menion,

thanks for the immediate fix. 🙂 Saving works again.

But the selection px for the radius is still not applied. It is still reset to metres. For me this is unimportant, but if px is offered, it should of course also work. 🙂

BTW: Download from Google Drive works again as usual. Must have been a temporary problem.

In the meantime I was able to download the new version, but only in desktop view.

Bug: Edit folder / circles around points.
The "save" button at the bottom right is greyed out, no changes can be saved. Applies to the basic settings and the circles. It is therefore also not possible to change the folder name or the icon.

See screenshot.

New version 4.28.3 uploaded to Google Play (and Google Drive) and awaits confirmation.

Can't download from Google Drive. Server problem?

Hier habe ich das her:

https://www.locusmap.app/de/locus-map-4-gegen-locus-map-3-classic/

Hast recht, dürfte aber so nicht (mehr) stimmen.

Jein. LM3 wird vorerst noch gepflegt, ist aber seit Einführung von LM4 von allen Weiterentwicklungen und neuen Funktionen ausgenommen. Diese finden ausschließlich bei LM4 statt.

"Dass beide in der Entwicklung gehalten werden" stimmt also nicht und das steht m. W. auch nirgedwo so.
Dennoch sollte LM3 auch grundsätzlich unter A14 funktionieren, denn dass ist eben Pflege.

Hi Menion,

I've just had a look at my old S7, which still has the latest release version 4.28.2 on it. Even there, most of the tracks (not all) from these four old folders are without any statistics data.
This probably happened during the first conversion of the database (during the first installation of the MyLib version), and I hadn't opened these tracks since then and noticed it.

Since I have since restored the statistics of the tracks using "Update elevation data", this has been resolved. I don't think we need to investigate this any further.
After synchronisation, the tracks are now also complete again on the old S7.

Apart from that, I would like to express my enthusiasm about the possibilities of the new library and the latest improvements. Search, filters, operations... It's really fun to work with!

I haven't found any other bugs or problems yet. The current beta makes a very good impression.

Thank you very much and have a nice weekend!

Addendum: I've found a few more older tracks (2015, 2014), all ok with statistics. So it wasn't due to age. 🙂

Thanks for the update! New "fast filters" for nearest points and tracks are great!

After first tests I found some issues:

1. Older tracks (2016 and older) have almost all lost their altitude data. No display of an elevation chart. I had to update the elevation data for all of these tracks one by one so that the charts were displayed again (unfortunately batch update is not possible).

2a. Circles around points: if you delete the old value completely (long press back button), Locus crashes immediately and restarts. (BTW: is it really necessary to be able to enter decimal places here?)

2b. The setting px (instead of metres) for the radius is not accepted. It is always reset to metres.

I go on with testing.