Author: crschmidt[at]crschmidt.net
[Added to the original trac issue at 7.00pm, Saturday, 2nd December 2006]

Unfortunately, the OSM data doesn't make this possible, because that is not a 'closed' way. I have no way of knowing where the thames should be filled in.

(This is a case where a human can see it easily, and a computer can't see it at all.)

Author: osm[at]randomjunk.co.uk
[Added to the original trac issue at 12.25pm, Monday, 4th December 2006]

Replying to [comment:1 crschmidt[at]crschmidt.net]:

Unfortunately, the OSM data doesn't make this possible, because that is not a 'closed' way. I have no way of knowing where the thames should be filled in.

(This is a case where a human can see it easily, and a computer can't see it at all.)

Osmarender manages to do it by simply tracing round the segments' start and end points in segment order. This jumps the gaps and effectively closes the way. The whole river is done like this where the north and south banks form way sections that can be closed and filled by the renderer -- all the segments are correctly ordered in their ways for this to happen.

Dunno whether the riverbank tag is being used elsewhere where this shouldn't happen though... I haven't seen anywhere where it breaks anything yet.

Author: bruce.cowan[at]dsl.pipex.com
[Added to the original trac issue at 9.01pm, Wednesday, 21st March 2007]

Fixed.