Messages

Thanks John, I've found a possible reason. The next version next week, as you already know.

Hello John,
thanks, this should already be solved and will be published in the next app version next week.

For this I use Voluntary(street) or Velocity.

Both are very similar to Kurviger.

v1.4.0

• Military area names part of "Suburb" option
• Later display of some POI captions
• natural:hedge and natural:tree_row design shamelessly copied from Voluntary UK theme of John Percy
• Rework and xml improvement "Road network"
• "All features" menu change

[OS Map v20231203 Draft1.zip]

Had a busy evening, managed to draft fixes for all the issues reported so far.

I've loaded a draft version with fixes here:

    OS Map v20231203 Draft1.zip

I've not updated the legends or release notes yet, will do that for a proper release.

Changes made are:
- reduced heavy pylons at high zoom levels.
- fixed issues causing Oruxmap to not display many elements correctly.
- added option enabled by default "show symbols earlier" to allow reduced clutter in cities.
- fixed dynamic view of footpath dashes green/black out of sync
- moved surface highlights to below the highways to avoid obscuring the surface texture and street names.

BTW, the issue with Oruxmaps was down to case sensitivity of filenames in theme vs actual filenames. Seems Windows likes to capitalise the first letter by default. Have renamed all files to lowercase now.

Please try out the new draft and I'll all be very grateful of any feedback, thanks in advance.

@karlchick
I understand that in this situation the "layer" tag is probably misapplied (as per the instructions). However, I have always tried to avoid manipulating OSM data "from the table" (unless it's necessary)

I really think the best solution is to add a "layer" tag for hike & vike way as well. Please try the following map (not posted in the store). I think it should solve your problems.  https://gofile.me/7ecf2/CVYghVabB

In any case, this is very likely to cause further complications. Mapsforge has an internal limit where a node/path can have a maximum of 15 tags. I know there are already paths with 15 tags and I'm afraid that using a layer tag will exceed this limit. Well, we'll see during the next generation

[When a way has a layer tag applied, the way is drawn under or above other ways (by the mapsforge rendering engine?) with no possibility for the theme to alter this.]

I don't think I made my point clear enough.

I'm not suggesting removal of the layer tag for ways that are supposed to use it,  eg Bridges. Only for ways that are not supposed to use it... like cycleways for instance. This is defined is the osm guidelines and also copied out in post #1.

When a way has a layer tag applied, the way is drawn under or above other ways (by the mapsforge rendering engine?) with no possibility for the theme to alter this.

In my example I was using routes with cycleway but this is not relevant to the layer tag here... further along the same cycleway is another embankment on the cycleway for which it has no layer tag,  this is drawn as expected,  see attached.

Hence my suggestion layer tag is filtered out for ways that should not use it, as per osm guidelines in first post.

Hi,

all themes were removed because were created for LoMaps gen 3 and weren't compatible with gen 4. But some authors were preparing new version compatible with LoMaps gen 4. @john_percy @karlchick do you think is it possible to publish your themes in Locus Store?

Hi,
Where can I find themes for the new Locus (4)?  When I go to themes, only 4 are listed and the Store is empty...
-Donald

Elements theme. "all content is shown
as soon as it is contained in the map."
https://www.openandromaps.org/en/legend/elevate-mountain-hike-theme

Recently, I drove more than 1000 km on the bike according to the map theme of the Voluntary Beta from 1.8.2023. The map theme is very clear and it was driven very well in Poland and the Czech Republic. Thanks John.

Thank you John for the explanation. This should only be highlighted for: highway=cycleway But I understand that it may not suit everyone. Therefore, I suggest that the highlighting be optional and only in the cycling menu.

I've seen those occurences with cycleways close to railways, and the cycleways disappearing behind railways at lower ZL. Not much we can do here I guess. Except maybe allowing to hide railways.
It was in all themes I tried.
Please provide a position, for testing...

Hi Andrew, I have another request for adjusting the cycling. If the cycle path is not even a cycle route, it is almost not visible in the blue color. If it runs near the railway line, it is not visible at all. In the topics of Locus and Paws, the cycle paths are highlighted with a purple color. Would it be possible to add the possibility to make the cycle path to the menu? After activation, it would be highlighted to a full purple color. And I'm sorry I still want some changes.

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.

You are right. I discovered an error in the Voluntary theme

You cannot view this attachment.