Messages

"style" (missing in your reference)

Thanks, added it

Anyway because MF project seems not to be dead like in times I started to write own modded version, I'll instead contribute changes back to the official version.

Good news :-)
BTW, are you planning to update the V4-maps engine to mapsforge 0.12.0? This finally adds curved path text rendering, which is great for street names:
https://github.com/mapsforge/mapsforge/pull/1112#issuecomment-477969418

What is to do? Doesn´t the  features of the Locus V3 rendering engine work any longer?
Is there any description for Locus themes of all tags I can use?

Locus uses the standard mapsforge engine for maps V4 and higher. As the Locus extensions were never ported back to mapsforge, they can't be used.
I made a reference which tags are supported by which mapsforge version here:
https://www.openandromaps.org/en/oam-forums/topic/mapsforge-rendertheme-reference

I must correct, I used Elements theme. It displays a lot, but when zooming out town names should have the right prio...

Please use Elevate for normal or densely mapped areas. Elements is meant for countries like Iceland, northern Scandinavia etc.

Of course, this theme is only for V3 maps.

Please could you update your theme to V4 maps?
I really love it and used it always with the LoMaps.

The original Tiramisù 3 should work with V4 maps, just put it in a seperate directory in the theme folder. You find it in the link in the first post.

Is there a definitive guide to the usage of these tags anywhere?

The best thing is still this:
https://github.com/mapsforge/mapsforge/blob/master/docs/Rendertheme.md
That's a reason why I made the table, to have at least a complete overview. Of course one can add a lot to it, but it's a start.

I made a reference which mapsforge version support which tags that can be found here:
https://www.openandromaps.org/oam-forums/topic/mapsforge-rendertheme-reference

Thanks for the hint about the problem tags in the theme for V4 on your site.

I made a reference which mapsforge version support which tags that can be found here:
https://www.openandromaps.org/oam-forums/topic/mapsforge-rendertheme-reference

"Device screen scaling": I already read the post from Tobias, but I'm not too clever from this. What is the main issue he tries to describe except lack of interest in compatibility?

That post was more my tiredness of only limited support of new mapsforge features in various apps (not just Locus, but this was the app John came up with) which limit app-independent development as we do at OpenAndroMaps. In an older discussion I got the impression that LoMaps have a bigger priority than compatibility, but this new thread let's me hope for a change :-)

But as far as device screen scaling is concerned - as a cross-app-theme-developer this is the most important issue. It was introduced with mapsforge 0.4 in 2014, at first I was a bit sceptical but with very high ppi nowadays it's a must for good rendering, as far as I'm concerned.

Here's a description of the problem I posted in a different forum:

Mapsforge maps are meant to be scaled to screen density of the device, so that a map at 160ppi looks exactly the same as with 480ppi. To do that, not only symbols and line width are scaled, but also map tile size. So if you have a map tile size of 256px at 160ppi, you get 768px at 480ppi.
Locus uses a mod of a very old mapsforge version with no scaled tiles. So with modern devices with very high pixel density, you still get 256px like for devices years ago. The only thing that is scaled is line width and symbols. But as these grow larger (3x as large at 480ppi), the space on a 256px map tile gets more crowded, and less can be displayed. So when looking at the same zoom level, less and coarse information is shown.

Here are some comparison of a densely mapped are at zoom level 17:


At first, it looks as if Locus shows more - but this isn't the case, as the area is only larger as the tile sizes are smaller. The same area can achieved by OruxMaps by using the zoom button.

Now here you can see what details are available if tile size is adjusted:

In Locus, streets are rendered much too fat, so they overlap and swallow too much space. Only a few symbols are displayed, as most are eliminated because of too little space.

So the scaling policy of OruxMaps is true to how the maps are meant to be displayed and can be scaled to every pixel density without loss of details. The only disadvantage is that with larger tile size direct comparison to online maps with old 256px tile size is not possible (although there are more HD maps coming with larger tile size as it's necessary to keep the legible on high density devices).

On my to-do-list for the Locus version right now is the idea of moving all zoom-appears 1-2 levels as this is the only possibility right now to get it a bit better, but with other disadvantages.

Other issues:
- Folder structure for themes: only one theme xml per folder is allowed, and folder are also needed. Any other app with theme support allows xml files in base folder and graphics whereever the xml points to. So a special Locus format is always necessary. I get the one folder, one theme policy, but why not two or more xml files?
- Forced connection of V4 maps with V4 themes - it should be possible to use V3 maps with V4/V5 themes, or V3 maps and V3 standard mapsforge themes etc. Maybe use standard-mapsforge for all themes, whatever version, and locus-mapsforge-fork for those themes with locus-extended="1" in the rendertheme tag? That would solve the issues of the two posts above.

Best regards,
Tobias

The theme used is a pretty current version of Elevate, not Andromaps, and the map is also one of OpenAndroMaps, as surface is rendered.
But the symbols/text size shouldn't be reduced by zooming, and also aren't in all but one example - that's just an optical illusion. As everything around is enlarged it seems that they are smaller, but they aren't. In the first example it seems like the text size is reduced via a Locus setting (or some bug), because in the theme code the size is constant.

ach so, die  Singletrail-Skala hat aber gerade mal drei Farben für fünf  Schwierigkeitsgrade. Damit kann man imho auf Karten, zumal auf einem 4 -5 Zoll Smartphone wenig anfangen.

Deshalb wird auch S1 und S3 zweifarbig dargestellt, wie auch auf der Singletrailskala als fließender Übergang.

Das Schema blau-rot-schwarz ist an die Skipisten angelehnt, wie auch die Wanderweg-Einteilung vom DAV (+gelb), also sollte es eigentlich durchaus einleuchtend und verständlich sein.

Von Mountainbikern hab ich da bisher ziemlich positive Rückmeldung. Höchstens, dass sie bei Gegenden mit höherer Wegdichte außerhalb der Alpen (Elevate habe ich auf die Nutzung in den Alpen optimiert) auf die Markierung von Forstwegen verzichten können (insb. S0), deshalb hab ich da optional gemacht.

About themes - I think, it should be a lot easier, to give me a list of tags that do not work in new Locus and are included in v 0.5, and I'll try to add support also for them to Locus.

Hi Menion,
do you still intend to add support for mapsforge 0.5 themes?
At the moment I'm working on a new version based on mapsforge 0.5 possibilities of the Elevate theme for OpenAndroMaps, which of course doesn't work with Locus for now. Maybe it's good for testing:
http://www.openandromaps.org/en/oam-forums/topic/elevate-updates-and-test-versions-news#post-3858
Best regards,
Tobias