The result is that I don’t get the ferry Hanko-Rostock for the route, also with other parameters, car or fastest.
It seems to me that routing should be done via the the ferry line.
The ferry line is here:
But the ferry is also tagged hgv = true and trailer = true!
So we have vehicle = no and hgv= true on this way. Can this be coherent ?
We are analyzing freight traffic, and there is some freight going over this ferry in “reality”. How can I route freight in trailers/hgv over this ferry?
According to the wiki, hgv = yes (it’s true here) means: “Roads and other objects accessible to trucks”
This does not make sense at all. The vehicle=no tag implicitly forbids all vehicles:
Legal access restriction for all types of land-based vehicles not operated upon rails.
which overrules hgv=true. In order to solve this, I don’t think it’s a bug as @sascha filed, but the tag vehicle=no should be removed or changed into yes.
Actually, more specific OSM access tags such as hgv override the more generic ones, in this case vehicle.
I think the issue here might not be the tagging of the highways, but rather the barriers, e.g. Node: 9451269151 | OpenStreetMap. Please note that the route is found once the starting point is set past the lift gate.
It is certainly related to this barrier. On the OSM-website, none of the routing engines (Valhalla, GraphHopper, OSRM) is able to pass this gate. I guess it is related to the tag “access=permit”. According to Tag:access=permit - OpenStreetMap Wiki the intended usage described on is that the routing should pass through the gate, however, the actual usage is often equivalent to “access=private”. An easy fix is proposed in the corresponding github isse.