<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 WanMil,<br><br>I am just guessing. Will have a closer look tomorrow.<br><br>Gerd<br><br><div>> Date: Mon, 3 Feb 2014 20:19:46 +0100<br>> From: wmgcnfg@web.de<br>> To: mkgmap-dev@lists.mkgmap.org.uk<br>> Subject: Re: [mkgmap-dev] Problem with turn restriction<br>> <br>> > Hi WanMil,<br>> ><br>> > > > The problem probably only occurs with ways close to the tile<br>> > > > boundary that are clipped. I don't know if we can save a route<br>> > > > restriction when the to-node or from-node lies outside of the boundary.<br>> > ><br>> > > Would it solve the problem if the boundary nodes are added earlier just<br>> > > before the RestrictionRelation.addRestriction(MapCollector) is called?<br>> ><br>> > The boundary nodes are added for all ways before style processing, even for<br>> > all non-routable ways and shapes.<br>> > This wastes a few cpu cycles, but I don't see a problem or a solution here.<br>> ><br>> > Gerd<br>> ><br>> <br>> As far as I understand the to-node and the from-node are calculated by <br>> mkgmap. So I don't understand why there is a problem if the boundary <br>> nodes are available. Can you explain a bit more in detail?<br>> <br>> WanMil<br>> <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>