<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 Steve,<br>> Nice simple test case. I can reproduce on a similar version of mapsource<br><div>> that you used, but not on an older version.<br>> <br>> > I hope you can reproduce the problem and find out what goes wrong...<br>> <br>> Interestingly if set to shortest time and avoid u-turns, then it goes<br>> straight down w1, w2 and through the barrier to the destination. It<br>> doesn't go along w3 at all. This happens on good (and bad I think but<br>> I would have to re-check).<br>yes, the original test was without w3. I wanted to prove that the <br>link-pois-to-ways-v2.patch doesn't change something to the worse<br>as feared by Chris66 :<br><a href="http://gis.19327.n5.nabble.com/patch-v1-link-pois-to-ways-and-restrictions-tp5790650p5790923.html" target="_blank" rel="nofollow">http://gis.19327.n5.nabble.com/patch-v1-link-pois-to-ways-and-restrictions-tp5790650p5790923.html</a><br><br>The test proved that, so I wanted to find out what MapSource does if there is an <br>alternative connection which is much longer. Result is the test case.<br>Later, I've modified w3 to be much shorter, but that did not change <br>anything to the better, means, all results with wrong routes were the same.<br><br>Gerd<br><br></div> </div></body>
</html>