<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>For unpaved paths I would tag width of a path, not width of free space on sides of a path.<br></div><div><br></div><div>Second may be tempting in dense forest where bushes and overgrowth may be important,<br></div><div>but would result in weird cases where there is large amount of free space on sides.<br></div><div><br></div><div><a href="https://upload.wikimedia.org/wikipedia/commons/f/f6/Czerwone_Wierchy_widok_w_stron%C4%99_Tatr_Wysokich.jpg">https://upload.wikimedia.org/wikipedia/commons/f/f6/Czerwone_Wierchy_widok_w_stron%C4%99_Tatr_Wysokich.jpg</a><br></div><div>path is wide here, but not 100m wide<br></div><div><br></div><div>May 22, 2020, 13:42 by westis@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div>And yeah, the MTB preset bundle for JOSM has one preset for singletrack (width=0.5m) and one for doubletrack (width=2.5m), although the latter is highway=track. I suppose there's no need to be more detailed than within 0.5m in either case. But I'm still interested in the general principle of looking only on the treaded path on the ground or the "space" available for the path more generally.<br></div></div></blockquote><div><br></div> </body>
</html>