<div dir="ltr"><div><div><div>Hi Peter, we split the request containing via points into simple point to point request using our own model objects, not directly using GH api, so it can not be reused directly. But if you wish I can send the classes involved.<br>
</div><div>Bruno <br></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Aug 22, 2014 at 12:28 PM, Peter <span dir="ltr"><<a 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>ah, yes. If there is a one-way network
around the restriction a failed route for '1dir' is a lot more
likely. So maybe we remove this option entirely as it now does not
look that good anymore for me in real world.<br>
<br>
The best thing would be if we could create a hybrid solution.
Doing '1dir' for areas with no restrictions and '2dir' for the
other areas which are a lot less likely. This way we would have
same speed as node-based traversal but with correct routes. There
is a paper for this hybrid but we probably have to keep it simple
for now ...<div class=""><br>
<br>
> For our own usage I think we would not use
EDGE_BASED_2DIR_UTURN because, the u turn are mainly for the via
points<br>
<br></div>
I also do not like the routes it produces and also forbidden
u-turns are not that often tagged and so it produces forbidden
routes. So yes, maybe we remove this option also and instead make
an u-turn option available for the via-points. If you have some
code for this please do not hesitate to contribute :)<br>
<br>
Regards,<br>
Peter.<div><div class="h5"><br>
<br>
On 22.08.2014 09:57, Bruno Carle wrote:<br>
</div></div></div>
<blockquote type="cite"><div><div class="h5">
<div dir="ltr">Hi Peter,<br>
In the namesti miru example the path will not be found, even
using the full city map, this is because the northest part of
the Varsavska street is only accessible thru easter part of
Uruguaska, <br>
which is in only accessible from Francouska driving south/east.
For the map see <a href="https://graphhopper.com/maps/?point=50.074831%2C14.439039&point=50.07333%2C14.43869" target="_blank">https://graphhopper.com/maps/?point=50.074831%2C14.439039&point=50.07333%2C14.43869</a>
and <a href="http://imgur.com/MftaocZ" target="_blank">http://imgur.com/MftaocZ</a><br>
<br>
<br>
I will run later against a batch of usage routes from our prod
and let you know how often it happens.<br>
<br>
Regarding u turn, 0-1-2-1-6 would not be allowed in this namesti
miru example (the node 2 beeing where Francouska joins Namesti
Miru), <br>
For our own usage I think we would not use EDGE_BASED_2DIR_UTURN
because, the u turn are mainly for the via points (i.e. after
picking/dropping a delivery), and we do not use GH' via points,
instead we perform several point to point requests,<br>
so u turns in this case are automatically covered by the query
graph.<br>
<br>
My feeling is that often EDGE_BASED_2DIR_UTURN, will produce
routes with u turns which are not allowed. Again I will run
against some batch and let you know how often it happens.<br>
<br>
Regards <br>
Bruno<br>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><div class=""><pre>_______________________________________________
GraphHopper mailing list
<a href="mailto:GraphHopper@openstreetmap.org" target="_blank">GraphHopper@openstreetmap.org</a>
<a href="https://lists.openstreetmap.org/listinfo/graphhopper" target="_blank">https://lists.openstreetmap.org/listinfo/graphhopper</a>
</pre>
</div></blockquote>
<br>
</div>
<br>_______________________________________________<br>
GraphHopper mailing list<br>
<a href="mailto:GraphHopper@openstreetmap.org">GraphHopper@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/graphhopper" target="_blank">https://lists.openstreetmap.org/listinfo/graphhopper</a><br>
<br></blockquote></div><br></div>