Messages

For me, track recording is 4%, and optional navigation increases that to 8% (total). Will depend completely on battery size & condition & screen brightness. I therefore (mostly) never use navigation, and simply turn on the screen briefly before any potential turn. I find looking at the map far more informative & reliable than turn instructions. I have the screen timeout for 6s. Sometimes I use POI alert but to replace navigation commands would be very tedious if lots of turns.

I agree with Andrew.
In addition to keeping the consumption of Locus under control, it is also necessary to reduce that of the device.
If you don't need to be contacted by phone, you can put it in airplane mode.
If, on the other hand, a telephone connection is needed, but it is possible to give up the internet connection, data connectivity can be disabled.

Hi Menione, the new search is great. Very good work. This is the best change in the last year. Personally, I would add the option to view the search directly on the map, but it's not that important. Thanks.

For displaying realistic values in the bottom bar "Include navigation commands" has to be checked.

As you probably know, Locus used a custom implementation of the Mapsforge vector map rendering for LoMaps vector maps. There were several attributes that the original Mapsforge did not support.

As of May 2023, LoMaps is being released as Mapsforge V4 and the old V3 themes cannot be used for the new LoMaps V4. The new theme must be prepared to work with the new LoMaps V4.
 
We have prepared a simple script to help transform an existing Locus V3 theme into a Mapsforge V4 theme 

Script and simple doc are available at https://github.com/asamm/lomaps-mapsforge/tree/main/theme-v3-to-v4-converter

Please note that the script does not convert the entire theme 1:1.
Manual work will still be required, but should save time when editing attributes.

The new LoMaps now available in the Locus Store are much more mainstream Mapsforge but require updated themes. A preliminary version of Voluntary is now available for download from the link below. Please delete your old version in Locus first.

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

Sent from my moto g(6) plus using Tapatalk

@TrulloF
as mentioned above LoMaps V4 uses official Mapsforge renderer and it's needed to remove all tags that are not supported by Mapsforge.

I downloaded your theme and fixed some small issues like 'priority' in rule tag, 'repeat' can not be used for symbol, 'color' for symbol and 'country' attribute used for subways. I commented the subways section so please replace it with the symbol you want to use for subways
(the "fixed" theme in the attachment)

fix: (SILVER) activating of Presets by long-tapping an item in function panel

works: but selecting Information instead of a preset opens the Information for the dashboard

...
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!

See my response in the German thread.
If you had an old LM3 Pro install, maybe with Locus root folder directly on top of the SD card, then a new install of LM4 will not find that, except you have an AFA side load.

Tried kmz and Google Earth its also flawed.
I did write an email to the creator of MapC2MapC64.

Maybe he knows whats the problem.

[Norway_Mainland]

During the last months I worked a lot to create new DTMs, now they are available:

Norway_Mainland v2, Norway_Svalbard v1, Norway_Jan Mayen v1, Denmark_Faroes v1, United Kingdom v2, Ireland v1, Portugal_Mainland v0, Portugal_Madeira v1, Portugal_Azores v1, EUROPE v18

Have fun!

There was an offending folder in themes with the name MAC_OSX which was from me compressing the new Adventure theme on my mac and no matter what program I tried, sold explorer etc. would not delete this folder....this is what was causing the apache xml blinking error.  I manually exported 2 tracks to gpx files that were after the last full backup then did a full restore and got it working again.

I like the new backup manager. The only thing I would have liked is mapitems/Calibrated_maps

Internal themes for LoMaps are tested/developed directly in Locus. Previously I used to manually copy the theme .xml via Total Commander to the device and restore the theme in the app. It's not bad, but it's not ideal. As you probably know, LoMaps will finally be in V4 and will use the default Mapsforge renderer. When we started working on LoMaps V4, I had two thoughts about how to improve the theme development process:
- usage of variables in the theme
- quick refresh the theme on a mobile device.   

For this reason we prepared a simple python tool that solves mentioned issues. It basically copies and refresh the theme on the device in one click - available at https://github.com/asamm/lomaps-mapsforge 

The process of generation of theme file is the following:
1. Base template
On the input is theme template that contains variables and definitions for custom actions. This is basically a mapsforge theme but some colors or widths are defined using variables
2. Template config
It assigns values to theme variables
3. Generation of result theme file
The theme generator combines template variables to generate the final theme file
4. Copy the theme to the device and refresh the theme

There are several requirements (intall adb, python and some other python modules) and it may be complicated to run the script at this moment. Moreover it also automatically generates a theme for POIs so it is quite focused on internal LoMaps themes and is not as configurable as it could be.
But if anybody would like to use it to develop alternative themes, it is possible to make the generator more generic. Maybe it would be enough to prepare the settings to generate also POI themes and maybe a better installation...

Please let me know if anyone is interested and I can tweak it a bit. 
 

Die vorstehenden Routing-Tests haben mich neugierig gemacht und so habe ich nun auch noch einen Test gemacht. Es ging mir primär darum, ob und welche Unterschiede es zwischen dem BRouter und dem GraphHopper gibt.

Hier zuerst ein Bild von der Teststrecke unter Verwendung des GraphHoppers:

You cannot view this attachment.

Dazu die erzeugten 5 Navigationshinweise:

- Biege links ab
- Biege rechts ab
- Biege rechts ab
- Biege links ab
- Halte dich links

Sie sind korrekt und gelten jeweils für die durch einen blauen Punkt markierten Positionen.

Unter Verwendung des BRouters ergibt sich ein anderes Bild, das sich vom vorstehenden nur in einem Punkt unterscheidet, von den beiden Knicks in der Sebastian-Rieger-Straße ist nur der obere blaue Punkt vorhanden. Dem entsprechend gib es auch nur folgende 4 Navigationshinweise:

- Biege links ab
- Biege rechts ab
- Geradeaus
- Geradeaus

Auf den ersten Blick könnte man meinen, dies sei ein Fehler oder zumindest eine qualitativ schlechtere Navigation. Das ist aber nicht so. Dort wo der GraphHopper bei der Überquerung der Biege rechts ab die beiden Hinweise "Biege rechts ab" und "Biege links ab" entsteht damit eher eine Unsicherheit. Man darf nicht rechts abbiegen und dann wieder links, man geht einfach gerade aus. Der Versatz zwischen der Straße vor der Sebastian-Rieger-Straße und dem weiterführenden Weg nach ihr ist so gering, dass auch eine Auskunftsperson in etwa sagen würde: "Gehen Sie auf der Ebereschenstraße bis zur kreuzenden Sebastian-Rieger-Straße, überqueren sie diese und gehen dann auf dem Fußweg gerade aus weiter und kommen so zum Ziel." Das ist eine ziemlich genaue Beschreibung, "Gehen Sie immer gerade aus." würde auch schon reichen.

Kurzum, ich meine, die über den BRouter generierten Hinweise sind zwar kürzer aber keinesfalls schlechter als die des GraphHoppers. Außerdem sind sie in beiden Fällen vollständig und korrekt.

Auch die Zeitangaben sind in beiden Fällen identisch und mit 3 Minuten akzeptabel.