I am not sure why surface=sand really needs to be on the ways. But even if surface=sand is on the ways mkgmap shouldn't be creating polygons from it if the ways aren't closed. As surface=sand can be used for ways or areas. I might send a message to the original creator of the ways to ask if they mind If I remove the surface=sand as it isn't fully accurate anyway. Markus_g -----Original Message----- From: mkgmap-dev-bounces@lists.mkgmap.org.uk [mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk] On Behalf Of Charlie Ferrero Sent: Saturday, 8 January 2011 6:58 PM To: Development list for mkgmap Subject: [mkgmap-dev] Multipolygon problem Hello all, I have the following rule in my polygons style: surface=sand [0x1b resolution 20] The problem is the following multipolygon: http://www.openstreetmap.org/browse/relation/1221199 This is a complex multipolygon which, in certain sections, uses the coastline to define the outer. Parts of the coastline (and therefore parts of the multipolygon) have the key/tag pair surface=sand The result is that mkgmap attempts to build a multipolygon for Port Philip Bay and fill it with sand, which is not ideal: http://www.cferrero.net/maps/img/1.png What I can't figure out is how to adjust my polygon style rules to avoid this happening. Or tell mkgmap not to process multipolygons of type natural=bay Neither of the following two variations of the rule makes any difference: surface=sand & natural!=coastline [0x1b resolution 20] surface=sand & type=!multipolygon [0x1b resolution 20] Nor does natural=coastline & surface=sand {delete surface} make any difference whether I put it in the lines file or the polygons file Does anyone have a suggestion on how to fix this? Thanks! -- Charlie _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev