<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Andrew M. Bishop wrote:<br>
<blockquote cite="midvofxg3w707.fsf@gedanken.demon.co.uk" type="cite">
<pre wrap="">
I had thought about using it to find roads that are not connected to
the highway network. Start somewhere that obviously is connected and
try routing to one node on each other road way. I don't know how you
would interpret the data though. It also wouldn't find breaks that
can be routed round.
</pre>
</blockquote>
Have you seen 'keepright' ? (
<a class="moz-txt-link-freetext" href="http://keepright.ipax.at/report_map.php?zoom=13&lat=51.58584&lon=-4.00406&layers=B0T">http://keepright.ipax.at/report_map.php?zoom=13&lat=51.58584&lon=-4.00406&layers=B0T</a>
)<br>
<br>
That already spots disconnected nodes, broken junctions, duplicated
nodes in ways, ways crossing each other without a shared node etc etc.
It might just be a duplication of effort to do that again.<br>
<br>
<br>
<blockquote cite="midvofxg3w707.fsf@gedanken.demon.co.uk" type="cite">
<pre wrap="">Steve Hosgood <a class="moz-txt-link-rfc2396E" href="mailto:steve@tallyho.bc.nu"><steve@tallyho.bc.nu></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">May I offer a couple of comments please:
1) The positioning of the 'start' and 'end' markers for the route are a
bit over-critical. The slippy map provided doesn't let you zoom in
enough to place them accurately enough. Either please add a further
layer of zoom to the zoom-tool, or increase the tolerance for searching
for a road near the 'start' or 'end' markers.
</pre>
</blockquote>
<pre wrap=""><!---->
Currently it finds the closest highway node of any type. I have been
thinking about limiting it to finding only nodes that are connected to
highway types that you have selected to use. This should solve your
problem.
</pre>
</blockquote>
Hmm - that's not what I thought I saw. I placed a marker at my home
(but not quite on the road). The machine complained that it couldn't
find a suitable route from there. So I zoomed in more and managed to
place it more accurately on the road. Then the router was happy. The
first attempt possibly had the marker about 10m off the road and it
wasn't accepted.<br>
<br>
That just seemed a bit picky, that's all. Position the marker actually
*on* the road (or maybe only 1m off the road) and it all seemed OK.<br>
<br>
<blockquote cite="midvofxg3w707.fsf@gedanken.demon.co.uk" type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<pre wrap="">2) Would be nice to mark a road type as "avoid if possible". For
instance, when finding a bicycle route you might like to mark primary
roads in that way.
</pre>
</blockquote>
<pre wrap=""><!---->
This is already a work in progress - replacing the yes/no selection
with a percentage preference.
</pre>
</blockquote>
That'll certainly do it!<br>
<br>
BTW: it might be nice to be able to set a 'preference' based on paved
or unpaved roads. On a mountain bike, you might be happy to ride an
unpaved track. On a road-race bike with 20mm wide tyres pumped to 7 bar
you certainly *don't*!!<br>
<br>
<br>
Steve<br>
<br>
</body>
</html>