<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 10-Oct-17 02:24 AM, Martin
Koppenhoefer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABPTjTDELWxu=LZHyBCz+94josnQboP05rXpPfWN8Z76zA7Z1g@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div class="gmail_quote">If the same runway-like feature
needs<br>
to be tagged differently depending on if it is located
within an<br>
airport of not (by whatever definition of airport) that is
not a very<br>
good idea for tagging.</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>I didn't write this definition, but to me it seems to be
intended as a shortcut to say: "within a managed structure,
with associated infrastructure, managed, etc.", so clearly
the "same" runway in an airport and without any airport in
proximity is not the "same" thing. <br>
</div>
<div><br>
</div>
<div> </div>
<div class="gmail_quote"><br>
</div>
<div class="gmail_quote">more constructively, you have
suggested to tag airstrips as kind of runway, what about
tagging them as kind of aerodrome? There are "already" 14
instances of<br>
<br>
aerodrome:type=airstrip</div>
<div class="gmail_quote"><br>
</div>
<div class="gmail_quote">in the data, while the runway key is
mostly used for parts of the runway (like blast pads).</div>
</div>
<div class="gmail_extra"><br>
</div>
</div>
</blockquote>
<br>
In these 'airstips' there are no services - taxiways, etc.<br>
I simply tag them as aeroway=runway. <br>
But without any other areoway tags. So they don't get
areoway=areodrome nor anything else. <br>
If they have services for aircraft then I'd add other tags. <br>
</body>
</html>