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: [email protected] On Thu, Jan 1, 2015 at 8:19 AM, Clifford Snow <[email protected]> wrote: > > On Wed, Dec 31, 2014 at 11:18 PM, Natfoot <[email protected]> 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 >
_______________________________________________ Talk-us mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-us
