There is about ~1600 object tagged piste:type=yes in the database.
This value is undocumented, and it’s hard to give it a meaning (‘yes’ is not a ‘type’).
I’ve created a Maproulette challenge to browse through these elements and guess the original meaning of the mapper.
What I have seen so far:
Error due to editor auto-completion from taginfo
In that case, it’s pretty straightforward to replace it with one of these values with a bit of research or directly by infering the type from connection with neighbouring ways.
Small connection between pistes, or between a piste and a lift
Here piste:type=connection can be used, or just prolonging the existing pistes.
Small areas around baby-lifts
What about piste:type=downhill or piste:type=downhill;sled and piste:difficulty=novice, area=yes ?
Landuse paving
If really one is into landuse paving, landuse=winter_sports is as good a tag as any.
Thanks for the suggestion. I have looked at the few cases in the area I know. I was able to discover two “issues” there, which in my view could be easily corrected.
The whole ski area was tagged with piste:type=yes instead of landuse=winter_sports
A single section (way) of a longer piste with correct tags was tagged with piste:type=yes, the rest correctly with piste:type=downhill or piste:type=nordic.
I think that’s a good idea. I also discovered one case in southern Germany where a small slope with only one single rope lift was entered as piste:type=yes, I changed it exactly the same way.
I’m always a bit unhappy with this tag, as I think it leads to an overlap. I would say most areas of a ski resort are agricultural meadows (landuse=meadow). Here in the Alps, the landuse=winter_sports is therefore generously drawn as a separate outline around the entire ski area.
Seems like piste:type=yes is the highway=road of pistes, meaning “there is a piste here of unknown type”. This sort of general tag should get replaced with a more specific tag as soon as the type can be determined, but I don’t think that means deprecation is warranted.
Ok, now I understood how Id proposes this preset.
In my opinion this particular preset is not really useful, there’s plenty of options easily discoverable in the pistes presets to choose a meaningful piste:type value. But that’s a discussion for Id tagging schema.
The alternatives proposed above, are not that complicated, and that’s also why I thought of proposing them in a wiki page to propose alternatives.
Funny thing - I did introduce the general piste preset myself (commit ). Not sure Id was filling in ‘yes’ as default at the time, but this was clearly not my intention
It might be to do with how the piste:type field is of type typeCombo. If I understand the documentation correctly, then changing it to combo should get rid of the default =yes.
