<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">this should be fixed in latest master
and will deployed to GraphHopper Maps in a few days.<br>
<a class="moz-txt-link-freetext" href="https://github.com/graphhopper/graphhopper/issues/168#issuecomment-48483529">https://github.com/graphhopper/graphhopper/issues/168#issuecomment-48483529</a><br>
<br>
Peter.<br>
<br>
<br>
</div>
<blockquote cite="mid:53B313A0.9060304@gmx.de" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">We want to make sure the routes are
really possible and so we avoid routes with certain barriers. <br>
<br>
But indeed there seems to be some inconsistencies for bike and
foot. E.g. for bike we disallow: kissing_gate, stile, turnstile<br>
and for foot we are more restrictive (gate and swing_gate) which
we should rethink. Maybe you create an issue for this?<br>
<br>
Regards,<br>
Peter.<br>
<br>
<br>
</div>
<blockquote
cite="mid:1404236109.88289.YahooMailNeo@web87903.mail.ir2.yahoo.com"
type="cite">
<div style="color:#000; background-color:#fff;
font-family:garamond, new york, times, serif;font-size:8pt">Using
the GraphHopper.com/maps example implementation or an existing
Routeing application that uses the GraphHopper API I
frequently come across broken routes.<br>
<br>
This appears to (almost certainly, almost always), occur at
gates ~ whether the routeing is walking, cycling or driving.<br>
This should be a usable example of walking routeing, where
there is a valid path between start and end, but because of
the gate it goes a different route to the 'nearest point' on
the far side of an impassible barrier.<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://graphhopper.com/maps/?point=51.39383%2C-2.342652&point=51.393288%2C-2.343902&vehicle=foot&elevation=true">http://graphhopper.com/maps/?point=51.39383%2C-2.342652&point=51.393288%2C-2.343902&vehicle=foot&elevation=true</a><br>
<br>
While I can continue working with the RwGPS application with
this fault, as gates are fairly infrequent for cycle planning,
and not *very* common on footpaths, it does require some
fiddle to make it work (identify a failed routeing, switch map
styles to show gates, follow route to immediately before the
gate, 'draw line' to connect across the barrier, follow route
from immediately after the gate... ok for one or two, or if
you are familiar enough to know where the routeing will
fail... not so much "fun" for longer routes on FP, in novel
terrain.<br>
<br>
<br>
<div><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
GraphHopper mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:GraphHopper@openstreetmap.org">GraphHopper@openstreetmap.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/graphhopper">https://lists.openstreetmap.org/listinfo/graphhopper</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<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>
</body>
</html>