Messages

Question, why are the bike paths displayed differently depending on the used map?

I can't check directly on the maps you are looking at but there are various possible reasons
- OAM includes more information about surfaces and accessibility than Lomaps do
- OAM interprets lcn=yes as network=lcn, resulting in more local cycle networks showing than for Lomaps. This is possibly the case in your example.
- OAM does many similar transformations on the data, producing more information in general
- OAM attaches all routes to the highway they follow, meaning it is possible to know if bike and hike routes are running together, for example
- OAM preserves only the route of the highest "importance" of each type (bike, hike, MTB) when several routes run together. Lomaps preserves all routes. The theme then displays the route of the highest importance but if there are several routes of the same importance running together, the selection of which route reference to label it as is effectively random.

I want to temporarily hide tracks, this is now broken. I can't show them again after... hiding.

And what does it do? Hide: no? Rather unload I guess? This is not what is expected here. Here we need a quick show/hide toggle.
The counter of loaded tracks stays as is, after refresh ui it goes to 0.

The behaviour of prior version was perfect for me. A dialog window is wrong here.

Solution. Eye symbol: short tap = show/hide. Longtap: unload all. If none are loaded, bring up track manager.

Hi there, also my 2 cents to the new side panel:
First, like it! Wouldn't mind some more configuration (e.g. rarely using LoPoints, so would rather be able to hide those lines).

What I'm not quite happy with yet is the theme selector: When you change the theme, you still first have to go through the options screen everytime, even though now there's a dedicated button for that. When switching between themes, I rarely also need to change the current selection, so this is a superfluous step.
Also, the "layers" button may be technically correct, but I think most users will be confused and would rather call this "theme settings", so I propose to use a cogwheel icon.

Ich würde mich über Euer Feedback freuen.

Hallo Olaf, dann schieß mal los!
Was kann denn Dein Gerät konkret besser, wie groß ist es, wie sieht's mit der Stromversorgung aus und wie wird die Verbindung zum Handy hergestellt?
Statt schwammiger Formulierungen a la "nicht zufrieden mit der Qualität der GPS-Positionsdaten", "welches deutlich bessere Daten liefert" und "mit der aktuellen Präzision...zufrieden" wäre ein Foto vom Prototyp und ein dirikter Vergleich zwischen (D)einem Smartphone -unter denen gibt's ja durchaus auch große Unterschiede- und Deiner Entwicklung schon hilfreich.

In the current non-beta LM4, I can't find any themes in the store.  (I answered a question in another thread related to themes, so I was curious.)  I spent some time in the store totally lost, then found the "+" icon at the bottom of the theme switcher, which brought me to an empty page on the store.

*None* of the themes in the store would work with the new LoMaps! I don't know what the plans for the store are.
However the Voluntary theme is now compatible with old and new LoMaps as well as OAM maps. You can download it from https://voluntary.nichesite.org

[@lor74cas]

Hi guys,

@lor74cas
I've informed @Radim V about it. Should be improved in the one of next app versions.

@Gerhard57
ah, thanks. Info about "Presets" fixed.

@Tapio
backup info improved, thanks

@joeloc
Default folder for saving points: sorry, can't confirm the mentioned problem. The folder that should be preselected is only saved when you leave "Edit point" screen. Not in any other case.

Deadly recording button: as mentioned by @Tapio , this is not a bug but an intent. If you have a problem with current behavior, the solution may be to hide it permanently and add a "Track record" button into the functions panel.

"Live chat" icon > this should be visible in case, the owner of the live tracking room enabled "Live chat" in the room settings.

@balloni55
good observation, thanks. G4L use different generated ID for logs and it caused this. I've reworked whole system and also improved detection of duplications so it should work correctly in the next app version, thanks.

Wenn der Programmierer für die Preset-Klasse sich dieser Abhängigkeiten bewusst wäre, dann hätte er meiner Meinung mit Sicherheit nicht für jedes Preset eine eigene Liste der zu berücksichtigenden Optionen eingeführt.

Wäre es nicht besser, diese Diskussion mit Menion zu führen?
Dieser belehrende Ton bringt hier im Forum nix. Aber Menion und sein Team wären sicher sehr froh darüber noch etwas lernen zu dürfen, um sich dann der Arbeit, die sie seit vielen Jahren leisten, vielleicht noch etwas bewusster zu werden.
Nichts für ungut, aber mit der Behauptungen, Menions Leute wüssten nicht was sie tun, sollte man evtl. doch etwas zurückhaltender sein.

[Locus Map (4)]

New Locus Map (4) version

Important links
- list of news of public versions
- Public versions
- Beta versions

Versions
25. 4. 2023 - Locus 4.16.0

Noch einmal zur Frage dieses Themas: "Wo wurde dieses Bild aufgenommen?"

@balloni55 hat für die Beantwortung dieser Frage hier den entscheidenden Hinweis gegeben.

Richtig gut funktioniert das allerdings nur dann, wenn im DCIM-Ordner das Foto, für das der Aufnahmeort ermittelt werden soll, das einzige Geotag Foto ist. Sind in diesem Ordner mehrere Geotag Fotos, werden die nochmals importiert, was zu Problemen führen kann.

Man sollte daher auf der selben Ebene, auf der der DCIM-Ordner liegt, einen Ordner für alle Geotag Fotos anlegen, in die man diese nach einem Import verschiebt. LM findet sie auch in einem solchen Ordner und zeigt sie an, berücksichtigt aber für eine zusätzliche Geotag Foto Ebene nur den DCIM-Ordner und seine Unterordner.

Genau so sollte man für Fotos verfahren, die mit Geotag erstellt und in DCIM/Camera abgelegt werden. Spätestens dann, wenn man den Aufnahmeort eines Fotos ermitteln will, alle Geotag Fotos in einen anderen Ordner verschieben.

Ah, thanks balloni for the reminder ... visible truth is that I've forgot about it. I remember I tested it and noticed a very similar (not so critical) problem, but even after some testing, I wasn't able to find out why this happens.

Hmm ... complicated problem.

I may only add it higher in the never-ending list of priority tasks.

Do you have a screenshot? I have no clue what this is about; in what context do we have "active points"?

Hi, i've made a Screen Cap Video:
https://1drv.ms/v/s!AredTfs4J1f5gu5kazAzPtRydwnEtQ
Best, Lucas

4.15.2:
Great update with pointer directing at an active point

Do you have a screenshot? I have no clue what this is about; in what context do we have "active points"?

I think the app must become more attractive for Geocaching. I'm personally not interested in it, also I guess Menion doesn't do it. But they are a big and important community. [Removed Apple bashing]

missing geocaching features (long list of missing features starting by live-map, mass edit & upload of notes etc)

This is my favorite point too.
 - Please continue the started process to substitute the addon G4L. (Import of one named cache, live chart ...)
- define multiple different filters
  I often use special filters for different situations and it's a struggle to define and change all filterelements case by case (without a mistake 😚)
- include LabCaches

)
- missing geocaching features (long list of missing features starting by live-map, mass edit & upload of notes etc)

I would like to see features from the field notes add on incorporated into the app. Also, Adventure Lab Caches.