<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">ups, ... will have the <b>same edgeId</b>
so you ..<br>
<br>
</div>
<blockquote cite="mid:53624BA2.4040404@yahoo.de" type="cite">
<pre wrap="">Hey Phil,
the route result Path will give you always the edgeIteratorState with
the correct direction. If the edgeState is for the same edge then still
all states (e.g. directions are different) will have the edgeId so you
can associate them correctly to the cells IMO.
Regards,
Peter.
</pre>
<blockquote type="cite">
<pre wrap="">Am 01.05.2014 um 14:42 schrieb Peter K <a class="moz-txt-link-rfc2396E" href="mailto:peathal@yahoo.de"><peathal@yahoo.de></a>:
</pre>
<blockquote type="cite">
<pre wrap="">Why can't you use the correctly directed edgeIterStates which are
returned as routing result? (Path.calcEdges)
</pre>
</blockquote>
<pre wrap="">My simulated cars can drive in both directions, but I have only one cell
sampling for both directions, imho I get different edges for the direction.
I'm thinking about if it is a better choice to create different samplings for both
directions or can GraphHopper return for each direction different edge ids?
My driving method get the edge, so I can add on the "getting" call the current
direction, but imho an own edge should be better.
Phil
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
GraphHopper mailing list
<a class="moz-txt-link-abbreviated" href="mailto:GraphHopper@openstreetmap.org">GraphHopper@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/graphhopper">https://lists.openstreetmap.org/listinfo/graphhopper</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
GraphHopper.com - Fast & Flexible Road Routing</pre>
</body>
</html>