Design of two-way streets with priority (= only one lane)

[rouelibre1]

It seems that two-way streets are rendered as 2 separate lanes, even when there is a priority specified (= when there is actually only one lane, with a priority for backward or forward trafic)

See exemple :

https://www.openstreetmap.org/way/406015980

Trafic coming from here has to give way https://panoramax.ign.fr/#focus=pic&map=19/48.6062/7.751619&pic=f3634a35-8dc3-4627-bc11-e142cf2937fd&speed=250&xyz=38.80/6.76/14

Trafic coming from here has priority https://panoramax.ign.fr/#focus=pic&map=18.98/48.606289/7.751869&pic=c8a0bdd2-ab95-403f-8e57-2a83f608e90f&speed=250&xyz=260.81/-2.48/47

[dabreegster]

Thanks for reporting! This has been a tricky case for many reasons. I think we can start to solve it in osm2streets first, likely by switching the lane tag parser to a new project, https://gitlab.com/LeLuxNet/Muv/. Then "downstream", there are questions like:

• How should we render this? One lane without a one-way arrow will look odd. Maybe we can still use arrows, but style them differently
• At the traffic simulation layer, how do we make the right thing happen? When there's also a parking lane and room for vehicles to squeeze past each other, it gets harder. Also, not likely to touch this anytime soon - a-b-street/abstreet#996.

So maybe just the first one is useful to do for now.

[dabreegster]

For rendering, maybe just mimicking the sign is useful. Even if this is locale dependent, it's a start:

[dabreegster]

Moving to the osm2streets repo, since this is more actionable there

[dabreegster]

Going to keep this one open to think through Direction::Both support here and better rendering