Hi Henning, okay, first a correction : precompiled data is passed to the style (polygons), tags are natural=sea or natural=land (or the tag configured with --land-tag) If we also pass the osm data, we will have duplicate or heavily overlapping shapes, so I think it is a good idea to pass them only through the lines rules so that you can add coastlines, as this would not work with precompiled sea data. Another question is if that should also be done when option --coastlinefile is used, I don't know the content of such a file.
Gerd > Date: Thu, 13 Feb 2014 20:19:50 +0100 > From: [email protected] > To: [email protected] > Subject: Re: [mkgmap-dev] coastline boundaries > > Hi Gerd, > > processing the precompiled data through style isn't necessary. But I > would leave it to the style-dev to take care about rendering > natural=coastline also in polygon-file or not. After thinking some > minutes more, my approach isn't that better then yours, if you remove > the ignore function for polygon-file. > > Henning > > _______________________________________________ > mkgmap-dev mailing list > [email protected] > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
