Messages

Hmm.. so it sound like I should be able to see tidal=yes for lm_highway=footway (for a route=foot|hiking) when the original highway=footway had tidal=yes.

But I'm not seeing this, I can see the rendering for when highway has tidal=yes, but not for lm_highway with tidal=yes (they have different line thickness in my theme at the moment).

Would it be possible to include the tidal tag with the lm_highway tag?

It should be possible. But this is the same situation we discussed in another thread. Please consider whether this is really vital because of the number of (15) maximum tags.

Highway already has the tidal tag, and very useful it is too. I kind of assumed that lm_highway is a straight copy of highway, and hence including tidal tag would be fixing an ommission.

For routes related to highways, with lm_highway missing the tidal tag, I currently can't indicate tidal sections of routes. In OAM maps this isn't an issue since highways carry both the tidal tag and routes (albeit one of each type).

Are there other non highways tags being included in lm_highway?

Would it be possible to include the tidal tag with the lm_highway tag?

Yes, it's as John said, our themes ignored  areas that are not closed. I'm changing my theme since I don't fill or outline nature_reserve areas, just use symbol with name.

It's not an issue with the map.

- leisure=nature_reserve - I'm testing the latest LoMaps and seems to be OK (would you please check it again)

Still an issue in the latest LoMap, see attached. Link to osm data: https://www.openstreetmap.org/way/97554897#map=16/50.6817/-3.4543

But this might be a theme issue, mine and John's theme use very similar rules, but the internal theme is naming the nature reserve and outlining it... hmm...

Thanks for test map, yes it does fix my issue and improves the bridge for routes. Too (as John pointed out), attached, and now I understand what you mean about adding layer tag... but I do feel the cost of using one of the 15 tags is a little high, and possibly blocks other/future more worthy tags...

I can understand your concern about modifying osm data... although it looks like OAM are doing this already in this case.

Thank you for the updated map, looking much better now.

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

I found that LoMaps include layer=1 but OAM exclude it. I have to say that I have not found layer tags useful, they tend of mess up the rendering and usually seem to correspond to lazy mapping to quick fix lots of errors in osm.

Attached is an example if a cycleway with layer=1, showing lomap and oam maps rendering a highlight of the cycle routes underneath the highways. In this case the embankment is drawn above the highlight for lomap. The theme draws the. In the correct order to avoid this (embankment, highlight, cycleway)... but (I suspect) the layer tag overrides the theme in this case.

I'm not sure what tag transforms OAM is doing here, their documentation only mentions filtering out the layer=-1 for waterways with tunnel set...

Perhaps filter out layer tag on ways that it should not be used on, as per: https://wiki.openstreetmap.org/wiki/Key:layer

Some points from osm documentation that support this:

With some exceptions, layer=* on way ways should be used only in combination with one of tunnel=*, bridge=*, highway=steps, highway=elevator, covered=* or indoor=yes. For area areas, it could be used in combination with tags such as man_made=bridge, special types of building=* and similar.

Roads, railways, waterways etc. should not be tagged with a layer just because they are raised up on an embankment or are in a cutting - use embankment=* and cutting=*, respective waterway=ditch for this purpose.

Update, I am finding other cycle routes missing too,

e.g. NCN 5: 
https://www.openstreetmap.org/relation/123318#map=17/51.45736/-0.95540

And NCN 6:
https://www.openstreetmap.org/way/41156200#map=12/52.3602/-0.9057

And NCN 51:
https://www.openstreetmap.org/relation/15020

and NCN 13:
https://www.openstreetmap.org/relation/9765637

and NCN 71:
https://www.openstreetmap.org/relation/162996

Interesting that it seems to be NCN routes... note these routes are all fully available in previous versions of the LoMap map and current OAM map.

Anyone know how frequently the LoMap maps are regenerated? I know the OAM maps are monthly.

I just downloaded the latest England Lomap (4 Sept 2023) and noticed that bicycle route NCN 45 has gone missing.

https://www.openstreetmap.org/relation/22602#map=8/50.917/-6.152

I see that the route was recently edited in OSM and definitely exists, perhaps someone deleted it just prior to the LoMap generation?

I can't view the history in OSM, says it's too large to load...

Can we get this fixed/regenerated?

Best regards
Karl.

Hmm, I may look at the correct path later. Anyway I'm glad it works for you now

I think the behaviour is correct. I have now set up the lnk files to have no path just "legend.pdf" and make sure I zip up the theme without a sub-directory. This then works for both zipped and unzipped usages of the theme.

Desert & OS Map themes are the best at showing a difference. I have even modified Desert to make it even more evident, even at lower zoom levels.

Andrew, did you also modify the OS map theme, the colour of the unsealed Road in your screenshot looks strange to me. Attached is a UK example of an classified road that transitions to unsealed, the casings become dashed, but the core remains the same colour...

... or b) a relative path within the theme directory. So only the "legend.pdf" and not the "mapsVector/_themes/legend.pdf".

Thanks Menion, I tried just legend.pdf and it gave the attached error. I then tried "theme zip dir/legend.pdf",, I.e. "OS Map/OS Map Day Legend.pdf" and that worked.

In my zip of the theme all the files are in a subdirectory "OS Map/", should I be zipping the theme as the root of the zip file perhaps?

Anyhow, I can now get legends working, thanks for help and compliments.

Just need to get the legend completed for night theme and it'll be ready for release.