<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>25 cze 2022, 23:48 od ezekielf@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div>Thanks for the reply, marc_marc.<br></div><div dir="ltr"><div><br></div><div>On Sat, Jun 25, 2022 at 5:06 PM Marc_marc <<a target="_blank" href="mailto:marc_marc@mailo.com" rel="noopener noreferrer">marc_marc@mailo.com</a>> wrote:<br></div></div><div class=""><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class=""><div>imho the best it to tag what a sign said :<br></div><div> if all mode need a permit, access=permit is fine and enought<br></div><div> if the sign is only for snowmobile, tag as sutch without any generic <br></div><div> access rule<br></div></blockquote><div><br></div><div>Let's imagine the sign says "designated snowmobile trail - permit required". So what I would want to tag is snowmobile=designated + snowmobile=permit in order to capture both facts. However that is not possible due to the key conflict. What to do? <br></div></div></div></blockquote><div dir="auto">tag more restrictive one, maybe snowmobile trail can be tagged as route relation if it exists <br></div><div dir="auto"><br></div><div dir="auto">or invent a new extra tag and add it (and maybe document it)<br></div><div dir="auto"><br></div><div dir="auto">Maybe snowmobile=permit implies that it is designated as snowmobile trail,<br></div><div dir="auto">at least typically<br></div> </body>
</html>