<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 3/10/2018 5:27 AM, Paul Johnson
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMPM96qa-vc1ho5yOzhSQjp8CrsHV=0bgp8DNB1JJoSrnimu7A@mail.gmail.com">
<div dir="auto">
<div><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mar 9, 2018 03:49, "Austin Zhu"
<<a href="mailto:austinzhu666@gmail.com"
moz-do-not-send="true">austinzhu666@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">Well, maybe there is someone who thinks
mapping runway as area is wrong? I think that both way
and area are OK, because the way element matches the
way we map taxiways. So it is useful when others need
to guide their plane using osm data(maybe in flight
simulator softwares). Mapping as area can show the
width of the runway and thus is more realistic. The
best method should be using both elements. Just like
highway objects. Obviously, the wikipage needs some
edit or restoration.</div>
</blockquote>
</div>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Map the runways and taxiways as linear (who
knows, someone might want to have a routable model for flight
simulators or similar games), and map the negative space
(grass infields, etc) as areas?</div>
</div>
<br>
</blockquote>
<br>
Eventually routers will have to deal with areas that are routable ..
pedestrian areas , step areas as well as runways that are areas. <br>
</body>
</html>