Author: pishmishy
[Added to the original trac issue at 5.05pm, Thursday, 24th February 2011]

aeroway=runway is a tag that's documented as applying to ways and not areas. The rendering should reflect the documentation and not try and preempt how the tag's usage may or may not change.

The change in rendering caused by Changeset #25298 messed up the mapping in some areas where I'd mapped perimeter taxi ways as a continuous loop. Perhaps I was wrong in doing this, I don't know :( My suggestion would be to revert the change and give this some more thought as to what people had intended to represent with existing circular taxi ways.

Author: Ldp
[Added to the original trac issue at 6.42pm, Thursday, 24th February 2011]

Since many of the aeroway=* tags can and do apply to areas, we handle it as areas by default. This means that once it forms a closed loop, we see it as area. This hadn't been applied to taxiway yet, but now has. You can prevent this by setting area=no.

This doesn't help just the renderer, but any data user that processes your data. It makes it unambiguous just what you intended to represent with that closed way.

PS: Can you supply a link to your example? I'm curious why a closed loop would've rendered as circular way instead of area before, when I would expect we wouldn't have rendered it at all (due to the missing area handling, but closed loops ending up in the polygon table).

Author: pishmishy
[Added to the original trac issue at 1.48pm, Monday, 28th February 2011]

http://www.openstreetmap.org/?lat=51.6878&lon=-1.30249&zoom=15&layers=M and
http://www.openstreetmap.org/?lat=51.87873&lon=-1.21614&zoom=16&layers=M

(I've split the circular way for now)

Author: Ldp
[Added to the original trac issue at 10.41pm, Wednesday, 16th March 2011]

You can also add area=no instead of splitting it. That makes it clear to data end users what you mean.

Author: math1985
[Added to the original trac issue at 12.17am, Sunday, 30th March 2014]

This has been resolved in the meanwhile.