<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>May 26, 2020, 20:50 by bradhaack@fastmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>Yes! We have an overload of tags for trails, many poorly defined, many rarely used. KISS - keep it simple stupid. I think it would help if we narrowed the focus for cycleway and footway.<br></div><div>How about this, as default:<br></div><div>cycleway - paved path that a typical tourist or casual rider can ride on a road bike.<br></div><div>footway - smooth path, very firm surface or paved that is good for someone with less than average ability.<br></div><div>bridleway- for exclusive (or almost exclusive ) horse trails<br></div><div>path - for everything else. Implies not paved. Routers should not route road bikers here.<br></div><div><br></div><div>The difficulty for bikes (& maybe hiking) can be simple green/blue/black similar to what is used on US bike trails, and ski areas.<br></div></blockquote><div><br></div><div>The tricky part is that such redefining is not solving problem of already collected data.<br></div><div><br></div><div>You need to resurvey all already collected data and mark it as reviewed (by adding some tag,<br></div><div>for example reviewed_to_new_path_scheme=yes or explicit surface value).<br></div><div><br></div><div>Overall I see no benefit over explicit tagging of a surface value.<br></div><div><br></div> </body>
</html>