<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi Peter,<div><br></div><div>We played with the settings (minNetworkSize and highResolution) and it solved a certain class of problems. However, most of the requests still fail. After deeper investigation, we discovered it is due to one of the two points using a way which is a oneway, leading to a subnetwork from which you can’t return. It occurs in many airports or within private areas.</div><div><br></div><div>I think it is a bug in data, but despite of this, I believe Graphhopper should manage that properly in order to make it really useable. (osrm has the same issue). I mean, we have thousands of requests which fail.</div><div><br></div><div>What we did for now: We implemented in the web service an option specifying that the service, in case of a “not found”, move start or destination point (alternatively) within a certain distance, until it finds a route. This actually solve the problem by making the routing service using a routable way. Are you interested by this patch ?</div><div><br></div><div>Of course, it is only a workaround, maybe not suitable for a long term solution. We think that a correct way to fix this would be to clean the graph, at the prepare stage, removing nodes after a one way if they are less than N. What do you think about this ?</div><div><br></div><div><div apple-content-edited="true"><span style="color: rgb(0, 0, 0); font-family: Menlo; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none;">—pascal</span>
</div>
<br><div><div>Le 2 juin 2014 à 10:48, Peter K <<a href="mailto:peathal@yahoo.de">peathal@yahoo.de</a>> a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hey Pascal,<br>
<br>
there are cases with oneway where it wouldn't be logical to return
a route. Still there are workarounds like described here:<br>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/pipermail/graphhopper/2014-May/000960.html">https://lists.openstreetmap.org/pipermail/graphhopper/2014-May/000960.html</a><br>
<br>
But in your case it is a mapping problem with the incorrect oneway
somewhere here:<br>
<a class="moz-txt-link-freetext" href="http://graphhopper.com/maps/?point=43.697867%2C7.121721&point=43.69784%2C7.121657">http://graphhopper.com/maps/?point=43.697867%2C7.121721&point=43.69784%2C7.121657</a><br>
<br>
which makes the whole district in the south unavailable.<br>
<br>
Regards,<br>
Peter.<br>
<br>
<br>
</div>
<blockquote cite="mid:C61A1E6B-205A-4154-802F-1AD0A0564A9C@kds.com" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div style="margin: 0cm 0cm 0.0001pt;"><font face="Consolas">Hello
folks,</font></div>
<div style="margin: 0cm 0cm 0.0001pt;"><font face="Consolas"><br>
</font></div>
<div style="margin: 0cm 0cm 0.0001pt;"><font face="Consolas">I am
Pascal and I currently evaluate Graphhopper as an alternative
routing service for my company.</font></div>
<div style="margin: 0cm 0cm 0.0001pt;"><font face="Consolas"><br>
</font></div>
<div style="margin: 0cm 0cm 0.0001pt;"><font face="Consolas">We
are currently facing an issue with an itinerary: from “Nice"
to “St Paul de vence”, we just get a “not found” response from
GH.</font></div>
<div style="margin: 0cm 0cm 0.0001pt;"><font face="Consolas"><br>
</font></div>
<div style="margin: 0cm 0cm 0.0001pt;"><font face="Consolas">I
tested the official online instance and I get the same
behaviour:</font></div>
<div style="margin: 0cm 0cm 0.0001pt;"><a moz-do-not-send="true" href="http://maps.ad-kds.lan.net:8900/?point=43.703002,7.265224&point=43.694687,7.124634&locale=fr-FR" style="color: purple;"><font face="Consolas">http://graphhopper.com/maps/?point=nice%20&point=saint%20paul%20de%20vence</font></a></div><p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt;"><font face="Consolas"> </font></p>
<div style="margin: 0cm 0cm 0.0001pt;"><font face="Consolas">Whereas
the opposite works fine:</font></div>
<div style="margin: 0cm 0cm 0.0001pt;"><font face="Consolas"><a moz-do-not-send="true" href="http://graphhopper.com/maps/?point=saint%20paul%20de%20vence&point=nice">http://graphhopper.com/maps/?point=saint%20paul%20de%20vence&point=nice</a></font></div>
<div><font face="Consolas"><br class="webkit-block-placeholder">
</font></div>
<div apple-content-edited="true">
<font face="Consolas">Is it a bug related to some kind of one
way direction ?</font></div>
<div apple-content-edited="true"><font face="Consolas"><br>
</font></div>
<div apple-content-edited="true"><font face="Consolas">Should I
submit a bug, or do I miss something ?</font></div>
<div apple-content-edited="true"><font face="Consolas"><br>
</font></div>
<div apple-content-edited="true"><font face="Consolas">Thanks in
advance for your help,</font></div>
<div apple-content-edited="true"><font face="Consolas"><br class="Apple-interchange-newline">
<span style="font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">—pascal</span>
</font></div>
</blockquote>
<br>
</div>
_______________________________________________<br>GraphHopper mailing list<br><a href="mailto:GraphHopper@openstreetmap.org">GraphHopper@openstreetmap.org</a><br>https://lists.openstreetmap.org/listinfo/graphhopper<br></blockquote></div><br></div></body></html>