Turnrestrictions plugin doesn't like adding a new restriction on two ways when they already intersect at a different location.

[rickmastfan67]

Ok, I'm trying to add a new U-turn restriction I saw yesterday. I had already previously added another one dealing with the same two ways (where they split) at an intersection node. This time, (it's a divided road), I needed to add another restriction that uses a service road. So, I download the area and do my normal steps to add the new restriction. However, the Turnrestrictions plugin claims there is an error in doing it. I mean, I can force it, to accept it, but I'd rather not do it till you can fix this problem with the plugin. Once it's done, then I'll put the restriction into the database.

Steps to reproduce:

1. Download the following ways: 11947926; 76699184; 76699390 (make sure "Download referrers" is checked)
2. Open up the create new restriction option.
3. Place 11947926 in the From line.
4. Place 76699390 in the To line.
5. Place 76699184 in the Via box.
6. Select the "No U-Turn" restriction.

What should happen?
No error should pop up in the error menu.

What does happen?
The following error message is shown:

The from-way Washington Pl (5 nodes) and the to-way Washington Pl (4 nodes) interesect at node 104824604 (40.4388071, -79.9909280) but 104824604 (40.4388071, -79.9909280) isn't a via-object.
It is recommended to set 104824604 (40.4388071, -79.9909280) as unique via-object.

Can you please fix this bug? Because it wants me to place the intersecting node (where the intersection is) as the Via object. And the major problem with that is that the relation would be going the wrong way.

JOSM r4021 - Turnrestrictions v25465.

[rickmastfan67]

Alright, I've made this bug a little easier to deal with.

I've gone ahead and put in the turn restriction just now into the OSM database.

Download the following relation: 1552440 (make sure "Download referrers" is checked)

Once it's loaded, in the Turn Restrictions windows, there should only be one restriction listed. Select it and hit the Edit button. When you do that, you'll find there is one "error" mentioned which isn't an error. Hopefully you'll be able to figure out what's causing this problem since it is a valid restriction.