<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div style="16px" text-align="left"><br></div><div style="16px" text-align="left">9 lip 2019, 18:12 od richard@systemed.net:</div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div style="16px" text-align="left">80% of the time surface= is all you need. We could do with more and better<br></div><div style="16px" text-align="left">documented values for it, especially for clarity around gravel. I could see<br></div><div style="16px" text-align="left">some virtue in another tag to be used _only_ when surface= is also present,<br></div><div style="16px" text-align="left">documenting how well the surface is maintained, so that you could<br></div><div style="16px" text-align="left">differentiate between (say) potholey, broken-up asphalt and immaculately<br></div><div style="16px" text-align="left">maintained asphalt.<br></div></blockquote><div style="16px" text-align="left">What about smoothness tag combined<br></div><div style="16px" text-align="left">with surface=asphalt or<br></div><div style="16px" text-align="left">paving_stones?<br></div><div style="16px" text-align="left"><br></div><div style="16px" text-align="left">Is it also "die in fire" level of uselessness?<br></div><div style="16px" text-align="left"><br></div><div style="16px" text-align="left">I used smoothness tag in past to <br></div><div style="16px" text-align="left">indicate horribly bad asphalt/paving<br></div><div style="16px" text-align="left">stone alignments.</div><div style="16px" text-align="left"><br></div> </body>
</html>