February 25, 2021 at 14:55 #42195
It seems common to have some paths with piste:type=nordic, associated to one (or more) relations with route=piste (or route=ski) + piste:type=nordic (e.g. 24660872).
This results in two (or more) pistes drawn (my theme draw them semi transparently, with different colors).
It is normal to have multiple route relations for a single path (different loops sharing a common segment), and a dy offset can be used in the theme so different colors do not overlap; however, I don’t think the path itself should be drawn as a piste, when it is associated to a piste route.
Is this something that can be fixed when building the maps? Or is there something I can do in the theme file? Or maybe this is some incorrect osm tagging?
Thanks!February 27, 2021 at 09:47 #42225
I am not sure whether I understand correctly what your actual question is.
In the case, that there is a piste or piste relation associated with e.g. a path. Elevate *does* draw the way as path and then overlaid the piste. If you use dy= in the rule that draws the piste, you can show both next to each other with the offset.
Or do you want to distinguish between a piste as relation and piste as a path property?March 1, 2021 at 08:52 #42261
The problem is that the path, and the route relation, both have a piste:type=nordic tag, resulting in two pistes being drawn, possibly with different attributes. Maybe the piste:type should be removed from the path, if present in one or more route relations? And maybe other piste:* tags (i.e. piste:difficulty, or piste:grooming), if present on the path and not on the routes, should be removed from the path, and applied to the routes?
Thanks!March 3, 2021 at 11:51 #42280
That’s funny. It does not happen to me. If I offset the pistes in the pistes2 section in Elevate, all tracks and pathes are drawn as tracks and pathes and the pistes are offset, as it should be. So there is no problem in my case, if there is a piste:type=nordic on both track/path and in the relation.
In the wiki, there is no clear rule, whether piste:type grooming, oneway and difficulty should be on the way or in the relation (or both). I rather put in on the way, as the direction and the difficulty may change and the type, of course, in both.
Best regards, ReinerMarch 3, 2021 at 16:49 #42288
It is harder to notice with Elevate, as there is no multiple piste:difficulty rule; however, when pistes are drawn twice, the semi-transparent color appears more opaque than it should.
Try with this to make it much more visible:
<rule cat="sports" e="way" k="piste:type" v="nordic" zoom-min="14"> <rule e="way" k="piste:difficulty" v="*"> <line stroke="#55ff0000" stroke-width="0.6" stroke-dasharray="20,15" stroke-linecap="butt" dy="1"/> </rule> <rule e="way" k="piste:difficulty" v="~"> <line stroke="#550000ff" stroke-width="0.6" stroke-dasharray="20,15" stroke-linecap="butt" dy="2"/> </rule> </rule>March 3, 2021 at 21:12 #42305
In the wiki, there is no clear rule, whether piste:type grooming, oneway and difficulty should be on the way or in the relation (or both)
Have a look here:
Tags for the associated ways
These tags (among others) are properties of the underlying ways (i.e. elements of the relation) and thus should be applied to the ways and not to the relation:
Developer of Elevate mapstyle
1 user thanked author for this post.
You must be logged in to reply to this topic.