Betrachte 11 Beiträge - 1 bis 11 (von insgesamt 11)
  • Autor
    Beiträge
  • #42021
    Avatar-Fotovsa
    Teilnehmer

    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

    #42034
    Avatar-FotoTobias
    Administrator

    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 Teilnehmer(n) gefällt dieser Beitrag
    #42388
    Avatar-Fotovsa
    Teilnehmer

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

    #42411
    Avatar-FotoTobias
    Administrator

    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
    Avatar-FotoChristianK
    Administrator

    added historic=stone

    1 Teilnehmer(n) gefällt dieser Beitrag
    #42768
    Avatar-FotoTobias
    Administrator

    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
    Avatar-FotoTobias
    Administrator

    added historic=stone

    Is now shown with Elevate 4.5

    Developer of Elevate mapstyle

    1 Teilnehmer(n) gefällt dieser Beitrag
    #43061
    Avatar-FotoJohnPercy
    Teilnehmer

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

    Voluntary and Velocity themes - https://voluntary.nichesite.org

    #43069
    Avatar-FotoJohnPercy
    Teilnehmer

    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.

    Voluntary and Velocity themes - https://voluntary.nichesite.org

    #43071
    Avatar-FotoTobias
    Administrator

    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 Teilnehmer(n) gefällt dieser Beitrag
    #43101
    Avatar-FotoChristianK
    Administrator

    done

    historic=hist_stone EQ stone

    2 users thanked author for this post.
Betrachte 11 Beiträge - 1 bis 11 (von insgesamt 11)
  • Sie müssen angemeldet sein, um zu diesem Thema eine Antwort verfassen zu können.