<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Thanks, I'll investigate.<br>
<br>
</div>
<blockquote
cite="mid:01E7E8E50C98824E9045DFD5FFC859D402B8CE133516@SBSRV.ot.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi everyone,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">there seems to be a bug routing with
bidirectional algorithms. I’ve got different routing results
for same queries. (see attached pictures)<br>
All bidirectional algos are picking suboptimal pathes
sometimes.<br>
<o:p></o:p></p>
<p class="MsoNormal">For all I know A*-bidirectional is supposed
to result in possible suboptimal routes, but dijkstrabi and
dijkstraNativebi should find the shortest/fastest path.<br>
The finish condition (<span
style="font-size:9.0pt;color:black">currFromWeight +
currToWeight >= nativeBestPath.getWeight()</span><span
style="font-size:9.0pt;color:black">)</span><span
style="color:black"> should accept only for the best path or
am I missing something?<br>
<br>
<br>
</span><o:p></o:p></p>
<p class="MsoNormal">Note: to replicate the attached routes you
have to disable contraction hierarchies<br>
here are the related URLs:<br>
<a moz-do-not-send="true"
href="http://localhost:8989/?point=48.983206%2C12.140568&point=48.983438%2C12.136411&weighting=shortest&algorithm=dijkstra">http://localhost:8989/?point=48.983206%2C12.140568&point=48.983438%2C12.136411&weighting=shortest&algorithm=dijkstra</a><o:p></o:p></p>
<p class="MsoNormal"><a moz-do-not-send="true"
href="http://localhost:8989/?point=48.983206%2C12.140568&point=48.983438%2C12.136411&weighting=shortest&algorithm=dijkstraNative">http://localhost:8989/?point=48.983206%2C12.140568&point=48.983438%2C12.136411&weighting=shortest&algorithm=dijkstraNative</a><o:p></o:p></p>
<p class="MsoNormal"><a moz-do-not-send="true"
href="http://localhost:8989/?point=48.984428%2C12.144517&point=48.983146%2C12.136631&algorithm=dijkstra">http://localhost:8989/?point=48.984428%2C12.144517&point=48.983146%2C12.136631&algorithm=dijkstra</a><o:p></o:p></p>
<p class="MsoNormal"><a moz-do-not-send="true"
href="http://localhost:8989/?point=48.984428%2C12.144517&point=48.983146%2C12.136631&algorithm=dijkstrabi">http://localhost:8989/?point=48.984428%2C12.144517&point=48.983146%2C12.136631&algorithm=dijkstrabi</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
</blockquote>
<br>
</body>
</html>