Opened 15 years ago
Closed 14 years ago
#4931 closed defect (fixed)
U-turn restrictions created with turn restriction plugin are missing via role
Reported by: | AM909 | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Plugin turnrestrictions | Version: | tested |
Keywords: | turn restriction u-turn | Cc: |
Description
The turn restriction plugin does not know that a 'via' node is required for a no-u-turn restriction, and does not populate entries by default for the most common case of a no-u-turn at the intersection of a bi-directional way and another way.
Picture bi-directional ways A and B crossing at a standard perpendicular intersection X. You split way A into A1 and A2 at X in order to implement a no-u-turn restriction from A1 to A1 at X:
If you select way A1 and node X, then press Ctrl-Shift-T to bring up the plugin:
On the Basic tab, only the From: box is populated with A1. The To: box should also be populated with A1, and the Via: box should be populated with X.
If you manually populate the To: box with A1, the errors tab changes to "no issues" and it allows you to save the non-functional restriction (with no via node).
Also note that, when attempting to create other types of restrictions, if you select the via node first, it does NOT currently populate the Via: box with it. If you DON'T select the via node first, it (intelligently) finds it and populates the Via: box with it. If you tell it which node you want (by selecting it first), and it's a valid intersection, it should use it.
Attachments (0)
Change History (3)
comment:1 by , 14 years ago
Component: | Plugin → Plugin turnrestrictions |
---|---|
Owner: | changed from | to
comment:2 by , 14 years ago
Owner: | changed from | to
---|
comment:3 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed in [o23571]