There are no one-ways or seasonal allowances, no limitation for car or whatsoever; anyone can help to understand why ORS doesnt want to cross the brigde? Perhaps there was a barrier or something that has been removed, and it is just matter to wait for next routing table refresh?
@amandus, thanks for the comment. Hoever oneway=no seems to me pretty common. Several other ways in the area have it and all works. I’m going to follow your suggestion and post on the backend repository.
oneway=no is used to confirm that (a part of) a street is not a oneway street. (Use only in order to avoid mapping errors in areas where e.g. oneway streets are common, or to override defaults.)
Especially that last sentence makes me think that this tag shouldn’t have been there. Personally I’ve never had to use it.
Don’t get me wrong, the ORS code should still handle it properly, but I’m thinking that since a two-directional road is always implied in OSM this got kind of overlooked.
@Stefan thanks for your reply, and I fulyl get your point. With “seems to me pretty common” I meant several other ways in the area have this specific attribute and it seems ORS dealswith it correclty, i.e. it’s routable. For example, not only the bridge but also the two ways connected to it have the attribute as well.
hmmm. yes, I see. There are some differences though: the road coming from the south has lanes=2, the bridge and the road coming from the north have lanes=1. other than that the only difference is bridge=yes between the three features.
I don’t know the code that handles this of course, but these differences may have an effect on it.
btw: on the road with lanes=2 the oneway=no should probably be removed, see the OSM Wiki I posted earlier. of course that assumes that two lanes are going either way…