<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 28, 2020, 22:05 by kevin.b.kenny@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>So I return to, 'what's the minimalist set of attributes that we can<br></div><div>use to guide a data consumer, and conversely, the minimum set of tags<br></div><div>that a data consumer needs to recognize?' Specifying every attribute<br></div><div>in excruciating detail is fine if you're trying to map your area<br></div><div>artistically and say as much as possible; it shouldn't be necessary<br></div><div>for a mapper to do so, or for a data consumer to understand<br></div><div>everything, in order to get reasonable approximate results.<br></div></blockquote><div>Depends on what you want to achieve. <br></div><div><br></div><div>surface=* goes a long way toward distinguishing it,<br></div><div>but there are still unpaved park footways in city centers <br></div><div>and paved path inaccessible to many.<br></div><div><br></div><div>surface=* + wheelchair=no where applicable seems <br></div><div>to cover basically everything of what I mapped -<br></div><div>except unpaved paths in parks.<br></div> </body>
</html>