You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Author: tom[at]compton.nu [Added to the original trac issue at 3.06pm, Wednesday, 13th August 2008]
There is a substantial difference of opinion on the correct was to use a multipolygon relation which may be partly to blame here. Jon is the expert, so I'll push this over to him.
Author: vrabcak [Added to the original trac issue at 3.11pm, Wednesday, 13th August 2008]
Replying to [comment:1 tom[at]compton.nu]:
There is a substantial difference of opinion on the correct was to use a multipolygon relation which may be partly to blame here. Jon is the expert, so I'll push this over to him.
I dont think that this is the issue, because multipolygon buildings are rendered correctly.
Author: jburgess[at]uklinux.net [Added to the original trac issue at 6.26pm, Wednesday, 13th August 2008]
It fails to render correctly because the inner rings are clockwise. The current Wiki definition of multipolygons says this should be acceptable but this does not work with mapnik. I'll look at fixing up the ring direction during the osm2pgsql conversion process.
Reporter: vrabcak
[Submitted to the original trac issue database at 11.06am, Wednesday, 13th August 2008]
Compare mapnik and osmarender view at following link:
http://www.openstreetmap.org/?lat=49.6852&lon=16.0083&zoom=14&layers=B00FTF
It is obvious that Mapnik doesnt render hole in multipolygon forest. The same problem is also in other areas with multipolygon relations on forests.
The text was updated successfully, but these errors were encountered: