as discussed in #569 many people don't like the existing highway rules because it is too inflexible, annoying and messes their roundabouts.
I am going to add a new highway option. then make the old highway option legacy.
the new highway option works like this:
1- only works when merging
2- only works when lane mathematics add up (ie incoming lanes == outgoing lanes).
3- only works when there is no lane connections on the merging lanes. (same as legacy)
4- there is no cars may switch lane on junctions rule. (same as legacy)
5- does not restrict lane arrows. Although when merging you can only turn right anyway so this is not that much of a change. In any case I do not use highway lane arrows used by the legacy code.
future tasks:
1562
1561
restrictions (2) and (3) make it less likely for roundabout to be confused with highway. Additionally roundabout mass edit code adds 569 rule on highways so (4) provides another layer of protection.
(5) and (6) is there for extra flexibility so that it does not annoy users.
as discussed in #569 many people don't like the existing highway rules because it is too inflexible, annoying and messes their roundabouts.
I am going to add a new highway option. then make the old highway option legacy. the new highway option works like this: 1- only works when merging 2- only works when lane mathematics add up (ie incoming lanes == outgoing lanes). 3- only works when there is no lane connections on the merging lanes. (same as legacy) 4- there is no
cars may switch lane on junctionsrule. (same as legacy) 5- does not restrict lane arrows. Although when merging you can only turn right anyway so this is not that much of a change. In any case I do not use highway lane arrows used by the legacy code.future tasks:
1562
1561
restrictions (2) and (3) make it less likely for roundabout to be confused with highway. Additionally roundabout mass edit code adds 569 rule on highways so (4) provides another layer of protection.
(5) and (6) is there for extra flexibility so that it does not annoy users.