[Tilesathome] Rendering problems with natural=riverbank

[D Tucny]

2008/12/17 Andre Hinrichs <andre.hinrichs at gmx.de>

> On Dienstag, 16. Dezember 2008, D Tucny wrote:
> > Hi,
> > I've noticed some problems with rendering of natural=riverbank... In both
> > cases, the data looks ok...
> >
> > 1) The fill seems to be somewhat uneven...
> > e.g.
> >
> http://www.openstreetmap.org/?lat=29.83023&lon=120.27809&zoom=15&layers=0B0
> >0FTTTT
> >
> > It appears that it's being broken up into multiple smaller polygons that
> > aren't joined together...
> >
> > 2) Quite a few sea tiles have appeared where natural=riverbank has
> replaced
> > natural=coastline...
> > e.g.
> >
> http://www.openstreetmap.org/?lat=29.725&lon=120.2587&zoom=12&layers=0B00FT
> >TTT
> >
> > Some of the text of the place name is visible, so it is getting rendered,
> > but, it's flooded...
>
> These are bugs in the oceantiles. The area you mentioned is currently
> beeing
> rerendered. There are still loads of these bugs in the oceantiles and some
> of
> us are currently working hard on fixing them. Hopefully someday, when all
> coastlines are defined properly, there will be an automatic process
> creating
> the oceantiles, but today, this is still made by hand...
>

I guess that could explain the entire tile showing as flooded (problem 2)
but it can't account for problem 1 can it?


>
> BTW, it's waterway=riverbank, not natural=riverbank...
>

Oops, thankfully the ways are tagged correctly, just my email that isn't ;)

d
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tilesathome/attachments/20081217/a0650911/attachment.html>