Open henrigrossmann opened 6 months ago
The permissions are stored in the lanes anyway. I think you can modify the permission settings of internal lanes in netedit and the doc mentions you can patch it with PlainXML connection definitions (allow/disallow). Haven't tried the latter right now.
Thank you for your fast reply. Unfortunately, the allow/disallow specification does not work for connections.
example.zip here's an example where the connection from="182422861#1" to="1264142811#0" should only allow buses and bicycles but cars are using the connection too.
Well because there are no internal lanes (<no-internal-links value="true" />
), this information is discarded effectively. We'll have to think about it. Thanks for notifying us.
Task: when network has no internal links, the allow/disallow values of the <connection>
elements must be stored in MSLink and used in MSEdge::rebuildAllowedTargets
Currently, the connection specification lacks the ability to specify which types of vehicles can utilize a particular connection. This limitation becomes particularly significant when considering scenarios where different vehicle types, such as cars and buses, might not share the same turn lanes. This issue is closely related to #14248 but now that #14476 has been implemented, introducing vehicle type restrictions to connections seems like an extremely valuable enhancement.