February 16, 2021 at 19:53 #42021
vsaParticipantFebruary 16, 2021 at 21:16 #42034
so you mean we should add historic=stone?
That would be the fourth stone (after historic=boundary_stone, natural=stone and memorial=stone), and there’s also historic=milestone and historic=rune_stone. Might make sense to combine some of these, at least in rendering…
Developer of Elevate mapstyleMarch 7, 2021 at 19:21 #42388
Yes, add historic=stone and historic=rune_stone. Display on map as a standard historic=wayside_crossMarch 8, 2021 at 20:12 #42411
As historic=stone can have a lot of different shapes without crosses, it makes more sense to render it like historic=boundary_stone
Developer of Elevate mapstyleMarch 15, 2021 at 13:45 #42537April 3, 2021 at 14:05 #42768
Just checked the tagmapping – we’ve now got:
I am afraid this needs some correction for the common value bug, e.g. historic=hist_stone
Developer of Elevate mapstyleApril 21, 2021 at 21:19 #43012April 24, 2021 at 00:14 #43061
What about Tobias’s previous point about the common value bug?April 24, 2021 at 09:52 #43069
PS I’ve realised that there is a possible workaround in this case:
<rule e="any" k="historic" v="stone"> <rule e="any" k="memorial" v="~">
Which catches historic stones which are not memorials and allows memorial stones to be caught separately.April 24, 2021 at 09:56 #43071
Christian has some more important things on his plate since some months, so it can take some time for those details to be fixed. But nice workaround for the moment, in the end a separate value will be better though.
Developer of Elevate mapstyle
1 user thanked author for this post.April 25, 2021 at 09:25 #43101
You must be logged in to reply to this topic.