logo separator

[mkgmap-dev] Multipolygon problem

From Markus_g markus_g at bigpond.com on Sat Jan 8 10:07:19 GMT 2011

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.



-----Original Message-----
From: mkgmap-dev-bounces at lists.mkgmap.org.uk
[mailto:mkgmap-dev-bounces at 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:

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:

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 

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?


mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk

More information about the mkgmap-dev mailing list