<div dir="ltr"><div><div><div><div>Hi Peter, <br><br></div>fiddling with that parameter seems to do the trick. I managed to get routing to work for Naxos with a value of 500, but had to drop this further to 200 to get routing on some even smaller islands. I have not had time to really find the minimum value for this particular constellation. <br>
<br></div>For me at this point the question is what the motivation is to exlude certain areas at all. Even if this was a private area (behind a barrier) why exclude it from roiuting? <br><br></div>Regards<br><br></div>Ludwig<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 23 September 2013 16:44, Peter K <span dir="ltr"><<a href="mailto:peathal@yahoo.de" target="_blank">peathal@yahoo.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>Hi Ludwig,<br>
<br>
probably we are a bit too aggressive with removing subareas! Ie.
it could be that the island is 'too small' for graphhopper and
will be removed (as graphhopper thinks this is a subnetwork hidden
after e.g. barriers etc). Please change
PrepareRoutingSubnetworks.minNetworkSize to something smaller than
3000 like 500 and let me know if this helps.<br>
<br>
Kind Regards,<br>
Peter.<br>
<br>
</div><div class="im">
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Thanks for your quick reply, I only had time to
look into this again now.<br>
<br>
</div>
When I read your reply, I assumed that maybe the points
I chose for illustration of the problem were too close
together or maybe on the same road, but with my larger
area I cannot get any routing to work on Naxos and I do
get the same errors on the graphhopper website, even if
I choose distant points clearly on different roads.<br>
<br>
</div>
However, if I just choose a smaller area to create the
routing data, then the routing starts working. There is no
other change to anything. Boundaries of smaller area as
given in original mail.<br>
<br>
</div>
Example: 37.120359,25.410004 to 37.1,25.38 does not work on
the extended area (and does not work on the website), but
for the smaller routing area it works. See screenshot.<br>
<br>
</div>
I have not made any effort to understand how the routing
works, but my hunch was that it is disconnected areas (in this
case multiple islands) that cause the problem. Is that even
remotely possible?<br>
</div>
</div>
</blockquote>
<br>
<br>
</div><blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div><br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<br><div class="im">
<div class="gmail_quote">On 15 September 2013 03:17, Peter K <span dir="ltr"><<a href="mailto:peathal@yahoo.de" target="_blank">peathal@yahoo.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>Hi Ludwig,<br>
<br>
it looks like GraphHopper Maps has a similar problem (I
<a href="http://graphhopper.com/maps/?point=37.169792%2C25.449737&point=37.101957%2C25.375918" target="_blank">tried your coordinates</a>). Currently
the routing goes only from junction to junction and so
the second point resolves to the same junction. Will be
fixed (in the very near future) via #27<br>
<br>
Not sure why there is a difference for the "two" areas.
It would be interesting for me to know where the second
point resolves to for your unexpanded area and how the
route looks like (screenshot?).<br>
<br>
Regards,<br>
Peter.<br>
<br>
<br>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">
<div>
<div>
<div>Following problem: I create a graphhopper
app for one of the Greek Islands and it
works. Now I expand the area to include
other islands and the same app (no code
changes) does not find the route (start and
end point are the same as previously). <br>
<br>
</div>
To me this suggests that once I include a
wider area that is not connected to a subarea,
it somehow confuses the routing. The exception
is an IllegalArgumentException that says it
cannot find point1 and cannot find point2
(then it also says the two are the same, I
guess they are internally nulled after being
unable to find them.). <br>
<br>
</div>
The bounds for my OSM extraction are as follows:<br>
<br>
#Naxos only: works<br>
export LEFT=25.3<br>
export RIGHT=25.7<br>
export TOP=37.3<br>
export BOTTOM=36.9<br>
<br>
</div>
#Wider Aegais: does not work<br>
<div>export LEFT=24<br>
export RIGHT=28.5<br>
export TOP=38<br>
export BOTTOM=35.2<br>
<br>
</div>
<div># Slightly more verbose error message from
the error stack:<br>
</div>
<div>Error:[java.lang.IllegalArgumentException:
Cannot find point 1: 37.16979166666667,
25.449736666666663,
java.lang.IllegalArgumentException: Cannot find
point 2: 37.101957, 25.375918,
java.lang.IllegalArgumentException: Point 1 is
equal to point 2]<br>
<br>
</div>
<div>Any ideas why this is so?<br>
<br>
</div>
<div>Ludwig<br>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div></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>