<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks for getting back...</p>
<p>1) --keep-complete in splitter - yes. I figured with the long
routes and few nodes that this could be a possible point of
failure so I made sure to add it.<br>
</p>
<p>2) iWowik sent a PM suggesting that some of the important tags
were incorrect and/or missing and he was addressing some of them.
One suggestion of his was to use Key:ferry to help maintain
connectivity to the roads. Wiki states "With <tt
style="background:#EEF" dir="ltr" class="mw-content-ltr"><bdi
style="white-space:nowrap"><a
href="http://wiki.openstreetmap.org/wiki/Key:route"
title="Key:route">route</a></bdi>=<a
href="http://wiki.openstreetmap.org/wiki/Tag:route%3Dferry"
title="Tag:route=ferry"><bdi>ferry</bdi></a></tt>, this tag
can take the <tt style="background:#EEF" dir="ltr"
class="mw-content-ltr"><bdi style="white-space:nowrap"><a
href="http://wiki.openstreetmap.org/wiki/Key:highway"
title="Key:highway">highway</a></bdi>=*</tt> classification
of the roads it connects, like a bridge." So the service /
trunk_link issue Andrzej noted is very interesting. If not given,
what road classification does the routing engine see for the
ferry?<br>
</p>
<p>3) I made sure to untick the Toll Road avoidance thinking this
may be an issue as well, but no change.</p>
<p>OK... so it looks like there may be several issues at work here.
I didn't realize that ferries were such a can of worms both from a
mapping and a routing perspective. I expect that this service
road issue is a common problem with ferry mapping. Also, given the
impact that ferries can have on travel distance and time, unless
explicitly avoided, perhaps ferries should always be given a
pretty high priority in routing? They're more than just a stretch
of 30km/hr highway.</p>
<p>Thanks for looking into this! <br>
</p>
Sam<br>
</body>
</html>