Talk:Tag:route=piste
Amout of "start" child elements According to the current wiki page, route=piste may have exactly 0 or 1 "start" child element. The former route=ski allows 0 or more which is IMHO more realistic, because many roundtrip pistes (e.g. cross country skiing) have multiple possible start points - usually wherever they pass nerby a parking or public transport station. Any argument against allowing more than 1 start point? --Schoschi (talk) 14:12, 5 March 2020 (UTC)
- I don't see that on the current page. The table for members says "start | zero or more | entry points", so that seems fine? --Jeisenbe (talk) 07:45, 7 March 2020 (UTC)
Considerable differences between DE and EN variants of the page
There are two considerable differences between DE and EN variants of the page:
1) EN forbids to use piste tags on areas while DE encourages that. See discussion at https://forum.openstreetmap.org/viewtopic.php?pid=817248
2) EN forbids keys piste:difficulty and piste:grooming on the relation while DE does not. I do not see good reasons to forbid both keys on the relation. Instead, I do welcome it because it makes it quick & easy to see e.g. an 20km XC trail's overall difficulty & grooming compared to having to look it up at each of the dozens of parts/segments/ways. What speaks against allowing it?
--Schoschi (talk) 17:06, 29 January 2021 (UTC)
Lanes?
"Tags for the associated ways" - what is the meaning of lanes=* here? How many traffic lanes there are on a given road or something else?
If something else - note that a different tag should be selected, see for example https://www.openstreetmap.org/way/464186116 where tag used in two different meaning would conflict Mateusz Konieczny (talk) 14:46, 1 February 2021 (UTC)
- For something else but there is no conflict :) Lanes make only sense for some few piste types, for example classic cross country skiing which is done in tracks/lanes (see e.g. https://commons.wikimedia.org/wiki/File:Hoherbrand_loipe.jpg). For a pure nordic piste (i.e. one that is no path/street/track/whatever in summer time but just somewhere on the grass, for example https://www.openstreetmap.org/way/668030436), lanes=* can only mean these skiing tracks/lanes, so the key is not ambigous, similar like for cycleways which are also not roads but still carry lanes=* in a clearly understandable fashion. For a nordic piste that is a forestry track in summer time, lanes=* is - to my observation - quite strictly used for the lanes of the forestry track. In order to still map the amount of tracks of the nordic piste, the specialized key piste:lanes=* is provided on the way and/or the key lanes=* in the piste's relation (e.g. https://www.openstreetmap.org/relation/9341450) - both not ambigous, and all 3 variations (way + both + relation) have their pro & con so there is no clear favorite AFAIK. --Schoschi (talk) 22:00, 1 February 2021 (UTC)
