Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #42021
    vsa
    vsa
    Participant

    Hi ChristianK, is possible convert and display on the map this node? (for example as wayside_cross)

    Node with old stone

    /*
    Picture of similar stone:
    example
    */

    Thank you
    Vit

    • This topic was modified 5 months, 2 weeks ago by vsa vsa.
    • This topic was modified 5 months, 2 weeks ago by vsa vsa.
    #42034
    Tobias
    Tobias
    Moderator

    Hi Vit,
    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…
    Best regards,
    Tobias

    Developer of Elevate mapstyle

    1 user thanked author for this post.
    vsa vsa
    #42388
    vsa
    vsa
    Participant

    Yes, add historic=stone and historic=rune_stone. Display on map as a standard historic=wayside_cross

    #42411
    Tobias
    Tobias
    Moderator

    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 mapstyle

    #42537
    ChristianK
    ChristianK
    Keymaster

    added historic=stone

    1 user thanked author for this post.
    vsa vsa
    #42768
    Tobias
    Tobias
    Moderator

    added historic=stone

    Just checked the tagmapping – we’ve now got:
    historic=memorial, memorial=stone
    historic=stone
    I am afraid this needs some correction for the common value bug, e.g. historic=hist_stone

    Developer of Elevate mapstyle

    #43012
    Tobias
    Tobias
    Moderator

    added historic=stone

    Is now shown with Elevate 4.5

    Developer of Elevate mapstyle

    1 user thanked author for this post.
    vsa vsa
    #43061
    JohnPercy
    JohnPercy
    Participant

    What about Tobias’s previous point about the common value bug?

    #43069
    JohnPercy
    JohnPercy
    Participant

    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.

    #43071
    Tobias
    Tobias
    Moderator

    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.
    #43101
    ChristianK
    ChristianK
    Keymaster

    done

    historic=hist_stone EQ stone

    2 users thanked author for this post.
Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.