[Talk-us] Routing on Ferries

Natfoot natfoot at gmail.com
Thu Jan 1 18:23:51 UTC 2015

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.

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 "Mon-Sun: 7 AM–11:30 PM · every 60 min"  This is
a safe comment even though the schedules change seasonally.

Nathan P
email: natfoot at gmail.com

On Thu, Jan 1, 2015 at 8:19 AM, Clifford Snow <clifford at snowandsnow.us>

> On Wed, Dec 31, 2014 at 11:18 PM, Natfoot <natfoot at gmail.com> wrote:
>> When talking to the Scout team this summer it was mentioned as an issue.
>> Also Scout wont route across access roads and if there is an access road
>> leading up to the dock/portal then no route. you will notice that it is
>> listed as primary road in Edmonds and Kingston.
> It would appear that the router should use a ferry route. However, a check
> of both osrm and mapquest would indicate otherwise. The problem is I don't
> know if that is a routing engine problem, i.e. it won't use a ferry route,
> or a tagging problem.
> The tests were done using http://jsrouting.apis.dev.openstreetmap.org/
> Clifford
> --
> @osm_seattle
> osm_seattle.snowandsnow.us
> OpenStreetMap: Maps with a human touch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20150101/0c7d9f53/attachment-0001.html>

More information about the Talk-us mailing list