Messages

Do you plan to add "cubic" to the rivers as you did with the streams?

Tendency is: No. But I am not sure about the consequences. I think there may be footways/cycleways close to rivers, which then aren't aligned perfectly, or worse, get hidden below the river.

EDIT: A clear no. Author of Voluntary theme will undo such changes for rivers. Non-connected parts may happen, or bridges at the wrong place.

Hi John, beta is much better and clearer for cycling. The trees are not very important when cycling. It is important to navigate and the beta is clearer on the small display of the phone.

@karlchick
Point 13
I see. I added:

Code Select Expand


<osm-tag key="service" value="alley" zoom-appear="13" />
<osm-tag key="service" value="driveway" zoom-appear="13" />
<osm-tag key="service" value="emergency_access " zoom-appear="13" />
<osm-tag key="service" value="parking_aisle" zoom-appear="13" />
<osm-tag key="service" value="slipway" zoom-appear="13" />


@john_percy
Mapsforge now supports any "key" that can be used as a text value. So you can, for example, display the value of the key "highway"

Code Select Expand

<pathText k="highway" font-style="normal" font-size=....
Anyway, you are right - "osmc_text" and "osmc_text_length" are really missing in the latest LoMaps. The latest version of LoMaps was released in version 4 which doesn't contain variable "tag-values" (%s, %f)

Anyway, I generated a new version of LoMaps (see attached map of Monaco) as version 5. The mentioned "osmc_text" and "osmc_text_length" tags should be available in the data. But I think I found some bug in the Mapsforge generator, where the tag-value variable is not included in the data if there is another tag with the same value. The value of "osmc_text" is often the same as the value of "ref", and it seems that in such a situation the "osmc_text" is not added to the data. I need to test this with @Menion in more detail and debug the data in the map tiles.


For this reason, I edited one tourist way with "osmc_text" value and set value "03 testtest" (avaialable in attached monaco map). You can test it with your theme...

PathText to display the text "03 testtest"

Code Select Expand

<pathText k="osmc_text" dy="2" font-style="bold" font-size="16" fill="#e67400" stroke="#ffffff" stroke-width="2.5" priority="1000"/>

@john_percy Honestly, the position for captions remains in the theme very likely from my testing of this attribute. As I recall, "position" without an ID has minimal effect. It basically changes the defining point for the text box (the minimum rectangle around the text).

You may also share a theme-in-progress with me, I'll check if the app throws any errors in the background if you want.

John, maybe I'm too quick - the Voluntary Locus.zip\Voluntary\changelog.txt latest "Recent Changes Dec 2021" - I don't see any more recent changes?

OAM almost always (?) uses Mapsforge4 maps, so they use the new version of Mapsforge renderer. LoMaps still use highly customized V3 versions as you surely know.

Now sure how correctly works autoloading for V4 maps, but unfortunately V3 system collides with the mentioned problem. Complicated

Experts and novices alike will always suffer from changes, yet changes are key to improvements and progress.
Hence - AGAIN - my advise to spend energy into a 21st century help and function (*) search capability. Android settings in many new devices deliver that: you type a word about what you want to do and get a number of matching functions/settings at your fingertip.
That does not address the ongoing UI discussion, I know. But the overwhelming (yet USEFUL!!!) settings have been a reported pain since years.
(*) each function and setting needs to have a number of keywords and synonyms associated. In the selected language and always plus English.

Well, I had a look on the 2 raster maps I use. TopPlusOpen and Kompass. The size is pretty much perfect (a bit varying in different ZL). But I can see if Locus chose 2x instead 3x, it'll be too small again. I'd prefer to use it as it is now.

Yes John, it is a different story. Emux is quite hard working on VTM & MapsForge system so it is used as a core map engine in his apps.

I can't imagine how to use it in Locus Map, sorry. Using of rendered tiles from MapsForge library is one thing, using a complete map system as a base for the whole application is something completely different.

You need to be logged into the forum to see the ZIPs.
I was not when I looked yesterday ...
Cheers
Michael

[Main info]

One of the major problems with maps are caused by really really old system how the app works with map files, online maps, the system for rendering map tiles etc. I decided to update this system to try to solve most of the major problems.

Main info: to test changes is needed special ALPHA version. Currently not yet published, plan is on start of March. Subscribe to receive new information once ALPHA is ready for the test.

Current major visible changes

Implemented

• automatic scaling of all raster maps based on device DPI
• support for custom HDPI online maps, more info

In progress/preparation

• features related to MapsForge V4 maps, more info

Great, thx. My favourite hiking theme. The only change I do is giving shelters more attention. View starting at zl15 plus a red symbol 😁

In beta, comparing to last release:
- wider font in header, and it doesn't fit sometimes.
- no cutting and three dots in menu