Messages

If I use the version edited for v4 in v3 maps it works as intended.

That shouldn't happen. The rendertheme preamble should mean that your v4 theme doesn't show up in the list of themes for v3 maps and vice versa.

Have you also changed the rendertheme tag near the start of the theme?
Something like

Code Select Expand

<rendertheme xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://mapsforge.org/renderTheme" xsi:schemaLocation="http://mapsforge.org/renderTheme https://raw.githubusercontent.com/mapsforge/mapsforge/master/resources/renderTheme.xsd" version="5" map-background="#F8F8F8" map-background-outside="#EEEEEE">
(This doesn't work in Tapatalk - use Webview.)

@TrulloF Have you tried running your theme through an XML checker? A white map may indicate unmatched tags.


Sent from my moto g(6) plus using Tapatalk

Like @karlchick I don't want to render all areas as semi transparent. I believe OAM removes layer=-1 from tunnels in preprocessing and allows tunnels to be rendered by the theme with skillful use of transparency and position in the theme. I prefer this and I think it gives a better result overall.
The reason @karlchick can't get cycle route blobs to behave as wanted in tunnels (or on bridges) is because Lomaps treats all hiking, cycling and MTB routes as separate ways which don't inherit the tag values of the highways they follow. So the road has a tunnel tag but the cycle route does not.
Edit: @karlchick You'll also find that your cycle blobs are missing from the bridge (adjacent to the tunnel) in the Lomaps version. They have been drawn on layer 0, underneath the bridge layer, as the cycle route doesn't inherit the layer tag either.

Sent from my moto g(6) plus using Tapatalk

@voldapet
I think the is something wrong with the rendering of tunnels. The screenshot below  is of the Dartford crossing of the Thames East of London. Map is England, internal theme Road
Region 1 is road underwater: nothing shown
Region 2 is road underground: normal road shown plus underground markings
Region 3 is road above ground for comparison
It seems to me:
1. Layer=-1 puts the tunnel under everything, so solid colours like the river block visibility of the road markings. Every area needs to be semi transparent for this to work.
2. Tunnel=~|no seems to also select tunnel=yes, so underground roads are selected as well as above ground roads and rendered.


The second screenshot shows the same area and theme with an OAM map.


Edit: Does the common value bug persist for "no"? OAM removes all tag value=no before processing the map. Changing the test for non-tunnels to simply tunnel=~ deals with my point 2 above but leaves the tunnel hidden by the river in the underwater section. See the effect of a modified internal theme below.

I think @settler may be correct about the river name taking unwanted priority. If I recollect correctly, I found pathtexts didn't  respect display priorities I had set. But I can't remember the details.

Sent from my moto g(6) plus using Tapatalk

If you have a reasonably big town or city you get a zoom level where either the town name is off screen (if you are not looking at the exact centre of the town) or the name obscures other detail you might want to see. At that zoom level, you probably know what town you are looking at anyway. So my thoughts are there should be a maximum zoom level at which the names of cities, towns, suburbs appear.

Sent from my moto g(6) plus using Tapatalk

@voldapet
Could you please include the bridge=viaduct tag which particularly affects rendering railways. AFAIK it is functionally equivalent to bridge=yes.


Sent from my moto g(6) plus using Tapatalk

Thanks.
It looks like I can force railway bridges over roads to render correctly without the correct layer tag (easy change) and also railway over railway (but I'm not sure if the added complexity to allow for incorrect mapping is merited).
Screenshot is of your location with modified theme.

The modified theme is available from:
https://voluntary.nichesite.org/downloads.html
https://voluntary.nichesite.org/beta.html

@settler
Could you please tell me whereabouts those screenshots are of? Also, which map are you using?
Voluntary usually renders rail bridges correctly (see my screenshots).
My guess is this is connected with incorrect use of layer tags in the mapping itself but it may be possible to get round this. Do other themes render those locations correctly?

@T-mo
Sorry about the theme versioning. I'm not sure how Voluntary arrived at version 5, except it has v5 in the first line of the theme. Sadly it has to be Locus specific as Locus uses a pre release version of Mapsforge and also treats routes totally differently from OAM. The theme has various workarounds in order to function with both Lomaps and OAM maps on Locus (but on no other app at present)
The beta version is being updated regularly at present.

Sent from my moto g(6) plus using Tapatalk

@voldapet

@karlchick
BTW: are there any standard symbols or styles that indicate designation in the UK maps?

See attached Ordnance Survey legends. PROW are red or green according to the map scale; there are different markings for different types of access rights.



Sent from my moto g(6) plus using Tapatalk

@voldapet
1. Thanks for your response about foot routes. Found the mistake in my theme!
2. If you add a highway tag to all routes (as in your example code) won't that cause them all to render as highways unless one adds a "route=~" test to all genuine highways? Would it better to transfer the underlying highway to a rt_highway tag or similar?


Sent from my moto g(6) plus using Tapatalk

I confirm @karlchick's general analysis.

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.

OAM can display hiking, cycle and MTB networks at the same time  what it can't do is display more than one of each type of route at the same time. It always selects the "higher" route. International routes are preferred over national ones and so on.

The blue blobs on the MTB route in Voluntary in the Lomaps version are incorrect. There are not both MTB and bike routes along that road.  In the original map data, MTB networks may have values of icn, ncn, rcn, lcn like cycling networks. OAM changes those to imn, nmn, rmn, lmn to avoid confusion. I was testing on the network value which was ok for OAM but ambiguous for Lomaps. I have adjusted the test and the MTB route displays correctly in the latest beta version Voluntary V5 LE from https://voluntary.nichesite.org/beta.html

The latest Voluntary V5 LE  beta also shows highlighting on Lomaps as seen in the screenshot below.

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)