<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Minko,<br><br>attached is a patch (works with trunk and high-prec-coord branch). <br>In combination with precomp-sea option<br>ways with natural=coastline <br>are kept as is, but they are only processed by the lines rules.<br><br>A compiled binary (branch version) is here:<br><code>http://files.mkgmap.org.uk/download/177/mkgmap.jar</code><br><br>Please note that this contains many changes regarding routing, so <br>please use with care.<br><br>Gerd<br><br><div>> Date: Thu, 13 Feb 2014 09:16:10 +0100<br>> From: ligfietser@online.nl<br>> To: mkgmap-dev@lists.mkgmap.org.uk<br>> Subject: Re: [mkgmap-dev] coastline boundaries<br>> <br>> Thanks Gerd!<br>> <br>> <br>> > I discussed that with WanMil in a pm. I'll post a patch today.<br>> > <br>> > Gerd<br>> > <br>> > > Developers,<br>> > > Is it possible to give a mkgmap:coastline=yes (or some other) tag to<br>> > > those boundaries where the coastline has been (re)moved?<br>> > ><br>> > > Gerd wrote:<br>> > > > > I am not sure if I can help here.<br>> > > > > You use the precomp-sea option, that means that ways with<br>> > > > > natural=coastline are filtered in<br>> > > > > this way:<br>> > > > > a) the tag natural=coastline is removed from the original way<br>> _______________________________________________<br>> mkgmap-dev mailing list<br>> mkgmap-dev@lists.mkgmap.org.uk<br>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev<br></div> </div></body>
</html>