Messages

@Kodela, warst Du mal Beamter und nebenberuflich Schriftsteller? Sorry, ich muss das einfach fragen, bitte nimm' es mit Humor auf 😜

Genau genommen (nach den Gesetzen der Booleschen Algebra) müsste ich "Nein" oder "Falsch" sagen, aber sooo genau wolltest Du Deine Frage wohl nicht beantwortet haben. Dann verrate ich Dir, dass ich kein Schriftsteller war. 😜

Hier ein kurzes Video, das Schritt für Schritt zeigt, wie es zu reproduzieren ist.

Hmm.. I think the LoMap approach to cycle/mtb routes is very different compared to OAM.

OAM seems to remap the cycle/mtb/hiking network values through to the highways they are related and uses separated tags for each type of route (network=cycle, mtnetwork=mtb and hknetwork=hiking).

OAM additionally resolves issues like route=mtb and network=ncn, by remapping these through to mtbnetwork=nmn. An example of this can be seen in the attached first pair of images showing LoMap/OAM with the latest v5 Voluntary theme, see how the mtb route is displayed in LoMap with blue/purple blobs but in OAM is only purple blobs.

I resolved this for now in LoMap maps by ignoring the network tag and using just the route=mtb/bicycle values to differentiate them. Separate rules are used for OAM and ignored by LoMap by checking for route="~", since OAM doesn't used route tags for network routes. See second pair of images comparing LoMap/OAM with my latest OS prototype theme.

LoMap having separated routes results in multiple renders for each route, advantage is ref labels for both routes, disadvantage is multiple highlight/emphasis drawn.
 
Another feature/issue... since LoMap is using separated route ways from the highways, I can't determine if a route is off-road. With OAM I am introducing hollow blobs when a route is off-road, see attached third pair of images.

Finally, I am missing OAM's feature to autogenerate route refs when a route has no ref tag, it does this by raking the first letter if each word in the routes name and any numbers, see examples attached and how OAM names the mtb route PWCR.

A beta version of the Voluntary and Velocity themes to work with both this Locus beta app & maps and OAM maps is now available at:
https://voluntary.nichesite.org/beta.html


The new versions are named Voluntary V5 LE and Velocity V5 LE (Locus Edition)

Eine wichtige Information

Haben Sie "Navigationsbefehle einbeziehen" aktiviert? Wirklich wichtige Einstellungen!!

@koleda

Nein das habe ich nicht vergessen. 27 Minuten sind es auch mit dem Profil Hiking-Alpine-SAC6.

Komisch.
Wie Du an meinem Screenshot ersehen kannst, erhalte ich im Planer (Locus V3.66.2 / BRouter 1.6.3) eine Reisezeit von 2:48h.

Damit es keinen Zweifel an meiner Einstellung gibt ist im Anhang dazu ein Screenshot.

Kannst Du einmal in einem Screenshot zeigen, wie es bei Dir aussieht, wenn Du die Waxensteinroute mit Locus Map erstellst?

Hier kann die Formel angewandt werden und wird auch erklärt. Sehr einfach.
https://www.wanderndeluxe.de/en/calculate-hiking-time-distance-altitude/

Nochmals ein Grund, dem User die Möglichkeit in die Hand zu geben, interne Variablen selber in eine Formel zu packen.
Es würde Menion und Team Arbeit abnehmen und dem User Freiheiten schenken.

LG, Joska

[@CabrioTourer]

@CabrioTourer
Navigation commands > should be hidden. If they aren't it usually means, that for some reason, the connection between the track and these waypoints breaks and they are no longer considered as navigation points, but ordinary waypoints. ... ah, seems you find this. The question is why and how this happened.

It's the same reason why sometimes the shaping points lost. You remember. The loonnng time issue we never found and were not able to reproduce it.
This time I'm a bit sure it depend on not enough memory. I edited a tour in tour planner on medirore tablet. Exit Tour planner without saving. Did something else which resulted in a Locus crash. (I guess bcs not enough memory. Same thing works on my flagship smartphone without problem but crashes often on tablet)
Somewhere in this scenario the shaping points are lost and navigation commands lost there tour connection.

From me also once again a thank you
Have now been doing various tests all day and testing other combinations of If and Endif and variables. Once it was not zoomed at all and mostly only in and not out. I just thought of something else and I think that will work. Will be tested tomorrow.
The Unix seconds are not used with Navipoint1_Time. I have found out through various tests that it is specified in miliseconds. Unfortunately I found this out only after many unsuccessful tests.
I have to take a closer look at the tick later.

The examples for inspiration are all grayed out. Are they inactive ? How do you do that ?

d) Add an additional variable state trigger to the profile: "%tick !~ \%tick"
Done.

@tapio - a simple "SAY THANKS" click wasn't enough this time - thanks (again)!

Another two tiny issues, with a major consequences, were found and fixed:
- on some devices, the app did not record any points (because of problematic detection of correct point precision)
- and also someone may suffer from slow GPX import

Uff, so another version was published. This one was not planned and already contains more untested code than I would like. Anyway, it's out ...

The Velocity theme has been modified to show lakes and other bodies of water earlier. I've also made a few other tweaks.
Download from the link below.

Voluntary and Velocity themes - https://voluntary.nichesite.org

Ah got it. Problematic wrapping in the latest app version was found & fixed, thanks!

Since the new releases of Locus Map 4.15.1 and Locus Classic 3.66.1, both editions are now text wrapping "long" names.

For really long names this is good, but the algorithm is going g a poor job of wrapping also not very long names. Also the wrapping seems to be left justified, and the placement of symbols "below" are not to the bottom/right.

Seems to be only v4 maps affected.

In the past this would occur rare and then stop, e.g. if change maps or restart. But, I've tried restarting and it seems be permanent now.

Attached is an example.

Worst is the Nottingham Hill. Having a single character word wrapped also looks bad.

Can the text wrapping be made a setting? Or improved to of wrap on non-alpha chars?

Excellent

another common problem is the android automatic permissions removal if you dont use an app for a while.