<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 1/1/15 1:55 PM, Clifford Snow wrote:<br>
</div>
<blockquote
cite="mid:CADAoPLoXk+YmyF37xNXhA3KU+_9PEexRpJfwMSpvtj4s3of4MQ@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Jan 1, 2015 at 10:23 AM,
Natfoot <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:natfoot@gmail.com" target="_blank">natfoot@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote">
<div dir="ltr">The inherent problem with ferry routes is
that they have a schedule. Routers can't then tell
their users how long it is going to take without that
data. <br>
<span><br>
As far as I know we don't have schedule capability
within OSM and it is something that the routers have
not pulled not even the big G. The big G is listing
the route as being "</span><span>Mon-Sun: <span
class="aBn" tabindex="0"><span class="aQJ">7 AM–11:30 PM</span></span>
· every 60 min" This is a safe comment even though
the schedules change </span><span>seasonally</span></div>
</blockquote>
</div>
<br>
I agree. However, it would be nice to have it show the route.
Somehow we can route via bus using GTFS. I wonder if ferry
routes have a similar spec?</div>
<br>
</div>
</blockquote>
and there are places (for example, Ocracoke Island on the outer
banks)<br>
which are only accessible via ferry and thus can't be routed to by
apps<br>
that don't handle ferries.<br>
<br>
richard<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-abbreviated" href="mailto:rwelty@averillpark.net">rwelty@averillpark.net</a>
Averill Park Networking - GIS & IT Consulting
OpenStreetMap - PostgreSQL - Linux
Java - Web Applications - Search</pre>
</body>
</html>