[Transportation] OSM access:both_ways=no wrongfully interpreted as denied access #274
Unanswered
sokadd
asked this question in
Transportation
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Category Feedback
First we need to understand what
access:both_ways
even tries to describe. Problem is, it is not even directly documented, although the suffix:both_ways
is:By applying this explanation to the access key, we get the understanding that highways with
access:both_ways=no
have a "middle"/"center turn" lane, but you are no allowed to use it.The following OSM example shows this clearly with ways 1014909000 and 1014908999:
The corresponding Overture features are
0871faa0a8ffffff0474bfb8a7497e48
and0861faa0afffffff0479fe40a6440659
where you can also spot the denied access_restriction.By my understanding, the Overture data is wrong about this, because restricting access to the middle lane does not mean restricting access to the entire highway, in both directions.
Dependency with other categories, if any.
No response
Beta Was this translation helpful? Give feedback.
All reactions