Hey, just a quick FYI. I'm aware that piste and highway features can share the same way, and they don’t necessarily need to be overlaid. In theory, the tags should be structured in a way that clearly distinguishes which tags belong to which feature when they share the same way. However, I've noticed that in practice, many systems don’t always interpret these distinctions correctly. For instance, even if the piste:name tag is present on a way, the name tag is often used in its place.

There are cases where the names of roads, trails, and pistes differ. When this happens and the name tag is applied to both, it can introduce small inaccuracies. I’ve found that if I separate the piste into its own track, I can use both the piste:name and the name tag to ensure that the name of the piste gets applied accurately by the system interpreting the tags.

To help prevent misinterpretation, I sometimes overlay a piste way on top of roads or trails to make the distinction as clear as possible. However, I’ve seen some cases where people will then re-combine the two ways back into one. While this isn’t technically incorrect as you've mentioned, it can lead to issues with how the tags are interpreted by systems that might struggle with these distinctions.

I understand that we're not supposed to map with a specific interpretation in mind, but my approach isn’t about shaping the map for any one system. Rather, it’s about mapping in a way that reduces the chance of any system misinterpreting the tags.

I just wanted to share the reasoning behind my decision to overlay the piste.