<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 Carlos,<br><br>I was not able to reproduce the problem.<br>Please post a link to a tile for that mkgmap produces wrong messages.<br><br>Gerd<br><br><div>> Date: Fri, 21 Feb 2014 22:31:19 +0100<br>> From: cdavilam@orangecorreo.es<br>> To: mkgmap-dev@lists.mkgmap.org.uk<br>> Subject: Re: [mkgmap-dev] Wrong turn restriction warnings<br>> <br>> <br>> El 21/02/14 20:57, GerdP escribió:<br>> > Hi Carlos,<br>> ><br>> > you say that you see the message for the turn restriction in mkgmap.<br>> Right<br>> > If one of the ways of relation 1610018 crosses the tile border,<br>> > splitter will write all members of the relation to both tiles, but it<br>> > is only usable in the tile that contains the via point.<br>> Restrictions are correctly processed when a route is calculated, no <br>> problem there. The warning is not reported for the tile that contains <br>> the restriction (or the via point), but for the neighbor one. Would it <br>> be possible to detect that a restriction is fully contained in given <br>> tile and avoid such warnings in the neighbor one?<br>> The main concerns are the waste of time trying to fix restrictions <br>> reported by mkgmap that are correct in OSM and the bad experience of <br>> people who download errors files from my site and faces a list full of <br>> false errors, which for sure will dis encourage them to continue working <br>> on their fix.<br>> Carlos<br>> ><br>> > Gerd<br>> ><br>> ><br>> > Carlos Dávila-2 wrote<br>> >> Not sure what you mean. See attached screenshot for relation 1610018.<br>> >> It's placed on the crossing below label "CL-501". Tile border is the<br>> >> vertical gray line on the left, so some 800 meters. overlap=auto<br>> >><br>> >> El 21/02/14 19:31, GerdP escribió:<br>> >>> Hi Carlos,<br>> >>><br>> >>> is the via point within the tile border? If not, it should be ignored.<br>> >>><br>> >>> Gerd<br>> >>><br>> >>><br>> >>> Carlos Dávila-2 wrote<br>> >>>> Some of the turn restriction warnings reported by mkgmap are correctly<br>> >>>> mapped in OSM. They all seem to be near tile borders. Shouldn't<br>> >>>> keep-complete option of splitter take care of these relations?<br>> >>>> If you want to check some of these relations, here is the list I<br>> >>>> currently get processing a customized spain.osm.pbf file (I can supply<br>> >>>> the file if necessary) (max-nodes=2100000):<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1610018<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/2556829<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/2556828<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1619758<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1619754<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1619760<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1874949<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1471323<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/2733411<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1553991<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1553985<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1554001<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/3499015<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1874952<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1874950<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/3121764<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/2512039<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/3328204<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/3395687<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/3395691<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/3395685<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/3009483<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/3009481<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/3497275<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/2074869<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/3103660<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1694535<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1694528<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1694526<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/1694533<br>> >>>> Turn restriction http://www.openstreetmap.org/browse/relation/3526934<br>> >>>> _______________________________________________<br>> >>>><br>> >><br>> >> _______________________________________________<br>> >> mkgmap-dev mailing list<br>> >> mkgmap-dev@.org<br>> >> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev<br>> >><br>> >> MapSource.png (7K)<br>> >> &lt;http://gis.19327.n5.nabble.com/attachment/5797034/0/MapSource.png&gt;<br>> ><br>> ><br>> ><br>> ><br>> > --<br>> > View this message in context: http://gis.19327.n5.nabble.com/Wrong-turn-restriction-warnings-tp5797029p5797041.html<br>> > Sent from the Mkgmap Development mailing list archive at Nabble.com.<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>