<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 29/03/19 20:12, Martin Koppenhoefer
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABPTjTC+=2i8tTrJuNu7zFOuEs_om1KHJbEVM--jUX0a3n9tTg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="ltr"><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Am Fr., 29. März 2019 um
08:28 Uhr schrieb Warin <<a
href="mailto:61sundowner@gmail.com" moz-do-not-send="true">61sundowner@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div class="gmail-m_4871537608694073383moz-cite-prefix">On
29/03/19 17:59, Martin Koppenhoefer wrote:<br>
</div>
<blockquote type="cite"> <br>
<div>can you explain how it relates to this proposal?</div>
<div><br>
</div>
<div><a
href="https://wiki.openstreetmap.org/wiki/Relations/Proposed/Area"
target="_blank" moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Relations/Proposed/Area</a></div>
<div><br>
</div>
</blockquote>
<br>
That proposal is very broad , it defines implicit areas of
any kind, steps, ramps, flat bits . I think that is too
much in one proposal to consider and detail.<br>
<br>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>As far as I see you proposed the same tagging for your
proposal, "type=area" for the relation, why so generic if
the scope is reduced to area steps?</div>
</div>
</div>
</blockquote>
Compatibility. If/when that goes ahead. <br>
<blockquote type="cite"
cite="mid:CABPTjTC+=2i8tTrJuNu7zFOuEs_om1KHJbEVM--jUX0a3n9tTg@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div> You are also including the same proposed roles and
concepts for the stairmodelling, "upper" and "lower". The
main difference to the original area relation proposal is
that you didn't add the other applications, like defining
implicit or adding explicit barrier features and punctual
exceptions to these barriers.<br>
</div>
</div>
</div>
</blockquote>
<br>
I think barriers on stairs could be simply added as separate ways.
This would allow for barriers to be across the stairs at any angle,
for any length, for any pattern. It requires no additional tags. <br>
Nor am I defining ramps, etc. Just steps is hard enough. <br>
</body>
</html>