<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 28/11/2019 11:42, Paul Allen wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAPy1dOK9_RMfb_=i1LZcVCq_S5g7-9zWtVd0GrtSYoQX8jwwNQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Thu, 28 Nov 2019 at 10:56, Andy Townsend <<a
href="mailto:ajt1047@gmail.com" moz-do-not-send="true">ajt1047@gmail.com</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>OSM Carto, as far as I'm aware
<ul>
<li>Doesn't have a concept of 2-sided embankments or a
rendering for them<br>
</li>
</ul>
</div>
</blockquote>
<div>Does it need such a concept? I haven't tried it when the
embankment resembles an</div>
<div>arete, but for an embankment with a plateau all that is
needed is two embankments</div>
<div> delineating the plateau. <br>
</div>
</div>
</div>
</blockquote>
<p>Tagging 2 things to represent 1 physical feature just makes it
extra-hard for anyone consuming the data. They'd have to say "OK,
I've got a man_made=embankment here; now, before I decide what to
do with it, I have to see if there is another parallel one facing
the other way that tells me that what I've really got is a raised
flood bank or similar"</p>
<p>We represent other linear features (e.g. roads) as lines; it
makes sense to do the same here.</p>
<p>Best Regards,</p>
<p>Andy<br>
</p>
<blockquote type="cite"
cite="mid:CAPy1dOK9_RMfb_=i1LZcVCq_S5g7-9zWtVd0GrtSYoQX8jwwNQ@mail.gmail.com"></blockquote>
</body>
</html>