<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 Bruno,<br>
<br>
I try to integrate this into GH when I have time (or someone other
can add some basic unit tests + add it as pull request)<br>
<br>
Considering your second case, I do not understand it fully. If it
is not a map problem, then how can a vehicle get there? (Even if
it is a service highway)<br>
<br>
Regards,<br>
Peter.<br>
<br>
</div>
<blockquote
cite="mid:CANsAejU67p+ARrQW6-zVznP76dH4N7w+gKJ56gUw9ZCVJCDtDg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Hi,<br>
</div>
<div>I just wrote a small class that fixes this kind of issues.
Basically it looks for nodes where there is a way in but not
out (and vice-versa), and disable all edges around the node.
It seems to work fine so far. I Think islands will not be a
problem but I have not tested it since I don't have any
islands on the area I am working on.<br>
<br>
</div>
<div>For cases when there is no way out but there is a way in, I
believe most likely it is a problem on the map.<br>
</div>
<div>For cases when there is no way in but a way out , I believe
the map is correct: e.g. <a moz-do-not-send="true"
href="http://www.openstreetmap.org/way/27565747">http://www.openstreetmap.org/way/27565747</a>,
and hence this should be addressed in GH.<br>
<br>
</div>
<div>This is how to call it: (if you have multiple encoders you
ll need a way to retrieve the encoder's directionBitMask)<br>
</div>
<div><br>
</div>
<div>@Override<br>
</div>
<div>public GraphHopper importOrLoad(){<br>
super.importOrLoad();<br>
FixOneWayDeadEnds.fixAllOneWayDeadEnds(this.getGraph(),getEncodingManager().getSingle(),3l);<br>
</div>
<div> return this;<br>
</div>
<div>}<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Cheers<br>
</div>
<div>Bruno<br>
</div>
<div><br>
<br>
<br>
<br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Jun 16, 2014 at 9:52 PM,
graphhopper <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:graphhopper@gmx.de" target="_blank">graphhopper@gmx.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Yeah this is a frequent requested feature but not
hard to implement:<br>
<a moz-do-not-send="true"
href="http://graphhopper-read-only-archive.1087335.n5.nabble.com/Issues-detecting-driving-paths-along-one-way-streets-td1002.html#a1003"
target="_blank">http://graphhopper-read-only-archive.1087335.n5.nabble.com/Issues-detecting-driving-paths-along-one-way-streets-td1002.html#a1003</a><br>
<br>
But this would mean hiding the real OSM issues ...<br>
<br>
Regards,<br>
Peter.<br>
<br>
</div>
<div>
<div class="h5">
<blockquote type="cite"> 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><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;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;display:inline!important;float:none">—pascal</span>
</div>
<br>
<div>
<div>Le 2 juin 2014 à 10:48, Peter K <<a
moz-do-not-send="true"
href="mailto:peathal@yahoo.de"
target="_blank">peathal@yahoo.de</a>> a
écrit :</div>
<br>
<blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000">
<div>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 moz-do-not-send="true"
href="https://lists.openstreetmap.org/pipermail/graphhopper/2014-May/000960.html"
target="_blank">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 moz-do-not-send="true"
href="http://graphhopper.com/maps/?point=43.697867%2C7.121721&point=43.69784%2C7.121657"
target="_blank">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 type="cite">
<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" target="_blank"><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"
target="_blank">http://graphhopper.com/maps/?point=saint%20paul%20de%20vence&point=nice</a></font></div>
<div><font face="Consolas"><br>
</font></div>
<div> <font face="Consolas">Is it a bug
related to some kind of one way
direction ?</font></div>
<div><font face="Consolas"><br>
</font></div>
<div><font face="Consolas">Should I submit
a bug, or do I miss something ?</font></div>
<div><font face="Consolas"><br>
</font></div>
<div><font face="Consolas">Thanks in
advance for your help,</font></div>
<div><font face="Consolas"><br>
<span
style="font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">—pascal</span></font><br>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>