[JohnPercy]

Should leaf_cycle be included in the maps as well as leaf_type?
For a casual observer like me they seem to describe the same sort of thing and for our mapping purposes could possibly be treated as equivalent. A wood I was looking at had a value for leaf cycle rather than leaf type.

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

[Tobias]

I think that’s not so easy:

1 – Beech forest: leaf_type=broadleaved and leaf_cycle=deciduous

2- Larch forest: leaf_type=needleleaved and leaf_cycle=deciduous

3 – Spruce forest: leaf_type=needleleaved and leaf_cycle=evergreen

So depending on the tag used 2 renders like 1 or 3.
In German a forest is categorized by leaf_type (Laubwald, Nadelwald, Mischwald), maybe that’s different in other languages?

For your case I would say it’s a mapping issue if leaf_type is missing.

Developer of Elevate mapstyle

2 Teilnehmer(n) gefällt dieser Beitrag

ChristianK, JohnPercy

[JohnPercy]

I take the point, though mapping and rendering woods is not necessarily as straightforward as that. For instance the Elevate theme treats leaf type=deciduous and leaf type=broadleaved as equivalent, thus failing on larch. 🙂 I guess deciduous really belongs on leaf cycle.

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

[Tobias]

JohnPercy wrote:

For instance the Elevate theme treats leaf type=deciduous and leaf type=broadleaved as equivalent, thus failing on larch.

leaf_type=deciduous is only included as equivalent in tag-mapping, probably for wrong/sloppy mapping (when leaf_type was introduced and wood=deciduous/coniferous – what a mess 😉 – was deprecated).
So the rules in Elevate treat the old messy wood=deciduous the same as the new leaf_type=broadleaved, leaf_type=deciduous does not work with current tag_mapping. I don’t know how larch should be tagged in wood=*, probably that’s why it’s deprecated 🙂

Developer of Elevate mapstyle

• Diese Antwort wurde vor vor 3 Tage, 3 Stunden von Tobias bearbeitet.

[Autor]

Beiträge