Using Navigator by MapFactor the calculated route from Vancouver, BC Canada to Victoria on Vancouver Island took 1750km instead of the usual 112km. I found that, although the direct ferry route in open street map was shown and tagged correctly, it was not included in the navigation route. I believe this may be due to the path being designated as "unknown" instead of a "trunk road' for example. This path, named Tsawwassen to Swartz Bay, is one of many BC Ferry routes between the mainland and the island which have the same problem. First of all, am I correct in assuming that all I have to do is change the classification from unknown to trunk road for the route to be included in the navigation calculation? Then can I change a path created by someone else?

asked 17 Oct '14, 19:20

DavidJSmith's gravatar image

DavidJSmith
11112
accept rate: 0%

Notes to someone who has time to investigate: OSRM does not route to one intermediate island. Atleast OSRM conciders long ferry routes very time-costing and choooses alternative routes that are faster. * Ferry relations are FIXME (should not affect routing)

(17 Oct '14, 20:04) RM87

Selecting departure of Vancouver, BC and destination of Victoria, BC in MapFactor's Navigator app using OSM the calculated fastest route takes over 23 hours. Using the same settings and program but using Tom Tom maps takes the correct time of just over 3 hours (as tested by MapFactor's support). Google Navigator also says it takes about 3 hours using the Tsawwassen to Swartz Bay ferry. This is a direct route with no intermediate stops. I read in this help forum that the ferry route should be classified the same as the road connected to the terminals for it to be included in the navigation path. I would like to know if this is correct. After all the ferry is part of the road system here.

(17 Oct '14, 20:48) DavidJSmith
1

This is local to me and very familiar, so I'll check the tagging in a few hours after I'm done at work.

(17 Oct '14, 22:01) alester
7

Absolutely do not tag ferries as roads. They are not roads. They are ferries.

(18 Oct '14, 07:56) Richard ♦

OSRM was also refusing to route via that ferry. I checked the data on either end, and someone had made a number of changes to the data that meant some areas were inaccessible (incorrect oneway=yes, missing connections, etc.). I believe I've fixed these, so we just need to wait for the routers to update their data.

permanent link

answered 18 Oct '14, 16:22

alester's gravatar image

alester
5.8k25789
accept rate: 28%

Thank you Alester, I'll wait for the update.

(18 Oct '14, 16:43) DavidJSmith
2

I found the true problem. OSRM was seeing the ferry route as an option, but since it didn't have a "duration" tag, OSRM was assuming an extremely slow rate of travel for the route. As soon as I added a "duration" to the ferry route, OSRM has started using that as the suggested route between Vancouver and Victoria. I'll check the other local ferry routes to make sure each has a "duration".

(26 Nov '14, 02:14) alester

No, it is not correct to change this way into a highway=trunk in order to repair route calculation errors. You can use duration=* see http://wiki.openstreetmap.org/wiki/Tag:route%3Dferry

permanent link

answered 18 Oct '14, 07:01

ligfietser's gravatar image

ligfietser
2.9k52757
accept rate: 11%

edited 18 Oct '14, 07:03

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×15

question asked: 17 Oct '14, 19:20

question was seen: 2,437 times

last updated: 26 Nov '14, 02:14

powered by OSQA