Author: TomH
[Added to the original trac issue at 12.26am, Saturday, 6th February 2010]

If you actually choose osmarender as the component instead of just typing it into the keywords then the bug will get sent to the right place...

Author: yvecai
[Added to the original trac issue at 10.09am, Saturday, 6th February 2010]

Didn't I? Sorry, it was late.

Yves

Author: osm[at]petschge.de
[Added to the original trac issue at 10.43am, Thursday, 13th May 2010]

I suspect that this is really a bug in the tiled design of tiles@home. If you were able to render the whole planet at once using osmarender the relation should render just fine.

Author: HamishB
[Added to the original trac issue at 9.08am, Wednesday, 19th May 2010]

more examples:
http://osm.org/go/EAmUNR_V-?layers=0B00FTF
http://osm.org/go/EAk4alvA-?layers=0B00FTF
http://osm.org/go/EAltREK?layers=0B00FTF

It's in very large multipolygon relations (>10k nodes, split into 495 nodes per way). AFAICT JOSM's Validator doesn't find any problems. All looks good in the online Mapnik tiles, just the Osmarender tiles go funny.

thanks,
Hamish

Author: rammer
[Added to the original trac issue at 11.12am, Friday, 23rd July 2010]

I did some poking around with this and it seems that the large multipolygons get rendered correctly if the osm file fed to osmarender contains all the members of the multipolygons that intersect the tile to be rendered.
For example tile http://tah.openstreetmap.org/Browse/details/tile/12/2318/1149/
It contains relation http://www.openstreetmap.org/browse/relation/445107
Osmarender downloads

And therefore not all members of relation 445107 is included. If I open the same bounding box in josm and download all the members of that relation, save the data and using that render the same area I get a perfect render.

So you need to somehow coax osmarender to recursively download all members of the multipolygons in the tile to be rendered. Using something like http://www.openstreetmap.org/api/0.6/relation/445107/full

Author: osm[at]deelkar.net
[Added to the original trac issue at 11.56am, Sunday, 19th September 2010]

Applied Patch by Irrfahrt as r23267. Clients will start updating shortly.