January 6, 2022 at 15:49 #46714karlchickParticipant
Oooh, another tag I’ve been wanting see in OAMs for ages is, as well as the additional ones in the previous posts , is:
– node: k=”natural”, v=”tree”
These have been available in LoMaps, and are very common to see on OS maps too.
Here is an example in OSM:
I see that natural=tree is listed in the tag-mapping for v5 (I think also v3, v4), but I never see any trees at locations given in OSM when trying render natural=tree in any version of OAM.
January 6, 2022 at 16:24 #46720ikomsParticipant
- This reply was modified 7 months, 1 week ago by karlchick.
Trees are only visible on the map when they are a natural monument…
You can search the forum for natural=tree. There was some talking about some years ago.
1 user thanked author for this post.January 7, 2022 at 09:37 #46745karlchickParticipant
Hmm… while I do understand the concern with micromapping of trees, I’m not convinced that this is an issue. It should be up to the theme’s rules to decide when to display lone trees. I have the exact same issue with many other tags already in OAM, e.g. gardens are often micromapped and you will often see a whole neighborhood of residential housing with each garden tagged. In my theme I have decided to use rules to filter for gardens that have public access and are listed as leisure or tourism.
If all natural=tree map items were in the OAM data, you would still be able to choose to only display those with name=”*” to limit display to monument trees. And, if you want to keep trees out of cemeteries then use a rule to filter which trees to display, for example LoMaps only show trees when k=”natural” has a value.
I would also like the option to lone display trees, especially in flat open countryside where they are often the only prominent/tall landmark when navigating. If LoMaps is able to do it, why not OAM?January 29, 2022 at 13:07 #47128ManfredParticipant
See in “TagTransform”:
For maps from 15th of June 2015:
Bugfix for natural=trees
These nodes were deleted so far if they don’t contain additional tags.
If a node in a MultiPolygon contained such a tree at the connection beteween two members of the MP the MP broke.
Now the node is preserved, only the tag natural=tree is deleted FROM the node.
Thanks a lot to Richard who reported this issue and helped to identify of the Bug.Verwendete Software: Oruxmaps (immer die neueste incl. Beta)
January 29, 2022 at 21:37 #47143TobiasKeymaster
- This reply was modified 6 months, 2 weeks ago by Manfred.
I would also like the option to lone display trees, especially in flat open countryside where they are often the only prominent/tall landmark when navigating
Landmark trees are shown if mapped correctly, see tagtransform; every natural=tree which has either historic=tree_shrine, denotation=natural_monument, denotation=landmark or name=* is contained in the map.
If LoMaps is able to do it, why not OAM?
When OAM was started, all natural=tree were contained, and those were in almost every case significant trees in the sense you are looking for. But this changed with micromapping, and so the map content was changed to keep those usable. If we change it now again, all themes would need to be changed and lots of content which would be mainly filtered in themes would be added.
So I think it makes sense to keep it like it is and maybe just add some more exceptions, but there’s no need to have all trees in the maps.
Developer of Elevate mapstyle
- You must be logged in to reply to this topic.