Talk:Key:divider
Parallel solid and dashed lines
The double lines don't necessarily have the same dash pattern. Would this be indicated using divider:left=* and divider:right=* or using divider:forward=* and divider:backward=*? – Minh Nguyễn 💬 19:43, 29 June 2022 (UTC)
- Maybe divider=dash-solid_line (dash line left) or divider=solid-dash_line (dash line right)? Something B (talk) 08:22, 11 April 2023 (UTC)
- I am in favor of divider:forward=* and divider:backward=* to keep it consistent with change:lanes=* and overtaking=*. I would consider only one line solid even if divider:forward=dashed_line is combined with divider=double_solid_line instead of divider:backward=solid_line. --Jogemu (talk) 17:50, 12 January 2025 (UTC)
- divider=* is mostly mass added, and not being worked on https://taghistory.raifer.tech/#***/divider/
There's the newer marking:*=* that should be considered to be aligned with cycleway:*=* , together with physically raised delineators. Proposal:Separation
—— Kovposch (talk) 07:14, 13 January 2025 (UTC)
- divider=* is mostly mass added, and not being worked on https://taghistory.raifer.tech/#***/divider/
Flush median
How to indicate that the divider is an area rather than a simple linear feature, and how to indicate that it has a crosshatching pattern? In some U.S. states, this pattern carries additional legal restrictions on turning versus a double solid yellow line. – Minh Nguyễn 💬 19:49, 29 June 2022 (UTC)
divider tagging on intersection node
It is common that a (double) solid line extends for considerable lengths, interrupted only by intersections. Splitting the ways before and after every intersection may not be a big hastle but using divider=no on the intersection node would be considerably faster. The nodes value could overwrite divider=* of all connected ways, but only within the intersection. Furthermore, it could avoid unnecessary checks if overtaking=* is reasonable in the short ways that would be necessary when splitting at intersections. --Jogemu (talk) 02:22, 13 January 2025 (UTC)